Hello, Correct me if I am wrong but I am under the impression that it is at present impossible to control the order in which started init scripts are stopped during shutdown. If this is indeed the case, I believe it would be useful to add support for this - especially in case of OpenRC-based systems, on which operations formerly handled by the baselayout-1 core (e.g. LVM, dmcrypt) have got their own init scripts as well. What has brought me to think such a feature might be useful is when I noticed current OpenRC messes up the shutdown of dmcrypt volumes when rc_parallel is set to yes. As far as I can tell, what happens is that "dmcrypt stop" is called alphabetically, i.e. pretty early - and fails because the volumes in question (which happen to be this system's /usr and /var) are still busy. What do you think? I'll be happy to provide more information, should you need any. Cheers, -- MS
This is a good point. You can provide the version of openrc you're using in the subject, but i don't think it makes much difference. I'll assign it to the maintainer of openrc, maybe thay can provide some informations about this.
stop order is implicit in reverse of the start order. so if you have some dependency you arent expressing, fix your conf.d settings.
(In reply to comment #2) > stop order is implicit in reverse of the start order. so if you have some > dependency you arent expressing, fix your conf.d settings. > This is correct nothing for us to do here.
Sorry about the long silence, I've been rather busy lately. Anyhow, my two cents: > stop order is implicit in reverse of the start order. This only seems to be the case when the scripts are called sequentially, not in parallel mode... Yes, I know about the disclaimer related to this mode - it's just I've been wondering about how this problem could be addressed. > so if you have some dependency you arent expressing, fix your conf.d settings. Oh? How can I specify dependencies (in this particular case, making sure "dmcrypt stop" is only called after successful termination of "localmount stop") in conf.d? This would indeed solve the problem, then again OpenRC documentation is rather terse when it comes to the subject of configuration.
(In reply to comment #4) > > so if you have some dependency you arent expressing, fix your conf.d settings. > Oh? How can I specify dependencies (in this particular case, making sure > "dmcrypt stop" is only called after successful termination of "localmount > stop") in conf.d? This would indeed solve the problem, then again OpenRC > documentation is rather terse when it comes to the subject of configuration. Take a look at the section of /etc/rc.conf called "service configuration variables" and enable the appropriate settings in /etc/conf.d/mdcrypt. Thanks, William
