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

Re: 20021125: pqing and pqact not writing to ldmd.log

Jeff,

>Date: Mon, 02 Dec 2002 17:13:03 -0500
>From: Jeff Ator <address@hidden>
>Organization: UCAR/Unidata
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20021125: pqing and pqact not writing to ldmd.log

The above message contained the following:

> >     2.  Run them manually but logging directly to a file.  Do they work
> >     correctly?
> 
> Yes, using the -l option (which bypasses syslogd), I could log directly to
> /usr/ldm/logs/ldmd.log using both of them.
> 
> >
> >
> >     3.  Modify /etc/syslog.conf so that "local0" messages go to a file.
> >     Execute ulogger and pqing manually.  Do they log correctly?  If so,
> >     then either the pqing that you executed isn't the same as the one of
> >     the batch job, or there's something in the environment of the batch
> >     job that causes it to misbehave.  Check the log files of the pqing
> >     build process to see what libraries were linked to it.
> 
> In this case, ulogger does work, but pqact does not, so apparently
> there is some issue with going through syslogd when using pqact (and
> pqing), but not when using ulogger!?

This is very strange because both ulogger and pqing are, obstensivly,
using the same ulog module and have the same runtime environment.

What are the protections and owneship of ulogger and pqing?  Are they on
the same file system?

Regards,
Steve Emmerson   <http://www.unidata.ucar.edu>