Re: Cron Security Problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am Di, den 18.10.2005 schrieb work@xxxxxxxxxxxxxxxx um 13:36:

> Does anyone know how to resolve this cron error?

Wrong list.

> Oct 18 06:41:01 la1 crond[4847]: (*system*) BAD FILE MODE
> (/etc/cron.d/popmail)
> Oct 18 06:42:01 la1 crond[4847]: (*system*) BAD FILE MODE
> (/etc/cron.d/loadmysql)
> Oct 18 06:42:01 la1 crond[4847]: (*system*) BAD FILE MODE
> (/etc/cron.d/pop-perl)
> Oct 18 07:01:02 la1 crond[16105]: (root) CMD (run-parts /etc/cron.hourly)

Don't put executable script files into /etc/cron.d/.

Alexander


-- 
Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773
legal statement: http://www.uni-x.org/legal.html
Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp 
Serendipity 23:56:37 up 5:30, 16 users, 0.82, 0.88, 0.86 

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil

--
fedora-selinux-list mailing list
fedora-selinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-selinux-list

[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux