From: Timothy L. <ti...@wo...> - 2000-12-22 04:04:26
|
First off, Dag, sorry about the HTML format. I've made some changes to the script, and this time I'm including it as an attachment -- hope that solves the problem. Guess I'll stick to text format with this list just so everyone could read the stuff... <grin> Joe Piolunek wrote: > The script reports success even if the daemon doesn't really start. It > happened when the paths were incorrect. Add some error control features > and/or a message to indicate failure if it occurs. Don't create a lock file > unless the daemon sucessfully starts. > 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>) > 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. > 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.) Timothy Lee |