[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xlog-discussion] Cwdaemon
From: |
John |
Subject: |
Re: [Xlog-discussion] Cwdaemon |
Date: |
Tue, 24 Sep 2013 20:28:09 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7 |
Thank you, Tomi. I have reported my results in your quoted message:
On 09/24/2013 09:54 AM, Tomi Manninen wrote:
John address@hidden kirjoitti:
It's really strange that my init.d and default/cwdaemon don't start
it. Wonder what's going on?
As nobody seems to have addressesd this, I feel the urge to jump in
although I have never used cwdaemon...
A script in /etc/init.d and/or a settings file in /etc/defaults
doesn't cause the script to be actually ever run.
In traditional sysv init scripts, it's the symbolic links in
/etc/rcN.d that actually make daemons be started. Ubuntu nowadays uses
is't own Upstart in place of traditional Sysv Init but it has enough
backwards compatibility that things still work.
The N in rcN.d refers to the current "runlevel". Again Ubuntu
(Upstart) doesn't have runlevels but fakes them so that scripts work.
What I would do is first check that your init script works when
invoked manually:
# sudo /etc/init.d/cwdaemon start
address@hidden:~$ sudo /etc/init.d/cwdaemon start
[sudo] password for john:
Removing module lp
Starting Morse daemon: cwdaemonSegmentation fault (core dumped)]
Then check what (faked) runlevel you are on:
# runlevel
address@hidden:~$ runlevel
N 2
It probably says "N 2" which means current (faked) runlevel is 2. Now
check that you have a symbolic link in /etc/rc2.d. Something like this:
# ls -l /etc/rc2.d
..
lrwxrwxrwx 1 root root 11 Jan 1 1970 SNNcwdaemon -> ../init.d/cwdaemon
..
address@hidden:~$ ls -l /etc/rc2.d
total 4
-rw-r--r-- 1 root root 677 Jan 30 2013 README
lrwxrwxrwx 1 root root 18 Sep 19 13:27 S20cwdaemon -> ../init.d/cwdaemon
.
.
Here the letter S marks scripts that are *S*tarted when entering
runlevel 2. The NN is a number that defines the execution order of the
scripts. If the link is missing then you need to make it. I guess the
standard way is to call update-rc.d:
# sudo update-rc.d cwdaemon defaults
It doesn't look as if the symlink is missing, so I didn't pursue the
above step or the next.
If that doesn't do it, you can also make the link manually:
# cd /etc/rc2.d
# ln -s ../init.d/cwdaemon S99cwdaemon
You need to figure out the correct place to start it yourself but I
guess 99 should be pretty safe.
If you have the symlink in place already, then forget all about this
email and continue to search the answer somewhere else... :)
It looks as if the answer must lie elsewhere, Tomi, unless I'm missing
something obvious (which is always a possibility).
Thanks very much for jumping in!
--John K3GHH