ps and wall; How do they work?
Doug Gwyn
gwyn at smoke.BRL.MIL
Sun Sep 16 10:50:17 AEST 1990
In article <1990Sep15.132001.28596 at virtech.uucp> cpcahil at virtech.UUCP (Conor P. Cahill) writes:
-Doesn't wall(1) just send messages to terminals that users are logged
-into? Then there shouldn't be a problem with printer or other comm
-ports where user's are not logged in.
I didn't say that the printer hadn't been logged in. Users with hardcopy
terminals (e.g. letter-quaility) have used them for printing nroff output
for quite a long time now. A side effect of a reasonable nroff with
output sent to such a printing terminal is that the equivalent of "mesg n"
is performed to block "write" and "wall" during printing.
-To handle the case where a comm program is initiated once the connection
-is established, the comm program should be able to handle (and ignore)
-the noise generated by the message. If that is not feasible, perhaps
-a solution where the process turns off the "owner-write" permission
-bits (this is not what mesg -n does) on a tty and write is modified to
-not send a message to this port. I don't think this is necessary.
You're getting too elaborate. All that is necessary is for "mesg" and
"write"/"wall" to cooperate.
More information about the Comp.unix.questions
mailing list