This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Gilbert, re: -filelog flag for xinetd; logging would likely be as 'root' > I don't know how this could be a problem, but if it is...if it isn't > broke, don't break it. :-) Sage advice! > I thought that they, by default, went to > /home/ldm/logs anyway in a file called mcidas.log. It's actually there, > written as a zero-length file, dated September 11. If you are referring to logging of ADDE access, then the logging by the McIDAS side of things is done in a file called SERVER.LOG _if_ the 'mcadde' environment as ADDE_LOGGING turned on (i.e., the ADDE_LOGGING environment variable defined). I believe that I setup all of the weather machines to locate SERVER.LOG in ~ldm/logs. I also believe that I setup all of your machines to rotate these log files every week on Saturday night: <as 'ldm' on weather> ls -alt logs/SERVER* ls: unparsable value for LS_COLORS environment variable -rw-rw-rw- 1 ldm users 15880192 2007-09-24 11:21 logs/SERVER.LOG -rw-r--r-- 1 mcadde users 6609920 2007-09-15 00:00 logs/SERVER.LOG.1 crontab -l | grep SERVER # McIDAS ADDE Remote Server Logging 1 0 * * 6 bin/newlog logs/SERVER.LOG 3; chmod 666 logs/SERVER.LOG By the way, you can use the McIDAS application ADDEINFO to get a listing of ADDE activity on your machine(s): <as 'mcidas' on weather> cd $MCDATA addeinfo.k ADDEINFO: Start ADDE Cumulative Totals: 2007258.050101 - 2007267.162401 IP Bytes Sent Client Name -----------------+-----------+-------------------------------- 131.156.8.47 2.53D+09 weather.admin.niu.edu -----------------+-----------+-------------------------------- All 2.53D+09 62048 ADDEINFO: Done You can get more information on what can be listed from ADDEINFO using the McIDAS HELP facility: <as 'mcidas'> cd $MCDATA help.k ADDEINFO I don't know what the file 'mcidas.log' is. I don't believe that I have ever logged anything into a file named that. For McIDAS scouring I use the name mcscour.log... Cheers, Tom **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: BUT-351432 Department: Support McIDAS Priority: Normal Status: Closed