You are not logged in.

#1 2012-11-02 14:41:39

nuc
Member
Registered: 2012-04-26
Posts: 119

Cron error at boot [Systemd]

Hi, I get this error during boot:

/usr/sbin/crond[295]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory
/usr/sbin/crond[295]: (CRON) INFO (running with inotify support)

I disabled the syslog-ng Daemon because journalctl took over that task.
Do I need to start the syslog-ng Daemon nevertheless for compatibility reasons?

Last edited by nuc (2012-11-02 14:42:02)

Offline

#2 2012-11-08 11:44:13

Harey
Member
From: Bavaria, Germany
Registered: 2007-03-24
Posts: 374

Re: Cron error at boot [Systemd]

nuc wrote:

Hi, I get this error during boot:

/usr/sbin/crond[295]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory
/usr/sbin/crond[295]: (CRON) INFO (running with inotify support)

Me too. smile

nuc wrote:

I disabled the syslog-ng Daemon because journalctl took over that task.
Do I need to start the syslog-ng Daemon nevertheless for compatibility reasons?

Well, from what I researched this seems to be an unavoidable message at the moment. Crond can only send its output to either sendmail or syslog. According to man crond one can choose syslog by using

/usr/sbin/crond -s

I tried to set this in /usr/lib/systemd/system/cronie.service but it doesn't seem to have any effect. The use of syslog-ng seems to be a bit flaky too, because if you enable this service there are some complaints in journalctl about it not being able to pass all messages to syslog and skipping some from time to time.

I guess we have to wait until cronie upstream implements using systemd natively.

Harvey


Linux is like a wigwam: No Gates, no Windows and an Apache inside

Offline

Board footer

Powered by FluxBB