Aiya, > I can't see anything that would make /etc/fcron.conf have more permissive > access modes in a clean install of *fcron* (i.e. from purged state).
File has not been chmoded, it is as it comes when fcron is installed: $ ls -la /etc/fcron.conf -rw-r----- 1 root fcron 676 2005-03-26 06:13 /etc/fcron.conf > Take a look at dpkg-statoverride | grep fcron, and see if /etc/fcron.conf is > mentioned there. If it is, tell me. $ dpkg-statoverride | grep fcron dpkg-statoverride: no mode specified $ dpkg-statoverride --list | grep -i fcron root fcron 4750 /usr/sbin/fcronsighup fcron fcron 6755 /usr/bin/fcrontab > I will think about a way to guarantee that /etc/fcron.conf is no more than > 644 in postinst, but I have to check whether I can do that to a conffile at > all in the first place. $ sudo /etc/init.d/fcron stop Stopping advanced periodic command scheduler: fcron. ==> /var/log/syslog <== Apr 1 09:27:02 xxxxxxx fcron[18461]: SIGTERM signal received Apr 1 09:27:02 xxxxxxx fcron[18461]: Exiting with code 0 $ sudo /etc/init.d/fcron start Starting advanced periodic command scheduler: fcron. ==> /var/log/syslog <== Apr 1 09:27:04 xxxxxxx fcron[18475]: fcron[18475] 2.9.6 started Apr 1 09:27:04 xxxxxxx fcron[18475]: updating configuration from /var/spool/fcron Apr 1 09:27:04 xxxxxxx fcron[18475]: adding file systab So, it is only whining about wrong permissions (which are not actually wrong?) when fcron is installed. Namarie, - Miyo
signature.asc
Description: Digital signature
