FAQ
From CTSWiki
| |
This file contains answers to Frequently Asked Questions, at this point mostly about Solaris. It will continually be updated. For questions about making the transition from Solaris 2.3 to Solaris 2.4 see Solaris 2.4 FAQ, or run /usr/openwin/bin/answerbook on a Solaris 2.4 system, and browse or search through the appropriate books.
Solaris question summary
- My .cshrc and .login don't work very well under Solaris. What should I do?
- Why can't I specify a manual section when using the man command?
- My password doesn't work. How do I change my password?
- I set my PRINTER environment variable, but some things don't seem to use it. Why not?
- Why is talk messed up?
- Why doesn't my .forward file work?
- Why doesn't my .plan show up when someone fingers me from another machine?
- How do I set up ssh2 to allow remote login without a password?
Non-Solaris Question summary
Solaris questions
My .cshrc and .login don't work very well under Solaris. What should I do?
If you're using the CTS-provided .cshrc, .xsession, etc., and they're not working as advertised, send mail to bugs. If you're not using them, and you'd like to be, enter /pkg/cts/init/install (don't worry - it will back up all files it replaces).
- Reference: CTS Help: The init System
- Reference: Sending mail to bugs
Why can't I specify a manual section when using the man command?
The format for specifying sections is man -s section command. For example:
- man -s 5 man
- From the man manpage
My password doesn't work. How do I get a new password?
Call CTS to get a new password, or send an email to bugs
I set my PRINTER environment variable, but some things don't seem to use it. Why not?
SunOS 5 uses LPDEST instead of PRINTER. Some things also use PRINTER for compatibility, but not everything.
- From the lp manpage
Why is talk messed up?
talk was never intended to work between two machines of different architectures. Use ntalk or ytalk.
- From the talk manpage
- From the ntalk manpage
Why doesn't my .forward file work?
It needs to be world-readable, and your home directory needs to be world-executable. Enter chmod a+x ~; chmod a+r ~/.forward.
- From the aliases, addresses, forward manpage
Why doesn't my .plan show up when someone fingers me from another machine?
The default for Solaris is only to show when the user was last logged in. To see a long listing (plan, login shell, when you last read mail, etc.) you have to:
- finger -l login@machine
- From the finger manpage
How do I set up ssh2 to allow remote login without a password?
(plagerizing from //tinf2.vub.ac.be/~dvermeir/manual/ssh/) We assume here your on machine myhost and you want to access somermt
- Your going to need ssh2, ssh-keygen2 and ssh-agent2
- On myhost: mkdir $HOME/.ssh2 if needed.
- On somermt: mkdir $HOME/.ssh2 if needed.
- On myhost: ssh-keygen2 this generates public and private keys, if you need to run scripts from cron, enter a null pass phrase, otherwize give a passphrase and use ssh-agent2, scripts should run from a seperate account. You should now find two files id_dsa_1024_a.pub and id_dsa_1024_a with pub readable by anyone, the other readable only by you.
- Now on myhost, create a file with: echo "IdKey id_dsa_1024_a" > identification This in combination with our pass phrase Identifies you.
- copy the myhost public key to somermt : scp2 id_dsa_1024_a.pub somermt:.ssh2/user-myhost.pub (you still need a password at this point)
- Now on somermt, create a file authorize, with : Key user-myhost.pub This file could have several entries, for every myhost1,myhost2,...
- Now run ssh-agent2 (if you have a pass phrase)
- you sould be able to ssh in to somermt from myhost with out a password prompt.
Allen 4th Mar 2002
Non-Solaris Questions
Why doesn't my .rhosts file work?
You might be using the wrong hostnames. Some destination machines require full hostnames of the source machines, like ``siesta.cs.wustl.edu, while other destination machines require the trailing ``.wustl.edu to be left off, as in siesta.cs. Eventually, all CTS-administered machines will use full hostnames, for now it's safest to include both.
- Send mail to bugs.
- Reference: Sending mail to bugs
Why doesn't /project/foo show up when I do an ls /project?
Project directories are auto-mounted. This means that they are automatically mounted when you access them, but not before. Try this:
- cd /project/foo
- cd ..
- ls
foo should now show up in the directory listing. If the directory is not used for a while it will be unmounted, and stop appearing in the directory listing again. All the directories in /project, /pkg and /opt are auto-mounted.
- From the automount manpage
