- 1.2.1. How do I change my password?
The main way to do this on the ITCS Login Service -
easiest is to use the passwd uniqname (where
uniqname is your uniqname) command from the %
prompt. If you type passwd uniqname, it will prompt you
for your old password, and then your new one twice.
The kpasswd command will also work to change your password.
- 1.2.2. How do I change my full name?
You can change your full name (what finger gives out as your
full name, and what Pine uses as your full name if you haven't
explicitly changed it in Pine) with the command:
chfn uniqname
That command will ask you for a new full name, a location, and a phone
number. If all you want to change is your full name, then just hit the
Return key for the other questions.
- 1.2.3. How can I use
tcsh as my shell?
There's a fairly simple way to do this, but there is no official
way to do this for a variety of reasons.
The solution is to add these lines to the end of your .login file:
if ( $SHELL == "/bin/csh" ) then
foreach i ($path)
if ( -x $i/tcsh ) then
setenv SHELL $i/tcsh
set shell=$i/tcsh
exec $i/tcsh -l
endif
end
endif
This sets the shell to tcsh if (and only if) it can find a copy
of tcsh on the machine.
If you really need tcsh to be the login shell, then you should
start it with the -l flag as it is done above.
- 1.2.4. How do I get the standard configuration back?
If your account has somehow been misconfigured, you can get
back the standard configuration with the command:
/usr/bin/redot
(For legacy Solaris servers, it remains: /usr/itd/bin/redot)
If you only need a specific configuration file, you can limit it
to that file by specifying the file on the command line:
/usr/itd/bin/redot .cshrc
This is usually necessary because someone deleted the files by
mistake, or because someone has old files, and they need to be
updated. The files affected are: .cshrc, .login, .logout,
.xsession, .Xresources, .mwmrc, .principals, .profile, .tvtwmrc,
.twmrc, .zephyr.subs, .zephyr.vars, and AppleVolumes.
- 1.2.5. What is Zephyr ?
The Zephyr service is a Kerberos-aware
"instant messaging service" developed at M.I.T.. It publishes your location to
others at your request. There are several significant differences
between finger and the Zephyr service. Some differences
are:
- Zephyr is an "opt-in" service, that is, you
must run the Zephyr client for others to be notified about your
login.
- The Zephyr client runs in the background, and can notify
you when people you specify log in or out. This works similar
to a "buddy list"
- Only users authenticated to the UMICH.EDU Kerberos realm
can receive information about you via the ITCS Zephyr service.
The former finger service was available to anyone.
Unfortunately, the manual pages for the Zephyr programs are much
better as a reference than a "how-to" guide. To get
started with Zephyr, you should try the following:
- Run the
zwgc command. You need to run this at
each login in order to publish your login information to other
Zephyr users, so it's probably best to run this from your
.login file in your IFS home directory.
- Run
zlocate to find a user. If the user you are
attempting to find isn't running zwgc, you will not
be able to find him/her. This is the intended behaviour.
- If you'd like to be notified immediately when another user
logs on (or off), run
znol to recieve notifications about
other users' logins and logouts. Only users specified by
uniqname in your .anyone file are watched for,
and only users who run zwgc will be seen.
See the manual page for znol for more details.
You might want to run znol on from your .login
file, if you want this to be automatic.
- If you are running
zwgc, you can receive
authenticated messages from others if they use the zwrite
command.
- Once you're comfortable with Zephyr, you can fine tune it
using the
zctl command.
- 1.2.6. How do I transfer files to and from the Login Pool?
There are a few methods of doing this.
If you have one of the Internet Access Kits supplied by
the University, you can use Fetch (on the Mac) or Rapid Filer (on
a Windows machine). Connect these to sftp.itd.umich.edu, using
your uniqname as login, and your password as password.
A better alternative is
SFTP
("secure ftp"). This is a feature of SSH.
GUI clients are available for Mac OS X and Windows. Currently (
19 September 2006) SFTP does not have University-wide support and
no GUI client is available for Mac OS 9, but it is rapidly becoming a de facto
standard.
- 1.2.7. How do I change my default editor from
pico to vi?
The best method for doing this is to change it in your .login
file. Just add the following line to the end of your .login
file:
setenv EDITOR vi
That will change the default editor to vi for you.
- 1.2.8. How can I keep that login intro message from showing up?
This is generally not recommended, because the message of the
day is there to inform you of changes and important announcements.
However, if you really don't want to see this message, there is a fairly simple way to make it
go away. The way you disable the message of the day is with a
file in your home directory called ".hushlogin".
You can create this file with the command:
touch ~/.hushlogin
You will then no longer see the message of the day. If you
want to reenable the message, just remove the file with the
command:
rm ~/.hushlogin
- 1.2.9. How can I make a screen with more lines than 24?
The resize command in Solaris 2 isn't quite as useful as the one
in the previous version of the OS, so what I would do is create
a script in a bin directory... And use that. To do that, I would
do the following:
Make a bin directory if you don't have one:
mkdir ~/bin
Edit a file called ~/bin/rs, and add the following lines:
#!/bin/csh
eval `resize`
Then change the permissions on the file to make it executable
with the command:
chmod 700 ~/bin/rs
Then, every time you find yourself with the wrong screen size,
just type rs and it will resize the screen for you.
Note that the quotes in the above command are back-quotes, not
normal apostrophes.
You can also accomplish the same thing by adding this line to
the end of your .cshrc file:
alias rs eval `resize`
- 1.2.10. How can I find my recent logins?
When you log into one of the Login or Statistics Servers, you may
notice a line like the following:
Last login: Wed Sep 16 14:35:50 1998 on frogger.rs.itd.umich.edu
from galaga.rs.itd.umich.edu (pts/6)
This tells you which machine you last logged in to in the Pool, and
from which host. The command
that takes care of this is called lslogins, and you can use
it to find out where you have logged in from recently. This is
valuable information; If you suspect someone has obtained your
account's password, you can check to see from where your account has
been used, and when. If you suspect someone has been using your
account, you should notify the ITD
User Advocate immediately. The phone number for the User
Advocate is 734-647-6396, and their email address is itdua@umich.edu. You should provide
them with as much data as possible regarding the possible compromise
of your account.
The lslogins command can be used in a few different ways:
lslogins -h
This is an optional flag for the lslogins command which requests a short
help message about the use of lslogins.
lslogins -s
The "-s" flag causes lslogins to truncate the name of the host
that the user logged into to only the machine
name, and not the fully qualified domain name.
For instance, if you logged in from amidar.gpcc.itd.umich.edu,
this flag would truncate that host name to amidar.
This is to save space and prevent the text from
wrapping on a display that is only 80 characters
wide.
lslogins -n <number>
The "-n <number>" flag requests a given number of records
returned. You should replace <number> with an actual number.
(Do not include the < >). The default is 15 if the "-n" flag
is not specified. If you use "-n 0" you will receive all records
stored. Any numbers larger than the number of logins
stored will return all the logins stored.
- 1.2.11. Why can't I to use SSH RSA authentication to log in?
RSA Authentication is disabled on the Login Pool's SSH daemon for two
reasons:
- The Login Pool uses Kerberos, a software package for
centralized identification, authentication, and authorization .
Kerberos is the University standard for
authentication.
- A user logged in via SSH RSA authentication would still need to
authenticate via Kerberos in order to access his/her
home directory. Some supported programs will not behave properly if the users' home directory is
inaccessible.
