syslogd is running but it stops writing to messages. I do a "logger -p user.error Hello" and it gets to the Console Output but not to the "messages" file.
I think that it is because "messages" is written to a NFS. The NFS isn not Solaris server and it has frequent and long time delays. I think that syslogd times-out when trying to write to messages and stops trying. I have tried to "truss -p <syslogd>" and "truss logger -p user.errror Hello" but I can't see the difference between when syslogd successfully writes to messages (on one server) and when it fails on another server. Also pstack doesn't indicate when a failed write occurs.
I looked in to door status commands but they are all "C" program calls and I won't be allowed to run or develop my own "C" code....
Any ideas how I can tell that syslogd is not writing to the messages file besides using "tail -1 message" ?