On 2015-09-07 14:54 +0200, Anselm R Garbe wrote:
> I assumed you'd use a signal, but I'm just wondering about your stop
> script, can you share it?
Currently my scripts are a mess and perhaps I should use some more
standard solutions but here it goes:
https://github.com/ypsu/desktop-configuration/
On 7 September 2015 at 13:55, Balazs Kezes wrote:
> On 2015-09-07 13:12 +0200, Anselm R Garbe wrote:
>> How do you reflect the running init process that it should re-exec
>> itself from your stop script?
>
> You mean how do I notify init? Well, I send it a signal. It should be
> quite simple to do
On 2015-09-07 13:12 +0200, Anselm R Garbe wrote:
> How do you reflect the running init process that it should re-exec
> itself from your stop script?
You mean how do I notify init? Well, I send it a signal. It should be
quite simple to do this in sinit without a new signal: just get it
reexec itse
On 6 September 2015 at 16:07, Balazs Kezes wrote:
> Still, I've added a workaround to this in my setup just in case: before
> I unmount the drives, I get init to reexec itself so that it is not
> holding references to deleted files. I added a command line argument to
> skip the initscripts and jum
Hi.
"Reexec init" is normal solution. It is used in sysvinit-based distros: every
time init is updated, init reexecs itself.
Also, probably the most beautiful solution is systemd's one: :) write special
program, which unmounts file systems and then reboots/poweroffs the computer.
Links: http:/
Hey!
Although I don't use sinit directly but I do use a very similar
minimalistic init program in which I've managed to track down a problem.
It seems sinit is also suffering from the same problem as I've seen no
workarounds in it for this.
Usually of one the last steps in shutdown/reboot phase i
