You can write a server on B and a client on A that does this. Writing such clients in Perl or C isn't all that hard.
You can also use uucp over tcp/ip. That has some advantages of delivery and reporting.
But for simple tasks like this I often make use of the existing client/server tools. You are already using rexec, but did you ever think about using mail to an alias that runs a script to strip out headers and leave the body in a file? Or a printer on B that does the same thing? These kind of scripts are easy to write. Tony Lawrence
SCO Unix/Linux Resources
Thanks for the idea!....I thought of using the client-server idea much before using rexec....but just for dumping few logging messages in a file on machineB(which is already overloaded with too many processes), I didnt want to go ahead with this idea.
But, in the rexec, i felt that the password-change of machine B's login will result in the modification of my source code(i can still avoid modifying the source code, by dynamically changing the passwd). And also, it was consuming more msecs for executing this system call.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.