Quoting Riccardo Mottola (2014-04-04 15:29:06) > >> >"sendisgs stop" > > sendsigs uses killall5 which has been proven to be problematic. In > > short it does something like 'pkill -SIGSTOP . ; pkill -SIGXXX .'. > > This is problematic for a multiserver OS like Hurd, because stopping > > vital system servers will most likely also prevent killall5 from > > completing its job (e.g. killall5 used to stop procfs and then it > > tried to iterate over /proc, resulting in a deadlock). > Do we have a precedence problem here?
What do you mean by this? > >> >I shut down from console and had a remote connection open. At this point > >> >even issuing a "sync" will hang and I need to cut the machine's power > > Please be more specific when reporting this, as ideally I should be > > able to reproduce your problem. > > > > I*guess* that you meant to say: If you do not log in using telnet, > > your system shuts down fine, but if you do and then shut your system > > down, it hangs. Is that correct? > Actully, I wasn't implying that the hang is dependent on the open telnet > connection. I just said I launched shutdown and watched the progress on > the open telnet connection because it is easier and I can check it, > copy&paste stuff, etc. > With a single console (I don't get multiple consoles) it is a bit awkward. Ok, thanks for clarifying this. > I don't know yet a minimum set of action that reproduces the hang. > > I know that if I power on, login, shut down all on the local console, > the cycle ends with success. > > If on the other and I run apt-get, do some compiling and use the box, it > hangs on shutdown. It hangs even if there is no open telnet connection! > > Sometimes bugs can't be easily reproduced, sadly. One needs to gather > information in the best possible way then... Yes, thanks for reporting. Keep at it, we'll get it eventually :) Justus