Currently rc.local is executed among other services, without ordering. In order to make it safer, it could be good to start as late as possible. Replacing Type=forking with Type=idle could do the trick. Note: Colin Guthrie seems to think it could, *maybe*, cause problems: "but it's based on Type=simple, not Type=forking, so not 100% sure if that will cause some knock on problems. but it's probably worth playing with." Also, we should add as a comment in rc.local that the best way is to create a custom system unit, and maybe link to some documentation about it.
Source RPM: (none) => initscriptsWhiteboard: (none) => MGA2TOO
Does someone have a suggestion for the wording that should go into rc.local? What exactly are the "problems" that using it could cause? Is it simply the lack of a fully deterministic execution order? Type=forking seems like an odd choice, since there's no guarantee rc.local does any forking, nor leaves any PID around to track.
CC: (none) => dan, mageia
This bug report saw no action since almost 3 years ago. Is it still valid?
Keywords: (none) => NEEDINFOCC: (none) => marja11Whiteboard: MGA2TOO => (none)
(In reply to Marja van Waes from comment #2) > This bug report saw no action since almost 3 years ago. > > Is it still valid? No reply, so closing as OLD Please reopen if needed.
Status: NEW => RESOLVEDResolution: (none) => OLD