Am I missing something when it comes to /etc/rc.local? - Page 2

chrism01 · 03-17-2008, 03:15 AM

given that the /etc/rc.local process needs to terminate...

nohup <yourcommand> &

Jongi · 03-17-2008, 05:58 PM

Quote:

Originally Posted by chrism01

given that the /etc/rc.local process needs to terminate...

nohup <yourcommand> &

The below did not work

Code:

[root:~#] cat /etc/rc.local
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.
touch /var/lock/subsys/local
nohup /usr/bin/hellanzb.py -D &

billymayday · 03-17-2008, 07:26 PM

Have you tried something more like

Code:

python /usr/bin/hellanzb.py -D -c /etc/hellanzb.conf

Note the explicit specification of python and clarification of config

Jongi · 03-19-2008, 07:39 PM

billymayday - that didn't work. i suspect there must be something about the nature of hellanzb.

chrism01 · 03-20-2008, 02:42 AM

When I said <yourcmd> that means everything it needs to run, inc full paths to prog and cfg file etc. Just like cron ....

Jongi · 03-20-2008, 08:49 PM

Code:

[root:~#] cat /etc/rc.local
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.
/sbin/modprobe snd-ca0106
touch /var/lock/subsys/local
python /usr/bin/hellanzb.py -D -c /usr/etc/hellanzb.conf

that's what didn't work

billymayday · 03-20-2008, 09:16 PM

Do you get any kind of message during the startup process, entries in logs?

Jongi · 03-21-2008, 06:33 AM

I can see just as the boot process finishes that there is some sort of message but it almost immediately starts loading the DM. Maybe if I booted up in init 3 I would be able to see it? Or does the screen clear and the login prompt then appears?

I've also looked in these two logs and nothing

Code:

[root:~#] cat /var/log/boot.log
[root:~#] cat /var/log/messages | grep hella

tredegar · 03-21-2008, 08:44 AM

When you start /usr/bin/hellanzb.py from the command line (and presumably it works OK from the command line), which user are you running as? If it is yourself, then that is the problem, as commands in rc.local are run as the root user. Please try suing to yourself, then running the command, with a line like this at the end of rc.local

Code:

su - yourusername -c "cd /home/yourusername/ && /usr/bin/hellanzb.py" &

This is how I start a vncserver for my username when one of my boxes boots. It works nicely

PTrenholme · 03-21-2008, 12:19 PM

Try adding a sleep 10 as the script's last command to "pause" the output long enough for you to read the messages (if any).

Jongi · 03-21-2008, 03:42 PM

doesn't matter whether i run it as root or a normal user. If the command is successfully run, it is in a daemonised state and thus a ps aux should pick it up as running.

will try the sleep 10 command.

PTrenholme · 03-21-2008, 04:09 PM

The "10" in the sleep 10 is the number of seconds to "sleep," so you can increase it as needed.

From man sleep:

Code:

SLEEP(1)                         User Commands                        SLEEP(1)

NAME
       sleep - delay for a specified amount of time

SYNOPSIS
       sleep NUMBER[SUFFIX]...
       sleep OPTION

DESCRIPTION
       Pause  for  NUMBER seconds.  SUFFIX may be ‘s’ for seconds (the default), ‘m’ for
       minutes, ‘h’ for hours or ‘d’ for days.  Unlike most implementations that require
       NUMBER  be  an  integer,  here  NUMBER may be an arbitrary floating point number.
       Given two or more arguments, pause for the amount of time specified by the sum of
       their values.

Jongi · 03-21-2008, 04:28 PM

Yeah I kinda guessed that's what it does.And that has shed the first serious bit of light on the problem.

The following error is what presents itself

Code:

Please install notify-python or disable Hellanzb.LIBNOTIFY_NOTIFY.

I am suspecting that hellanzb is trying to run in init 3 where notify-python is not loaded. I am guessing this as when I am in a desktop manager, There is no problems with running it.

Code:

[root:~#] yum list | grep notify
libnotify.x86_64                         0.4.4-8.fc8            installed
libnotify.i386                           0.4.4-8.fc8            installed
notify-python.x86_64                     0.1.1-2.fc8            installed
python-inotify.x86_64                    0.7.1-1.fc8            installed
inotify-tools.i386                       3.13-1.fc8             updates
inotify-tools.x86_64                     3.13-1.fc8             updates
inotify-tools-devel.x86_64               3.13-1.fc8             updates
inotify-tools-devel.i386                 3.13-1.fc8             updates
kadu-exec_notify.x86_64                  0.5.0-4.fc8            fedora
kadu-led_notify.x86_64                   0.5.0-4.fc8            fedora
kadu-osdhints_notify.x86_64              0.5.0-4.fc8            fedora
libnotify-devel.x86_64                   0.4.4-8.fc8            fedora
libnotify-devel.i386                     0.4.4-8.fc8            fedora
pidgin-knotify.x86_64                    0.1-5.fc8              fedora
pidgin-libnotify.x86_64                  0.13-2.fc8             fedora
python-inotify-examples.x86_64           0.7.1-1.fc8            fedora

EDIT: My suspicion above was confirmed by running hellanzb.py -D in init 5 and 3 once the system had booted. And sure enough the same error pops up in init 3.

Jongi · 03-23-2008, 06:18 PM

The key of course was then to run the file not through a console script but through a x script. Enter

Code:

[root:~#] cat /etc/X11/xinit/xinitrc.d/helladaemon.sh
#!/bin/sh
/usr/bin/hellanzb.py -D

which then on boot produces

Code:

[root:~#] ps aux | grep hella
jongi     2469  0.0  1.8 300552 19256 ?        S    00:14   0:00 /usr/bin/python /usr/bin/hellanzb.py -D

So now all is order. Thanks for everyone's help.

konsolebox · 03-23-2008, 10:16 PM

i should have known.. your /usr/bin/hellanzb.py is X dependent right?