On 9/3/2010 10:00 AM, Keisuke MORI wrote: > 2010/9/3 Fabio M. Di Nitto <[email protected]>: >> so the current init script has: >> >>> # chkconfig: - 20 20 >> >> and that is definitely wrong. It must have slept through the crack when >> we re-did the init script a while ago. Kudos to Vladislav for noticing it. >> >> (making a bunch of assumptions here) the general rule is: >> >> stop-priority-value = 100 - start-priority-value. >> >> to guarantee the service start/stop symmetry that is pretty much the >> case for corosync. >> >> So a value of 20/80 would be correct. >> >> Now this should address the first concern reported. > > > As for the starting order, I would be grad if you could also consider > the attached patch. > > It will adjust the dependency with syslog correctly so that can > prevent a problem when you use rsyslog as I reported before: > https://lists.linux-foundation.org/pipermail/openais/2010-July/014946.html
I think this is a sane patch and should go in. The only thing that puzzles me about this requirement is that many daemons do use syslog before the daemon is available and don´t fail. All C calls to syslog returns void so there is no way to know if they succeeded or not (as sign that the daemon is running), and glibc should make that transparent. So I wonder if the issue is really corosync that needs to start after syslog or we are masking another bug somewhere else (most likely glibc). Fabio _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
