Table of Contents
Advertisement
System Set-Up and Operation
Sun 100/150 Installation Manual
6.13. Making Local Modifications
Locally written commands are kept in /u,r/,rc/local and their binaries are kept in /u,r/local.
This allows
/u,r/bin, /u,r/ucb,
and /bin to correspond to the distribution tape (and to the sys-
tem manuals). People wishing to use /u,r/local commands should be made aware that they
aren't in the base manual.
A
/u,r/iunk
directory to throw garbage into, as well as binary directories /u,r/old and
/u,r/new
are useful. The man command supports manual directories such as
/u,r/man/manj
for junk
and /
u.r/ man/ manl
for local manual page entries to make this or something similar practical.
6.14. Accounting
Optionally,
UNIX
records two kinds of accounting information: connect-time accounting and
process-resource
accounting.
Connect-time
accounting
information
is
stored
in
the
/u,r/adm/wtmp file, which is summarized by the program /etc/ac (see ac(8)). Process-time
accounting information is stored in /
u.r/ adm/ acet,
and analyzed and summarized by the prc>-
gram / etc/.a (see .a(8)).
If you need to charge for computing time, you can implement procedures based on the informa-
tion provided by these commands. A convenient way to do this is to give commands to the
clock daemon / etc/
cron
to be executed every day at a specified time. This is done by adding
lines to /u.r/lib/crontab; see
cron(8)
for details.
6.15. Resource Control
Resource control in the current version of
UNIX
is rather primitive. The resources consumed by
any single process can be voluntarily limited by the mechanisms of .etrlimit(2). Disk space
usage can be monitored by
duel).
No system-enforced procedure for controlling a user's disk
space usage is implemented under the current system, although a modicum of control can be
obtained by dividing user groups between dHferent disk partitions.
0.10.
Network Troubleshooting
If you have anything more than a trivial network configuration, from time to time you are
bound to run into problems. Before blaming the software, first check your network connections.
On networks such as the Ethernet a loose cable tap or misplaced transceiver cable can result in
severely deteriorated service. The netltat(8) program may be of aid in tracking down hardware
malfunctions .. In particular, look at the -i and
-B
options on the manual page.
If
you believe you have a faulty coaxial Ethernet cable, test the cable to make sure it is deliver-
ing 50 ohms: remove the terminator from the N-connector on the transceiver terminating the
cable, and use an ohm meter to test resistance (use the pin 'inside' the N-connector for signal,
and the housing as ground). If you are getting something other than 50 ohms, your cable may
be damaged. Contact Sun Microsystems for assistance.
If you believe the routing daemon is malfunctioning, its actions - and even all the packets sent
and received -
may be printed out. To create a log file of routing daemon actions, just supply
a file name when you start the daemon up, for example:
#:
/etc/routed /etc/routerlog
6-26
Revision
H
of
12
March
1984
Advertisement
Chapters
Table of Contents
Troubleshooting
