Lines Matching +full:multi +full:- +full:system

30 .Sh 1 "System operation"
32 This section describes procedures used to operate a \*(4B UNIX system.
33 Procedures described here are used periodically, to reboot the system,
35 system performance, recompile system software and control local changes.
38 In a normal reboot, the system checks the disks and comes up multi-user
42 This will leave the system in single-user mode, with only the console
46 you must enter the root password to bring the machine to single-user mode.)
48 and then to return to single-user mode by signaling
52 To bring the system up to a multi-user configuration from the single-user
54 all you have to do is hit ^D on the console.  The system
57 a multi-user restart script (and
67 Unless the system was taken down cleanly, you should run
68 ``fsck \-p'' or force a reboot with
72 To take the system down to a single user state you can use
79 when you are running multi-user.
82 system is taken single-user.  If you wish to come up multi-user again, you
86 \fB#\fP \fI/sbin/umount -a\fP
90 Each system shutdown, crash, processor halt and reboot
91 is recorded in the system log
95 When serious errors occur on peripherals or in the system, the system
98 by the system error logging process
100 and written into a system error log file
112 Error messages printed by the devices in the system are described with the
117 (e.g. with the command \fItail \-r /var/log/messages\fP).
127 should be used to get the system to a state where a filesystem
131 since once the system is going it is easy to
135 You should arrange to do a towers-of-hanoi dump sequence; we tune
148 so that dump can notify logged-in operators when it needs help.
208 Exhaustion of user-file space is certain to occur
234 program uses an ``in-place'' algorithm that
257 Bring the system down.
263 root filesystem as you did when first installing the system.
268 drivers they should also be added to the standalone system in
273 .Sh 2 "Monitoring system performance"
277 program provided with the system is designed to be an aid to monitoring
280 when the system is active you can judge the system activity in several
286 out at 20-30 tps in practice), and the user cpu utilization (us) should
289 If the system is busy, then the count of active jobs may be large,
292 be non-zero).  It is healthy for the paging demon to free pages when
298 when the system is busy, you can find
301 is overloaded or imbalanced.  If you have several non-dma
303 that are doing high-speed non-buffered input/output, then the system
304 time may go high (60-70% or higher).
305 It is often possible to pin down the cause of high system time by
307 activity (in) and per-device interrupt counts,
308 or system call activity (sy).  Cumulatively on one of
309 our large machines we average about 60-200 context switches and interrupts
310 per second and about 50-500 system calls per second.
312 If the system is heavily loaded, or if you have little memory
313 for your load (2M is little in most any case), then the system
315 reduction in system performance and pregnant pauses when interactive
317 If you expect to be in a memory-poor environment
319 limiting system load.
320 .Sh 2 "Recompiling and reinstalling system software"
322 It is easy to regenerate either the entire system or a single utility,
323 and it is a good idea to try rebuilding pieces of the system to build
326 In general, there are six well-known targets supported by
327 all the makefiles on the system:
363 may be mounted read-only by multiple machines.
367 system except for the contributed, old, and kernel software.
369 The system consists of three major parts:
391 If you want to mount your source tree read-only,
423 Note, if system include files have changed between compiles,
428 The entire library and utility suite for the system may be recompiled
435 This target installs the system include files, cleans the source
437 the system utilities.
473 If you modify the C library or system include files, to change a
474 system call for example, and want to rebuild and install everything,
520 /usr/local/man/cat[1-8] to encourage this practice (see
552 been incorporated in the system and allow control over the
561 To use the disk quota facilities, the system must be
591 (default seven days) the system then treats the soft limit as a
596 exceeded the system will generate a message on the user's terminal.
610 In particular, look at the \fB\-i\fP and \fB\-s\fP options in the manual page.
616 system will trace all traffic and internal actions (such as timers
621 Most of the servers distributed with the system
622 accept a \fB\-d\fP option forcing
627 We conclude the discussion of system operations by listing
628 the files that require periodic attention or are system specific:
640 /etc/rc.local	local system restart script; runs reboot; starts daemons
652 /var/log/messages	system error log