Re: problem on shut-down

[Justus Winter]

Quoting Riccardo Mottola (2014-04-02 10:42:37)
> Justus Winter wrote:
> > As a workaround, using {reboot,halt}-hurd is safe (filesystem-wise)
> > even when using sysvinit.  Using those commands avoids such problems.
> I will try!
> >
> > Then again, you should try to debug this.  See what the init script
> > does.  Inject a set -x to see where it hangs, etc.
> I tried telnetting into the box and then perfoming a couple of 
> operations (remote login seems to be stabler than the console, which 
> freezes).

telnet? Really? Wait, hang on a minute, the 80ties called and
suggested that you retrain your fingers to use the upcoming rsh
instead :p

> Some additional info:
> I tried manually "openbsd-inetd stop" and it stopped without hanging

Ok, I installed openbsd-inetd and telnetd on a test vm.  service
{start,stop} openbsd-inetd work as expected.

> I then did "poweroff &" and checked with "ps -a" where it was haning
> I noticed that almost with any script in init.d called with "stop" it 
> did hang. I then killed that process and it continued to the next, nutil 
> it came to filesystem where everything did hang. That is it looks that 
> it is not just one hanging...

I just did 'poweroff &' without and with openbsd-inetd installed, the
system shut down properly.  Note that we don't do apm or acpi, so the
system won't power down at the end.

If this does not work for you, that suggests that something is wrong
with your box.  Not sure what though :/

> I should try perhaps just booting an shuttingo down, to see how a clean 
> system works.

Are you doing anything that might trigger this that I'm missing?

> what should I do with "set -x" ? Please explain further...

Oh, I just suggested that you add 'set -x' somewhere near the top of
/etc/init.d/openbsd-inetd so that you see what is executed and when
exactly this script hangs.

Justus