SGI uses an 'autoconfiguring' version of /etc/sendmail.cf. You can create this file with the 'configmail setup' command, but it doesn't set everything you will want. Instead, just create the file /etc/sendmail.params by hand (permissions mode 644) with the following contents:
relayname:smtp-relay rootdomain:[NULL] directdomains:chem.upenn.edu forwarder:[NULL]This should work fine (assuming the chem domain is appropriate!), other than possibly needing to edit the Cw line to add more aliases:
Cwlocalhost[NB: if you make use of ipaliasing, you WILL have to add the ipaliased hostnames onto the Cw macro line.]
Now, restart the mail programs
/etc/init.d/mail stop
/etc/init.d/mail startThen try out email, locally, and to and from another host.
The command 'mailq' shows you the pending mail queue. Look in /var/adm/SYSLOG or the appropriate mail log file to see logs of deliveries. The mail log might be directed to somewhere else (see syslog.conf; the mail logging level is set by the 'OL' macro in sendmail.cf.)
IRIX 6.5: The X-Windows features in the "Improve System Security" section are sufficient for the next step. Continue below with "Allowing X-Windows access."
Most of the configuration files for the X11 window manager xdm
are located in the directory /var/X11/xdm.
[NB: older versions of IRIX may have these files in /usr/lib/X11/xdm.]
Comment out '/usr/sbin/xhost +' or equivalent commands in the following
files:
Xsession, Xsession-remote, Xsession.dt
(this prevents anyone on the Internet from writing or reading your console screen, a pretty good idea.)
On newer IRIXes (eg 6.3), a slightly different command structure is found in Xsession and Xsession.dt. In these cases, it is possibly sufficient to make sure that the file /usr/lib/desktop/xhoston does not exist. Search for 'xhost' in these files and see the comments nearby to be sure.
In the absence of X terminals, you should look at and comment out lines in /var/X11/xdm/Xaccess, just to be safe.
Pre-IRIX 6.2 only: You should change /var/X11/xdm/Xservers to
be the following, to close a security
hole, apparently fixed as of IRIX 6.2. Note: upgrading to IRIX
6.5 with this will make the graphical display unusable.
[The following should be all one line; just the '-shmnumclients
0' part is new]:
:0 secure /usr/bin/X11/X -bs -nobitscale -c -pseudomap 4sight -solidroot sgilightblue -cursorFG red -cursorBG white -shmnumclients 0
Allowing X Windows access:
Now that your host has X Windows access turned off by default, you need to allow access to any remote hosts that need to display to your screen. For example, workstation users often log into servers and run graphical programs. The server displays the graphics to the workstation's screen. It needs to be allowed X access in order to do this. To allow a.chem.upenn.edu to display to your workstation for the current login session, enter:
xhost +a.chem.upenn.edua.chem.upenn.edu will now be able to display any programs you run on it to your workstation's screen. Under this scenario, it becomes tedious having to enter the hostnames to allow each time you log in. To fix this, enter the hosts that need to display to your screen AND that you trust to the file /etc/X0.hosts. Log out and back in for it to take effect. You can see what hosts are allowed to display to your screen at any time by entering:
xhostFYI, the following message means that a remote host tried to display to your screen, but has been turned down because it wasn't authorized by your system
Xlib: connection to "cypress.chem.upenn.edu:0.0" refused by server Xlib: Client is not authorized to connect to Server Error: Can't open display: cypress.chem.upenn.edu:0
Using /etc/X0.hosts is still somewhat tedious, because it involves
contacting a sysadmin to change the X0.hosts file. There is another
method called X authorization. X authorization lets any user allow
a remote-host to display on their screen. First, turn on usage of
X authorization (see 'xauth' manpage for more);edit xdm-config.
Change the line
DisplayManager*authorize: off
to
DisplayManager*authorize: onand reboot for it to take effect.
Now, edit .rhosts in the home directory of the account on the remote machine. Add the following line:
local_machine_hostname username
Change the permissions on the file:
chmod 600 .rhostsUsing rlogin, the remote machine will now allow the user to log in without a password. The local user can authorize the remote machine to display to the local machine with a command alias such as this:
xauthorize [user@]remotehostwhere they have the following alias set in their (csh or tcsh) shell:
alias xauthorize 'xauth extract - `hostname -s`:0 | rsh \!:1 xauth merge -'
Next page: User Account Configuration Back to table of contents