Broadcast Message from root (pts/int) on server
[date]
Cause
This message from the wall(1M) command is transmitted to all users logged into a
system. You could see it during a rlogin(1) or telnet(1) session, or on terminals
connected to a timesharing system.
Action
Carefully read the broadcast message. Often this broadcast is followed by a
shutdown warning.
#############################################################################
Broken pipe
Cause
This condition is often normal, and the message is merely informational (as when
piping many lines to the head(1) program). The condition occurs when a write on a
pipe does not find a reading process. This usually generates a signal to the executing
program, but this message displays when the program ignores the signal.
Action
Check the process at the end of the pipe to see why it exited.
Technical Notes
The symbolic name of this error is EPIPE, errno=32.
#############################################################################
Bus Error
Cause
A process has received a signal indicating that it attempted to perform I/O to a
device that is restricted or that does not exist. This message is usually accompanied
by a core dump, except on read-only file systems.
Action
Use a debugger to examine the core file and determine what program fault or system
problem led to the bus error. If possible, check the program’s output files for data
corruption that might have occurred before the bus error.
Technical Notes
Bus errors can result from either a programming error or device corruption on your
system. Some common causes of bus errors are: invalid file descriptors, unreasonable
I/O requests, bad memory allocation, misaligned data structures, compiler bugs, and
corrupt boot blocks.
[date]
Cause
This message from the wall(1M) command is transmitted to all users logged into a
system. You could see it during a rlogin(1) or telnet(1) session, or on terminals
connected to a timesharing system.
Action
Carefully read the broadcast message. Often this broadcast is followed by a
shutdown warning.
#############################################################################
Broken pipe
Cause
This condition is often normal, and the message is merely informational (as when
piping many lines to the head(1) program). The condition occurs when a write on a
pipe does not find a reading process. This usually generates a signal to the executing
program, but this message displays when the program ignores the signal.
Action
Check the process at the end of the pipe to see why it exited.
Technical Notes
The symbolic name of this error is EPIPE, errno=32.
#############################################################################
Bus Error
Cause
A process has received a signal indicating that it attempted to perform I/O to a
device that is restricted or that does not exist. This message is usually accompanied
by a core dump, except on read-only file systems.
Action
Use a debugger to examine the core file and determine what program fault or system
problem led to the bus error. If possible, check the program’s output files for data
corruption that might have occurred before the bus error.
Technical Notes
Bus errors can result from either a programming error or device corruption on your
system. Some common causes of bus errors are: invalid file descriptors, unreasonable
I/O requests, bad memory allocation, misaligned data structures, compiler bugs, and
corrupt boot blocks.
No comments:
Post a Comment