If you administered GroupWise on the NetWare platform and have migrated to Linux, one thing you probably miss is the GW agents log screen. That was where I went at the first signs of trouble.
I recently had to open a SR (not for GW) and watched the engineer make use of the tail command in Linux to watch the status of a log file. If you're not familiar with the tail command, Google is your friend. Tail shows the last few lines of a specified file. When the -f parameter is used, it will monitor a file - like a log file - displaying the lines as they are added to the log file. The command the engineer used was tail -f /path/file.log
Once I understood what he was doing, I wondered if I could use the tail command to get back my GW agent logging screens. The only problem I found was that GW agents cycle the log files, and each one has a name based on timestamp...
Again, Google was my friend. I Googled something like "linux find most recent file" and had several hits. Sure enough, there was a command line ls -t *|head -1 which will list the most recent file in the directory it is run. After a little trial and error and googling, I came up with the command tail -f `ls -t *|head -1` which will monitor the most recent file in the terminal window. Now all I had to do was supply the path to the GW agent's log files.
I created separate shell scripts for the POA, MTA, GWIA, & WebAccess. Actually, the scripts are identical (except for the paths to the log files.)
tail -f `ls -t *|head -1`
Don't forget to chmod the script file to 755 so you can execute it. You could also do this in Nautilus by editing the properties of the script file. I placed a copy of the script on the desktop for easy access. When you click on the script, Nautilus will ask you if you want to run or display the file. Select 'Run in Terminal'.
I have also used this same script to monitor other services which produce a log file - dns & dhcp for example.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.