paul on Mon, 5 Nov 2001 09:40:09 +0100 |
> Uh... if it's running as root via cron, there's no need to have the > root password in the file and, thus, no harm in having it be > world-readable, eh? That would solve the password problem! So would giving execute permissions or ownership to a group of trusted users. Actually, I still see no reason for anyone to manually initiate a time sync. At HOME on a dial-up, once in a while I manually run "ntpdate" to sync with a time server over the Internet. This about the only case in which I would do manual syncing. > I think the original problem was that users needed to be able to > run the script at will. The real solution to the problem at hand is > a better system for time synchronization. Word. > (What's more, the original poster's email address--he's not > subscribed to the list, but was included in the Cc line for at least > *some* time--seems to have disappeared from the headers...) Oops. I was just thinking about this group. I wished that the people in my former department (job) would have recognized the value of e-mail communication beyond sending personal messages and jokes. This group is a perfect example of effective technical dialog. Although, it's more effective if you actually subscribe! 8-) ______________________________________________________________________ Philadelphia Linux Users Group - http://www.phillylinux.org Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce General Discussion - http://lists.phillylinux.org/mail/listinfo/plug
|
|