You are not logged in.
Pages: 1
I've probably missed something easy but I'll ask anyway I've heard people mention around here backgrounding daemons on boot will make it faster, but you can't tell if they've failed or not. I've done some hacking aorund in my initscripts before and noticed the stat_bkgd() function so it's obviously something nifty. How do I go about doing this?
Thanks
Offline
how to set it? prefix whatever daemon you want to background with a @ in the DAEMONS() array in /etc/rc.conf.
Offline
yeah - not being able to see if they have failed is inevitable i think - it's logical - you want to know if they failed you have to wait and see - i guess it could log it tho - hmmmmm
Offline
yeah - not being able to see if they have failed is inevitable i think - it's logical - you want to know if they failed you have to wait and see - i guess it could log it tho - hmmmmm
Maybe add some sort of logging routine?
Such a thing could be implemented through a simple 'service' script or something,
service status gdm would go nab the status of the gdm that started earlier from the logs, or if we want to be funky and cool, there could be a status part in the /etc/rc.d/ script for GDM that checks it's status.
a service script could also be utilised for somethign like service start gdm which would run /etc/rc.d/gdm start and service stop /etc/rc.d/gdm stop.
sure its a thin wrapper, but would provide a good way of providing status information.
anyway, thats an idea, maybe i ought to post it on the mailing list tonight.
iphitus
edit: and that was my 500th post, about time i did something
Offline
easy way to see what daemons are running, and when they were started:
ls -l /var/run/daemons/
Offline
not all daemons create those files - the well written ones do
Offline
Offline
Pages: 1