[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[TIGGE #LJA-831211]: Fwd: [Fwd: Re: ldm can not write to /home/ldm/logs or /TIGGE/dasg011]
- To: schuster@xxxxxxxx
- Subject: [TIGGE #LJA-831211]: Fwd: [Fwd: Re: ldm can not write to /home/ldm/logs or /TIGGE/dasg011]
- From: "Unidata IDD TIGGE Support" <support-idd-tigge@xxxxxxxxxxxxxxxx>
- Date: Fri, 28 Aug 2009 10:58:08 -0600
- Delivered-to: support-idd-tigge@unidata.ucar.edu id 9E6F3CB18D; Fri, 28 Aug 2009 10:58:15 -0600 (MDT)
Doug,
Just to amplify Tom's advice: 1) ensure that the "bin/hupsyslog" utility is
owned by root and setuid; and 2) execute "bin/hupsyslog" before trying the
logger(1) test.
You should be able to use the lsof(1) utility to determine if the system
logging daemon has the LDM log file open.
Regards,
Steve Emmerson
Ticket Details
===================
Ticket ID: LJA-831211
Department: Support IDD TIGGE
Priority: Normal
Status: Closed
