On 11/28/2017 09:51 AM, Tom Horsley wrote:
The only reason I'm starting things in rc.local is because
systemd can't ever start them properly because it has no idea
when the network is actually up.
Can *anyone* experiencing this problem provide more information about
it? I tried to reproduce
Tom Horsley wrote:
> On Tue, 28 Nov 2017 19:26:49 +0100
> francis.montag...@inria.fr wrote:
>
>> Why not:
> 2. Because using rc.local is 10,000 times easier than
> decrypting systemd dependency operations.
Mind you, rc.local is a systemd service itself, nothing extra special about
it:
/usr/lib
On Tue, 28 Nov 2017 19:26:49 +0100
francis.montag...@inria.fr wrote:
> Why not:
1. Because systemd should work properly and it isn't my
job to fix it.
2. Because using rc.local is 10,000 times easier than
decrypting systemd dependency operations.
3. If rc.local was actually compatible with sysv
On 11/28/2017 06:44 AM, Tom Horsley wrote:
There is no bloody rc.local script that runs on shutdown,
it exists for running stuff at boot. What has systemd
done now and how do I make it stop?
Do you have anything in rc.local? If so, it may be waiting for that
script to exit.
_
Hi
On Tue, 28 Nov 2017 12:51:58 -0500 Tom Horsley wrote:
> Aieee! The only reason I'm starting things in rc.local is because
> systemd can't ever start them properly because it has no idea
> when the network is actually up. I guess I'll have to move all
> my rc.local content to a different scrip
> Some good info at:
>
> https://github.com/systemd/systemd/issues/5497
>
> So you likely have a result with "running" when doing:
>
> systemctl status rc-local
>
> And they suggest:
>
> The only way to start a daemon in rc.local is by mean of "at -f
> now", as atd runs in a separate
> cgroup
On Tue, 2017-11-28 at 09:44 -0500, Tom Horsley wrote:
> I just rebooted my fedora 27 partition to get new kernel
> running, and I had to hit the reset button because it
> stuck here forever:
>
> A stop job is running for /etc/rc.d/rc.local Compatibility
>
> There is no bloody rc.local script that
I just rebooted my fedora 27 partition to get new kernel
running, and I had to hit the reset button because it
stuck here forever:
A stop job is running for /etc/rc.d/rc.local Compatibility
There is no bloody rc.local script that runs on shutdown,
it exists for running stuff at boot. What has sys