[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[McIDAS #BUT-351432]: How do I keep McIDAS-XCD message logs out of /var/log/messages?

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.

  • Subject: [McIDAS #BUT-351432]: How do I keep McIDAS-XCD message logs out of /var/log/messages?
  • Date: Mon, 24 Sep 2007 08:48:26 -0600
Hi Gilbert,

re:
> I am seeing this in /var/log/messages:
> 
> Sep 23 17:18:01 weather xinetd[2632]: EXIT: mcidas status=0 pid=23953
> duration=0(sec)
>
> Every minute with a process happening. This is normal and expected,

Interesting.  I had never looked for these messages in /var/log/messages...

> but
> I'd rather put it in a file in /home/ldm/logs. How can I do this?

A quick check of the man page for xinetd on weather shows that there is
a flag that should be able to be used to specify where logging will
occur:

       -filelog logfile
              xinetd-produced messages will be placed in the specified file.
              Messages  are  always  appended to the file.  If the file does
              not exist, it will be created.  This option is ineffective  in
              debug  mode since all relevant messages are sent to the termi-
              nal.

I would assume that one would have to modify the /etc/init.d/xinetd script
to include the use of the '-filelog' flag.

Please remember that the log file that will be written will likely be
owned by 'root'.  This may or may not cause problems for you down the road.

> Thanks and take care. Oh, Weather.admin.niu.edu was down this past
> Friday-Saturday when a storm blew through here and took out the power,
> resulting in scrambled hard drive files. After a reboot and an
> automatic/automagic file system check, all is well now.

OK, thanks for the heads-up.
 

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