Quote:
IP Messenger may be what you are looking for:
|
Ooo, boy, talk about a sparse web page.
No screen shots, no online docs, nothing.
Not to mention the app is in GTK, which I prefer to avoid.
Quote:
If you like to code in Perl then you didn't need me to list this
|
Perl is a foreign language to me.
Oof! That thread is from the year 2001!
Quote:
The thing is wall is based on broadcasting to all users on a host - not broadcasting to all hosts on a Lan.
|
True, and that is where rwall enters the picture. rwall will intercept messages broadcast across a LAN and then use wall to relay the message locally. There also is rwho, which can reveal all current login sessions across the LAN. Seems rwall could send messages in a shotgun approach --- to everything everywhere, or the information from rwho could be used to send a LAN broadcast message only to certain users.
Quote:
Sorry if I offended anyone
|
You did not offend me. Offering ideas is how solutions are found. People might not agree with each specific idea, but such conversations act as a catalyst toward finding a palatable solution a person seeks. Not to mention I learned something new about netcat. Thanks for helping!
Quote:
The requirement got me searching for "ready made" solutions and none was forthcoming - in fact I found more solutions for Windows networks. To me it would seem quite a common requirement and I was surprised there didn't seem to be a ready made product.
|
Bingo. There is no ready-made solution. Seems odd to me too, especially considering Unix is 40 years old and Linux systems are almost 20. As I mentioned previously, the shutdown command displays a shutdown message, but the design is limited to the mainframe way of connecting users, not the modern way of using a LAN. That is, the broadcast message is local to the server and not to the LAN.
Quote:
Now, Java version is only open to public in Japanese Page
|
I don't read Japanese.
Also, seems Java might be a tad heavy for a simple messaging system. The KDE popup I receive from a wall message is crude but functional. Nonetheless, thanks for finding the links!
I think the rwalld and rwhod tools probably provide the basics of what I was seeking originally.
One caveat I noticed after posting yesterday. When I exited X/KDE, there were a slew of messages appearing suddenly in tty1, which is where I logged in and started X/KDE. Apparently those test messages I had sent on my LAN went to tty1 in addition to my Konsole terminal and KDE popup and other machines on the LAN. No damage done, but sloppy. As of yet, I don't see a way to fine tune the process except by using rwho to pinpoint where messages should be sent. I don't know whether I can further limit to which tty the message is sent.
I also have not yet figured out how to get rwalld in Slackware to work with /etc/netgroup. I don't know whether the problem is my not understanding syntax correctly, or the version provided with Slackware does not support the
-n option.