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

Re: ldm-6.4.0 hupsyslog


>Date: Mon, 1 Aug 2005 14:08:32 -0400 (EDT)
>From: Gabe Langbauer <address@hidden>
>Organization: Ohio State University
>To: Steve Emmerson <address@hidden>
>Subject: ldm-6.4.0 hupsyslog 

The above message contained the following:

> I just upgraded the ldm at polarmet12.mps.ohio-state.edu to ldm-6.4.0 from 
> ldm-6.3.0.  When I start the ldm now, I get the error:
> "hupsyslog: couldn't open /var/run/syslogd.pid"
> However, the ldm does still seem to handle the data correctly.
> As I recall, in the past we had to do one step of the installation as 
> root, but I do not recall seeing that on the directions this time around 
> (and I think I remember during the 6.4 briefing talk about that no longer 
> being required)  Do I have something misconfigured now that root access is 
> not required?  Do I have to chown some files back to ldm?

In general, the "make install_setuids" step is necessary and must be
executed as root.  It not done, then you'll have exactly the problem
you've encountered: no logging.

> Thanks,
> Gabe Langbauer

Steve Emmerson

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.