No, write, talk, wall and message are not allowed. :( But maybe xinetd or inetd could be helpful?
xinetd and inetd are just daemons that run other network-related daemons/scripts. Yes, they could be in charge of start/stopping your daemons, but you still need to write those daemons.
Thank you. I have read that the Inetd daemon listens on specific network ports for incoming connections. After a connection has been established, the daemon sends all data to the program, that corresponds to this port. Maybe I could use this program as mediator server that receives and stores messages and later sends them to the target hosts?
Here is an image that shows how the whole construct shall look like:
Sorry, I got side-lined...
Do you mean something like the example service described here? Even so, you'd still need to write the actual code to do the message processing, even though inetd is controlling it.
However, this approach does not even use rcp, so I'm confused...
This approach is written in C, but mine should be only based on shell script. rcp is now working, but after dispatching the file I am getting the error "select: protocol failure in circuit setup". The same error message appears when I use rsh.
I found three websites that describe how xinetd shall be configurated:
Here, the files etc/xinetd.d/rsh and etc/xinetd.d/rlogin are mentioned. Do both have to be altered?
Here, the server /usr/sbin/in.rshd is referenced in the file /etc/xinetd.d/shell. Why not in /etc/xinetd.d/rsh?
Here, the server /usr/sbin/in.rshd is referenced in the file /etc/xinetd.d/rsh.
Now I am bit confused about which files have to be altered to make rcp and rsh work. When do I have to write a service in /etc/xinetd.d/login and when in /etc/xinetd.d/rlogin?