> I didn't do it on purpose to lock up my system and risk FS corruption
> durin unclean reboot. I was interested in the server output and " 2>&1 | less"
> is the logical way to do that.
>
> I could also "solve" this problem by not running linux. And I can "solve" all
> gcc bugs by not using gcc. Those are not solutions. Not to me at least.
It's not Linux-specific, but will ALWAYS happen when you use one program
that eats all your input and pipe its output into another program that
waits for your input.
What and when do you think you will eat when you feed your dog the
sausage you want to eat yourself?
> > output into interactive programs. tail -f is a viable workaround -- and
>
> tail -f ? what is the difference between :
> $ X 2>&1 | tail -f
> and
> $ X
That you're clueless.
You'd do:
X >/my/safe/tmp/dir/X.log 2>&1 & tail -f /my/safe/tmp/dir/X.log
> > all this is off-topic on linux-kernel,
>
> non-root user locked up the console code. console code is part of kernel.
> it is a kernel topic.
Nope. Non-root user has used setuid application and thus become root.
Drop setuid privileges and use xdm/kdm/gdm if you're to avoid this.
> My own dumbness ? Did you also say that ping-of-death is not a problem ?
Ping-of-death is a kernel bug or correctness issue or whatever you call
it. This is not. root gave away the privilege to redirect console input
by installing a setuid-application, X, XFree86, Xwrapper, whatever it
may be called.
And now please take this off the list.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/