[gentoo-user] Init files and daemon state
I'm having problems with daemon init on Gentoo. Whenever, for example, due to a misconfigured file, a daemon with an /etc/init.d file does not start, (typically sendmail, bind, etc.), whenever I try to restart it using the /etc/init.d/daemon restart, or a stop/ start sequence, or just a plain start, it refuses to start again. The error message says that the daemon has already started, in spite of the fact that it did not start. If I then try to stop it, I am told that it was not started. The only way to get the daemon up again is to reboot or change the runlevel and then switch back to the default runlevel. I am sure there is an easier way to do this. Thanks, Krishnan -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Init files and daemon state
In many cases you can use zap instead of stop which will the process. From: S. Krishnan [EMAIL PROTECTED] Date: 2004/01/21 Wed PM 03:22:07 GMT To: gentoo-user [EMAIL PROTECTED] Subject: [gentoo-user] Init files and daemon state I'm having problems with daemon init on Gentoo. Whenever, for example, due to a misconfigured file, a daemon with an /etc/init.d file does not start, (typically sendmail, bind, etc.), whenever I try to restart it using the /etc/init.d/daemon restart, or a stop/ start sequence, or just a plain start, it refuses to start again. The error message says that the daemon has already started, in spite of the fact that it did not start. If I then try to stop it, I am told that it was not started. The only way to get the daemon up again is to reboot or change the runlevel and then switch back to the default runlevel. I am sure there is an easier way to do this. Thanks, Krishnan -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Init files and daemon state
S. Krishnan wrote: I'm having problems with daemon init on Gentoo. Whenever, for example, due to a misconfigured file, a daemon with an /etc/init.d file does not start, (typically sendmail, bind, etc.), whenever I try to restart it using the /etc/init.d/daemon restart, or a stop/ start sequence, or just a plain start, it refuses to start again. The error message says that the daemon has already started, in spite of the fact that it did not start. If I then try to stop it, I am told that it was not started. The only way to get the daemon up again is to reboot or change the runlevel and then switch back to the default runlevel. I am sure there is an easier way to do this. And just for completness ... every started demon has symlink in /var/lib/init.d/started if u remove it, u can restart the demon paintless again noro -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Init files and daemon state
On Wed, 2004-01-21 at 17:28, Norbert Kamenicky wrote: S. Krishnan wrote: I'm having problems with daemon init on Gentoo. Whenever, for example, due to a misconfigured file, a daemon with an /etc/init.d file does not start, (typically sendmail, bind, etc.), whenever I try to restart it using the /etc/init.d/daemon restart, or a stop/ start sequence, or just a plain start, it refuses to start again. The error message says that the daemon has already started, in spite of the fact that it did not start. If I then try to stop it, I am told that it was not started. The only way to get the daemon up again is to reboot or change the runlevel and then switch back to the default runlevel. I am sure there is an easier way to do this. And just for completness ... every started demon has symlink in /var/lib/init.d/started if u remove it, u can restart the demon paintless again Thanks to everyone who replied. I really appreciate the incredible helpfulness of everyone on the list. Regards, Krishnan -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Init files and daemon state
On Wed, 2004-01-21 at 22:28, Norbert Kamenicky wrote: S. Krishnan wrote: I'm having problems with daemon init on Gentoo. Whenever, for example, due to a misconfigured file, a daemon with an /etc/init.d file does not start, (typically sendmail, bind, etc.), whenever I try to restart it using the /etc/init.d/daemon restart, or a stop/ start sequence, or just a plain start, it refuses to start again. The error message says that the daemon has already started, in spite of the fact that it did not start. If I then try to stop it, I am told that it was not started. The only way to get the daemon up again is to reboot or change the runlevel and then switch back to the default runlevel. I am sure there is an easier way to do this. And just for completness ... every started demon has symlink in /var/lib/init.d/started if u remove it, u can restart the demon paintless again noro And for more completeness, you can `/etc/init.d/postfix zap` (example) to remove it for you... -- Tom Wesley signature.asc Description: This is a digitally signed message part
