Re: HELP: FATAL SERVER ERROR
In article [EMAIL PROTECTED], Albert Hurd [EMAIL PROTECTED] wrote: This newbie would like some help with the following problem: Okay. Follow closely. It began with a cd to /tmp All right so far. and then a rm -r /tmp. You must have been root at this time? /tmp is pretty much necessary for the system to operate. The rm -r command means remove the following directory and everything inside it. That's what killed your system. I then wanted to cd ~ but You can just say cd. If you don't specify where you want to go, cd will take you to your home directory by default. did cd ` byy mistake. This replaced the usual prompt $ by . The prompt is bash's way of asking you for more input to complete the command. Back-quotes need to come in pairs in bash commands, so bash assumed your command was not finished, and asked you for more. In that situation, just press CONTROL-C to abort the command and get your usual prompt back. I then tried to get a new xterm window by clicking the afterstep icon. Nothing happened. Since you'd zapped /tmp, which is where the X server keeps its socket (the connection point for new X programs which want to display on your screen), the new xterm you started could not connect to that socket, and so could not display itself on your screen, instead bombing out without being able to tell you what was happening. I then rebooted and got the the following when I tried startx: Fatal server error: Could not create lock file in /tmp/.tX-lock That was because /tmp didn't exist! Incidentally, rebooting was rather a drastic measure. You should have first tried CONTROL-ALT-BACKSPACE to abort your X session, and then run startx again. Only, in this case, that would have failed, too. Could anyone tell me what happened Hope this helped. and how to recover. Thanhs so much. As Joey said, become root and say mkdir /tmp; chmod 1777 /tmp Make sure you do not use your computer as root as a matter of course; use a different user ID for day-to-day usage, and become root only when necessary to do system administration. That will help avoid accidents like the one you described. -- Charles Briscoe-Smith White pages entry, with PGP key: URL:http://alethea.ukc.ac.uk/wp?95cpb4 PGP public keyprint: 74 68 AB 2E 1C 60 22 94 B8 21 2D 01 DE 66 13 E2 PS: If my messages seem late or out-of-date, it's because I'm communicating in batch mode via floppy-disk-net! -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
HELP: FATAL SERVER ERROR
This newbie would like some help with the following problem: It began with a cd to /tmp and then a rm -r /tmp. I then wanted to cd ~ but did cd ` byy mistake. This replaced the usual prompt $ by . I then tried to get a new xterm window by clicking the afterstep icon. Nothing happened. I then rebooted and got the the following when I tried startx: Fatal server error: Could not create lock file in /tmp/.tX-lock -X11TransSockeetUNIXConnect: Can't connect: errno=2 xinit: No such file or directory (errno=2): unable to connect to X server xinit: No such process (errno=3): Server error Could anyone tell me what happened and how to recover. Thanhs so much. Albert Hurd -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: HELP: FATAL SERVER ERROR
Albert Hurd wrote: Could anyone tell me what happened and how to recover. Thanhs so much. As root: mkdir /tmp chmod 1777 /tmp -- see shy jo -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: HELP: FATAL SERVER ERROR
Albert Hurd [EMAIL PROTECTED] writes: It began with a cd to /tmp and then a rm -r /tmp. I then wanted to cd ~ but did cd ` byy mistake. You removed your /tmp dir. The Xserver (and other programms) save temporary data in it, so you get into problems as you saw by yourself. If you want to delete the contents of a directory and all its subdirectory, then you can do this by: cd /tmp rm -R * I wouldn't do this as root (and probably also not as a normal user) as you will delete some important temporary data. All files older than 3 days got wiped from /tmp during boot anyway (see /etc/init.d/boot). For servers who usually don't reboot (sometimes for months), there is also tmpripper in hamm. Better to selectively delete files and directories (using mc for example). So create a new /tmp dir with these permissions: drwxrwsrwt 6 root root 2048 Feb 15 21:48 /tmp/ See man chmod for help on setting the right permissions. This replaced the usual prompt $ by . I then tried to get a new xterm window by clicking the afterstep icon. Nothing happened. I then rebooted and got the the Don't know afterstep, but the prompt means, that the shell expects forter data from you . By ' you started a string. Try CTRL+c next time to get out of this prompt. Ciao, Martin -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
