> I hope this is not too vague, but is there an established way
> to send a
> message from Linux S/390 that will show up in an OS/390
> LPAR's logs? I
> was hoping to send a message from linux to the other end of it's CTC
> channel that our ops could see (and react to).
If you have syslog enabled in USS, you should be able to use the existing
remote logging support in Linux and direct messages to a remote loghost.
Can't check right now, but I seem to remember that syslog is part of USS --
someone else please correct me if I'm on cough syrup again. Once that's
done, then you update syslog.conf to point to the USS address (from the man
page for syslog.conf:
Remote Machine
This syslogd(8) provides full remote logging, i.e. is able
to send messages to a remote host running syslogd(8) and
to receive messages from remote hosts. The remote host
won't forward the message again, it will just log them
locally. To forward messages to another host, prepend the
hostname with the at sign (``@'').
Using this feature you're able to control all syslog mes-
sages on one host, if all other machines will log remotely
to that. This tears down administration needs.
syslogd on USS grabs the message and posts it to your standard OS/390
automation. You then do the usual message automation stuff that you do for
other OS/390 messages.
This doesn't catch absolutely everything, but it gets you most of the stuff
you need. It also lets you do the same automation for non-Linux systems
too...8-)
--d b
