From: <pa...@rc...> - 2000-12-24 04:14:33
|
Joe Piolunek wrote: > I think David would like users to be able to start a copy of the daemon, so > could you make that easier? /var/lock/subsys is only writable by root, so a > user's lock file would need to go somewhere else. Although I think it should be OK for non-root users to start ptal-printd, the init script and .conf file are special in that they indicate the "official" policy for a system, so I think it's OK that they are root only. Timothy Lee wrote: > The script was written with root in mind: to make administrating the > system easier. It doesn't stop the user from running a local copy of > the darmon. (But it *will* kill all daemons when stopped.) In other words, users can run the daemon directly, but not the init script. If the init script is called to stop ptal-printd, then all instances of the daemon are killed, even those started without the init script. Sounds reasonable to me. Timothy Lee wrote: > The script now checks for ptal-printd and the config file before > launching the daemon and reporting success. It's hard to check for > errors because the daemon doesn't fork itself and return. (Maybe it's a > feature David will consider adding??? <grin>) Yes, I'll fix that. Would it make more sense to fork or not fork by default (changeable by a command-line option)? David |