On Do, 2009-09-17 at 19:15 +0000, Scott James Remnant wrote:
> If you open another console and do: > > killall -USR1 mountall > > does it output more stuff? If so, attach that.
I didn’t reboot anew, because that’s really cumbersome. This is via SSH now:
usr1_handler: Received SIGUSR1 (network device up)
> Then if that does something, try: > > status udev > (if running, "start udevtrigger", if not running, "start udev" then > udevtrigger)
root@sams:/# killall -USR1 mountall root@sams:/# status udev udev start/running, process 28029 root@sams:/# start udevtrigger ^C
... I had to Ctrl-C it, it was stuck. Then ...
root@sams:/# status udev udev start/running, process 28029 root@sams:/# status udevtrigger udevtrigger start/starting
... and no change in the console with mountall running.
What now?
--Tobias
On Do, 2009-09-17 at 19:15 +0000, Scott James Remnant wrote:
> If you open another console and do:
>
> killall -USR1 mountall
>
> does it output more stuff? If so, attach that.
I didn’t reboot anew, because that’s really cumbersome.
This is via SSH now:
usr1_handler: Received SIGUSR1 (network device up)
> Then if that does something, try:
>
> status udev
> (if running, "start udevtrigger", if not running, "start udev" then
> udevtrigger)
root@sams:/# killall -USR1 mountall
root@sams:/# status udev
udev start/running, process 28029
root@sams:/# start udevtrigger
^C
... I had to Ctrl-C it, it was stuck. Then ...
root@sams:/# status udev
udev start/running, process 28029
root@sams:/# status udevtrigger
udevtrigger start/starting
... and no change in the console with mountall running.
What now?
--Tobias