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

20010110: McIDAS-LDM: Syslogd HUP fails on LDMADMIN Start

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: 20010110: McIDAS-LDM: Syslogd HUP fails on LDMADMIN Start
  • Date: Wed, 10 Jan 2001 17:35:23 -0700
>From: Michael Keables <address@hidden>
>Organization: Geography Dept, University of Denver
>Keywords: 200101102326.f0ANQbo04873 LDM hupsyslog

Mike,

>In an earlier email you mentioned that Solaris has a problem with
>syslogd hanging up (which was why I was not getting ldm log output.)

Right.

>You suggested that I may need to logon as root, kill the daemon, and
>then restart it.

Yes.

>I had to do just that today, and now find that each time I restart the
>ldm using ldmadmin start, the HUP to syslogd fails due to a permission
>error (I must have inadvertently reset the permission when I launched
>syslogd.) What should the permissions be for /usr/sbin/syslogd so that
>ldm can kill and then restart it?

Both rpc.ldmd and hupsyslog have to have set uid root permisson set.

The following was extracted from the LDM installation checklist page:

http://www.unidata.ucar.edu/packages/ldm/ldmBinaryInstallList.html#s7

<login as root>
% cd ~ldm/{version-directory}/bin
% chown root rpc.ldmd
% chown root hupsyslog
% chmod u+srwx,g+rx,o+rx rpc.ldmd
% chmod u+srwx,g+rx,o+rx hupsyslog

>Thanks in advance.

No problem.

Tom