On 11/17/2008 12:47 AM, g wrote:
My specific solution was to simply run a root cron. But I did test sudo by disabling "#Defaults requiretty" in /etc/sudoers. Giving root ownership to a script IMHO is a security issue. Actually, the backup script probably should have been run as root via a root crontab in the first place.as a question of curiousness, and 'wat' from svr5 days, have you tried giving ownership of script to root? also, if you want backup to run only after you are logged off, or after you have done something needing backup, have script check for 'filename' and then delete 'filename' as part of closing. this way, you can run 'touch filename' to enable.
The bottom line is that things change as time goes on, and it is important that one (eg. me) keep up. Subsequently we had the exact same problem on the Boston Linux server, and as I saw the logs, I let my partner know about it since he maintains those.
-- Jerry Feldman <gaf@xxxxxxx> Boston Linux and Unix PGP key id: 537C5846 PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846
Attachment:
signature.asc
Description: OpenPGP digital signature
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
