This patch adds daemontools support to the fcron init script. daemontools support also requires 2 additional executable files: /var/daemontools/fcron/run /var/daemontools/fcron/log/run daemontools does not need to be installed and it's use is optional. Default is to use daemontools if it is installed. This seems reasonable.
Created attachment 17853 [details, diff] Patch for fcron init script to support daemontools if installed
Created attachment 17854 [details] /var/daemontools/fcron/run
Created attachment 17855 [details] /var/daemontools/fcron/log/run
I wish you guys will try and make up your minds. First its to not use the 'evil init.d' whatever that means, now you want support to some rc-scripts. I am not really for hacks like this - either we add some sort of daemontools support back to runscript.sh so that we do not need to add ugly hacks like this to every rc-script, or you use daemontools without the rc-script like the original cry went out for.
Bit harsh after reading it again, but I do not think hacking the same basic thing to a dozen scripts is very productive.
Ok, I read new comments to bug #28294 =) Sorry, will try to read all the new load of bugs before commenting next time. It is fairly late though from work - sorry. Anyhow, I still think duplicating code is not the way. Doing some runscript.sh and functions.sh support code changes will be the better way. I will try to get an patch out for review as soon as possible.
Yes, sorry azarah. I think we had a bit of misunderstanding there to begin with. Mark managed to convince me about what you were originally trying to convey. I agree that adding some generic mechanism for init.d is the right thing to do. I look forward to seeing your patch :-).
hi. please have a look at this ebuild: http://dev.gentoo.org/~kaiowas/portage_overlay/sys-apps/svc-scripts/svc-scripts-0.0.3-r1.ebuild this would solve the daemontools integration with gentoo in a very simple way. no need to hack a lot of init scripts. I would be happy to maintain this new ebuild and add scripts received/needed by users. Please tell me if it suits your needs, and I will commit it to portage. * description it's a sys-apps/supervise-scripts rewrite with full selinux support. it also has a long list of supervise scripts provided as samples (IUSE="withsamplescripts") * use svcinit <service_name> <command> <service_name> is one of the services from /services or /var/services (paths have been inherited from supervise-scripts for maximum compatibility), or the 'all' keyword <command> is one of start, stop, restart, status, add, remove * compatibility compatible with sys-apps/supervise-scrips maximum ease of use in a selinux environment (run_init doesn't have to be used, 'status' command actually works compared to svc-status) * needs a line in use.local.desc: sys-apps/svc-scripts:withsamplescripts - Provides a number of supervise scripts as examples
So, WONTFIX? Really stale bug.
Petre, you still have that ebuild of yours around ? Sorry I did not comment, but it seems like in the time I was MIA.
my ebuild has moved to sys-process/supervise-scripts in the public portage tree
I ment sys-process/daemontools-scripts
In sys-process/daemontools-scripts.
