| 1 |
Yikes... guess I gotta be careful with what I add to my .bashrc... added |
| 2 |
this to root's .bashrc and locked myself out of my system! |
| 3 |
|
| 4 |
Before I exited (and then couldn't reconnect) I looked at ps -e and |
| 5 |
there were hundreds of screen/bash processes... something went haywire. |
| 6 |
|
| 7 |
Managed to rm the .bashrc with ssh ... rm .bashrc but still had to |
| 8 |
reboot to login... even restarting sshd (via webmin) didn't do the trick. |
| 9 |
|
| 10 |
So a warning to anyone who sees the previous message and tries it... do |
| 11 |
it on a local machine first (I went straight for root on my remote |
| 12 |
server... :-O) |
| 13 |
|
| 14 |
b |
| 15 |
|
| 16 |
Christian Spoo wrote: |
| 17 |
> Ben Munat schrieb: |
| 18 |
>> Well, I think the response is overwhelmingly clear: screen! |
| 19 |
>> |
| 20 |
>> I just wanted to add my 2 cents that I absolutely love screen... it has |
| 21 |
>> saved my ass countless times. The only problem is remembering to run it |
| 22 |
>> on login before starting the emerge. I suppose I really should look into |
| 23 |
>> getting bash to run it for me automatically. Anyone got a script for that? |
| 24 |
> |
| 25 |
> How about adding a |
| 26 |
> |
| 27 |
> screen -A -m -d -S <your screen name> /bin/bash |
| 28 |
> |
| 29 |
> to your ~/.bashrc ? |
| 30 |
-- |
| 31 |
gentoo-server@g.o mailing list |
Archives