University of California at Berkeley Department of Electrical Engineering & Computer Sciences Instructional Support Group /share/b/pub/login.help Oct 12 2016 CONTENTS Lost Your Password? Can't Login? UNIX Troubleshooting Tips "couldn't set locale correctly" error message Forgot to Logout? Blank screen on the workstation? Setting the environment for running CAD tools Lost Your Password? ------------------- If you have forgotten the password to an account on the EECS Insrtructional computers, you have to ask the IT support staff for help. See our signature at the bottom of this page for the email and office addresses. 1) Note that most of the accounts are on UNIX (Linux, MacOSX and Solaris) and on Windows. The initial password is the same on both UNIX and Windows, but it you change it on one it does not automatically change it on the other. 2) If you still have the original account form (with the original password), Then you can ask us via email and we'll reset it to the original password, on UNIX, Windows or both. 3) If you have lost the original account form, you have to visit us and show us your CAL1 student id card. We will search our records using your SID number. If you have a 'named' account, your SID card will be enough to verify that you own the account, and we will let you reset the password(s). If you have a 'class' account, we will look for your answers to the 'register' questions that should have appeared when you first logged in. That will verify that you own the account, and we will let you reset the password(s). If you did not answer the questions, we may ask you to describe some unique content in the home directory, and we may deny your request to give you the password. In the worst case, you would have to get a new account form from your instructor and start again. Can't Login? UNIX Troubleshooting Tips --------------------------------------- If your UNIX account should work but you can't login, here are some troubleshooting tips. + If the problem occurs at just one computer, it is probably just | the computer that is messed up. Please report that to the staff. | +--> If other people can't log in either, it is probably a server | or network problem. Please report that to the staff. | +----> Otherwise, your account may have a problem with: (1) password (2) disk quota (3) X Windows files To debug the problem, first try to login without X Windows: 1a) Login to another networked computer account if you have one, and try to "ssh" into your Instructional UNIX account. (You can download "ssh" for your computer from http://inst.eecs.berkeley.edu/connecting.html.) If that works, you'll know that your password is OK and your .cshrc and .login files are OK. So you have probably exceeded your disk quota. Go to step (2) below to fix that. If you are not able to login that way, you'll need help from the staff. Here's another way to login without X Windows: 1b) Go to one of our UNIX workstations in 277 Soda. At the login screen, click on the "Options" button and select "no windows", "Command line" or "FAILSAFE" from menu. Then type your login and password as usual. If you are able to login, you'll get a simple window in the middle of the screen or just a text interface. This would indicate that your password is OK and your .cshrc and .login files are OK. So you have probably exceeded your disk quota. Go to step (2) below to fix that. If you are not able to login that way, you'll need help from the staff. 2) If you could login, then check your disk usage. When you are over disk quota, you can't login using X Windows because the window manager is prevented from opening X Windows log files in your home directory. But you can still login using "ssh" because ssh doesn't need to open any log files. Check your disk quota by typing "quota" or "quota -v". If you see the word "EXPIRED", you have exceeded your quota. If that doesn't tell you anything, type "du -ks ~". You should have under 60 MB of disk usage. Here's how you can find large files that you could delete. This UNIX command displays the size (in KB) of all the subdirectories in your account: find ~ -type d -exec du -ks {} \; Look for things to delete in the large directories, such as "core" files and old files in your ~/.netscape/cache directory. These commands will delete all such files automatically: find ~ -name core -exec rm {} \; rm ~/.netscape/cache/*/* Type "more /share/b/pub/disk.quotas" for more info about disk quotas. There is also information there about additional disk space you can use, for this semester, on our /home/tmp disk. If that wasn't the problem, then your X Windows files may be at fault. Go to step (3) below to fix that. 3) UNIX and X Windows read several configuration files in your home directory when you first login. If there are errors in these files, you may not be able to login an an X Windows workstation. You can check several configuration files: Sometimes the .Xauthority or .TTauthority file gets confused. The Window manager adds information to these files to identify which SunRay you are currently using. (see "man xauth" and "man ttauth" for more information). You can delete these files using rm ~/.Xauthority ~/.TTauthority They will be recreated the next time you login at a workstation. You can also check the file permissions on the .xsession script, by typing "ls -la ~/.xsession", and you can set the permissions correctly with "chmod 755 ~/.xsession". "NAMED" ACCOUNTS: If you have editted any of the default "dot" files (.dtprofile, .twmrc, .cshrc, .login, .profile, .xsession), you can replace them from /share/b/default-named-account/ . "CLASS" ACCOUNTS: Don't change your "dot" files! Also see /share/b/pub/dotfiles.help for more information about setting up for different terminal types and keyboards. "couldn't set locale correctly" error message --------------------------------------------- The UNIX workstations and SunRays have an option for setting different character sets before logging in. If you get the error "couldn't set locale correctly" when you type commands such as 'xterm', the setting is incorrect for your needs. You can correct it yourself. Before you login, make sure the locale is set to "C" (on the Options submenu of the login screen). Other users sometimes change it, and it often reuses the last setting. Forgot to Logout? ----------------- If you forgot to logout from a UNIX system and realized it after you left the lab, here's what you can do 1) login to the same computer over the network using 'ssh' or 'putty'. 2) If you were logged in on a SunRay, you can kill the related Xsun process with the commands: ps -ef | grep $USER | grep Xsun | awk '{print $2}' | kill 3) To be sure all your processes are killed, type one of these commands (note that these commands will log you out from your current session, too): pkill -9 -U$USER ps -ef | grep $USER | awk '{print $2}' | xargs kill -9 Blank screen on the workstation? -------------------------------- If you login at a workstation in our labs and get a completely blank screen, it may be caused by a corruption of the config files for your window manager. You can fix that by logging in without windows, either via ssh or by pressing at a workstation in 27x Soda and then logging in at the text screen. Then delete the related files and directories and log in normally again. The related files and directories are typically hidden, ie they start with a dot. You can list them with the command 'ls -a'. To avoid the risk of deleting the wrong things, you can create a subdirectory and just move them there with the "mv" command, for example: mkdir old-files mv .gnome old-files mv .gnome .gnome2 .gnome2_private old-files If all is well, you can delete the old-files directory later with the "rm" command. (Carefully! Don't delete the wrong files. See 'man rm'). Here are related files and directories you might find and move: .ICEauthority .Xauthority .cache .compiz .config .dbus .dmrc .dt .dtprofile .gconf .gnome .gnome2 .gnome2_private .gstreamer-0.10 .gvfs .icons .local .pulse .pulse-cookie .qt .tgdb .xsession .xsession-* Then logout, resart the window manager () and login again to see if the problem is fixed. Other causes may include being over disk quota (type 'iquota' to check), and having an error in your login scripts (did you edit your .bashrc?). Also, you can select different window managers at the login prompt; try a different one. If that doesn't help, please ask us for help (inst@eecs.berkeley.edu). Setting the environment for running CAD tools --------------------------------------------- Here are tips if you need to customize your UNIX user environment to run programs such a Matlab, ADS, Cadence and Synopsys tools. Most of those programs have wrapper scripts in /share/b/bin/ and help files in /share/b/pub/. The wrapper script sets the environment variables for the defauilt versions on our computers, so you may not have to make any additions to that. Your GSIs should be able to refer you to the wrapper scripts needed for your class. Examples: /share/b/bin/matlab # starts the latest Matlab verison /share/b/bin/virtuoso6 # starts the latest Cadence tools Problems may arise if you add LD_LIBRARY_PATH or other variables to your UNIX login scripts (tyically .bashrc) for one CAB tool that may conflict with another tool or with remote login programs such as x2go and scp. It is best to put those addtional settings in a separate file that you can run just when you need it, and not in your login scripts where they may have unexpected side effects. For example, you could create a file called "my.bash" with this content: # run this using: source my.bash if [ -f /etc/bashrc ]; then . /etc/bashrc; fi TOOLS=`cds_root spectre`/tools LD_LIBRARY_PATH=/$TOOLS/dfII/bin/64bit:${LD_LIBRARY_PATH} LD_LIBRARY_PATH=/$TOOLS/lib/64bit:${LD_LIBRARY_PATH} MATLABPATH=/$TOOLS/spectre/matlab/64bit:${MATLABPATH} export LD_LIBRARY_PATH export MATLABPATH and load its settings by runing "source my.bash". Also, if you do mofify your login scripts (.bashrc, .cshrc, or etc), be careful to prevent any text output during non-interactive logins, such as if you use "scp" to copy files to or frm your account. The solution is usually to enclose the wordy command in a case statement that only runs if you are logging in with an interactive shell. For users with the bash shell (almost all of our users), the .bashrc code for that is if [ -z "$PS1" ]; then echo 'this print statement would break scp' fi and for users with the csh or tcsh shell, the .cshrc code for it is if ($?prompt) then echo 'this print statement would break scp' endif For more information about the CAD tools, see the help files in http://inst.eecs.berkeley.edu/software. EECS Instructional Support Group 378/384/386 Cory Hall, 333 Soda Hall inst@eecs.berkeley.edu