[97843] in RedHat Linux List
Re: linuxconf wants to kill crond
daemon@ATHENA.MIT.EDU (Jacques Gelinas)
Thu Nov 5 11:43:00 1998
Date: Thu, 5 Nov 1998 11:39:36 -0500 (EST)
From: Jacques Gelinas <jack@solucorp.qc.ca>
Reply-To: Jacques Gelinas <jack@solucorp.qc.ca>
To: redhat-list@redhat.com
cc: marcv@vlminc.net
In-Reply-To: <19981104013444.14346.qmail@mail2.redhat.com>
Resent-From: redhat-list@redhat.com
> Does anyone know why after a fresh reboot I can run linuxconf and when
> exiting it tells me it wants to kill my cron daemon?
> Here is the error as to what it wants to change:
> Executing: /etc/rc.d/rc3.d/S40crond stop
> I don't want it to stop the crond. It starts up at bootup and runs fine
> but if I let linuxconf have it's way when exiting it will shut it down.
> Is there a place where linuxconf is checking for the state of crond and
> then deciding it should be killed?
The file /etc/rc.d/rc3.d/S40crond contains some tags at the beginning
telling linuxconf what to do. Here they are
# processname: crond
# config: /etc/crontab
# pidfile: /var/run/crond.pid
The config tag tells linuxconf that this file influences the crond
process. If this file is newer than the process, then the command
/etc/rc.d/rc3.d/S40crond restart
will be issued. If the file is missing, linuxconf issue the stop command.
If /etc/crontab is missing on your system, your redhat installation won't
work that well. Most maintenance commands normally run with crond (in the
/etc/cron.*/ directories) won't be executed and your disk will fill over
time.
I suggest that you get back this file and the linuxconf problem with go
away. Many other problems will also go away. This file is part of the
crontabs package.
--------------------------
Jacques Gelinas
jack@solucorp.qc.ca
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com http://archive.redhat.com
To unsubscribe: mail redhat-list-request@redhat.com with
"unsubscribe" as the Subject.
