| rwhod.8 (1554) | rwhod.8 (1856) |
|---|---|
| 1.\" Copyright (c) 1983, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 112 unchanged lines hidden (view full) --- 121format described above. 122.Pp 123Status messages are generated approximately once every 1243 minutes. 125.Nm Rwhod 126performs an 127.Xr nlist 3 128on | 1.\" Copyright (c) 1983, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 112 unchanged lines hidden (view full) --- 121format described above. 122.Pp 123Status messages are generated approximately once every 1243 minutes. 125.Nm Rwhod 126performs an 127.Xr nlist 3 128on |
| 129.Pa /vmunix | 129.Pa /kernel |
| 130every 30 minutes to guard against 131the possibility that this file is not the system 132image currently operating. 133.Sh SEE ALSO 134.Xr rwho 1 , 135.Xr ruptime 1 136.Sh BUGS 137There should be a way to relay status information between networks. 138Status information should be sent only upon request rather than continuously. 139People often interpret the server dying 140or network communication failures 141as a machine going down. 142.Sh HISTORY 143The 144.Nm 145command appeared in 146.Bx 4.2 . | 130every 30 minutes to guard against 131the possibility that this file is not the system 132image currently operating. 133.Sh SEE ALSO 134.Xr rwho 1 , 135.Xr ruptime 1 136.Sh BUGS 137There should be a way to relay status information between networks. 138Status information should be sent only upon request rather than continuously. 139People often interpret the server dying 140or network communication failures 141as a machine going down. 142.Sh HISTORY 143The 144.Nm 145command appeared in 146.Bx 4.2 . |