You are not logged in.
You know what my problem is: Xorg is prone to locking up instead of terminating itself if something goes wrong, and I've been messing around with evdev in preparation for use of a new trackball, leading to several such lockups.
I don't have another *nix box and I don't run SSH... So I'm wondering, is there a way to bind 'killall -9' to a keystrong - I'm thinking ctrl-alt-break would be best - using only bash, so that I could instantly kill whatever app was in the foreground without fail?
Offline
if you dont have another *nix box does that mean you've got a windows box? theres something called putty that will ssh to a *nix box from windows, I've used it before.
Just making an observation. Sorry I don't know the answer to your question (I'm pretty new to linux myself) - but it sounds like this might be useful to you from reading your post.
Offline
How do you define foreground, exactly?
Offline
Just use Magic SysRq.
Offline
Okay, two problems:
- I really, really, really do not want to run SSH. That would open me up as a potential target for hacking.
- Isn't magic SysRq not all that secure? And does it even allow you to terminate something that's frozen up completely?
Offline
Okay, two problems:
- I really, really, really do not want to run SSH. That would open me up as a potential target for hacking.
Please use the correct term (cracking). You can set ssh up so that it only allows you to log in from certain machines or IPs. Of course, it may theoretically be possible for your friendless neighborhood cracker to spoof the IP, I suppose.
Dusty
Offline
Just use Magic SysRq.
How would one do that? I think I know what you are talking about, but I've never used them.
Offline
Magic SysRq could be called insecure only due to the fact, that someone who has a physical access to your PC could shutdown it or kill processes on given tty. But firstly, he would have to know how to actually do it, secondly, he could press power button or unplug the power cord anyway. On the other hand, when it comes to freezes, SysRq is invaluable (it is intercepted directly by kernel, so it doesn't work only if kernel itself is locked).
Google for it or search the forum, I remember I had explained it at least once around here, but can't seem to find that topic (who steals my data, argh?).
Offline
The reason why magic sysrq is left off, is that apparently it can be sent remotely, via ssh or whatever. But I guess if someone has got into your SSH, magic sysrq is the last thing you will be worrying about.
I'd enable it, its damned useful and has saved me from rebooting countless times, and prevented me from hard rebooting the computer and risking FS damage.
iphitus
Offline
Thanks.
Offline
The reason why magic sysrq is left off, is that apparently it can be sent remotely, via ssh or whatever. But I guess if someone has got into your SSH, magic sysrq is the last thing you will be worrying about.
I'd enable it, its damned useful and has saved me from rebooting countless times, and prevented me from hard rebooting the computer and risking FS damage.
iphitus
I'm sure there have been a couple time I could have used this knowledge. Please explain
Offline