Re: [systemd-devel] Idea: adding WantsFileBefore= and WantsFileAfter=?

Ugh, looks like that message had gotten lost in spam somehow... Sorry for all the noise! -- Ryan (ライアン) Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else https://refi64.com/On Colin Guthrie , Mar 27, 2018 4:11 AM wrote:Perhaps you missed Lennart's

Re: [systemd-devel] Idea: adding WantsFileBefore= and WantsFileAfter=?

Perhaps you missed Lennart's reply? I have to say it doesn't sound like the right place to fix things. Really the daemon needs to be fixed. What you suggest sounds quite racy generally (at least the WantsFileBefore= bit anyway) and really is just to paper over a badly written daemon that also

Re: [systemd-devel] Idea: adding WantsFileBefore= and WantsFileAfter=?

I know everyone here is super busy, but I just wanted to bump this a sec before letting it die to make sure it didn't just get lost or something. (If someone agrees that it should be a feature, I'd happily try to work on it.) On Tue, Mar 20, 2018 at 4:08 PM, Ryan Gonzalez

Re: [systemd-devel] Idea: adding WantsFileBefore= and WantsFileAfter=?

On Di, 20.03.18 16:08, Ryan Gonzalez (rym...@gmail.com) wrote: > Hello!! > > Recently, I was trying to help out someone on IRC move some sysvinit scripts > over to systemd units, and there was one interesting issue that came up. > Many older daemons will create sockets at some unspecified point

[systemd-devel] Idea: adding WantsFileBefore= and WantsFileAfter=?

Hello!! Recently, I was trying to help out someone on IRC move some sysvinit scripts over to systemd units, and there was one interesting issue that came up. Many older daemons will create sockets at some unspecified point in their startup sequence, with no indication of when this occurs. In