[LDM #USJ-914724]: LDM on Snow Leopard

Dave,

Based on your email, I would have the following *two* entries in 
/etc/syslog.conf:

*.notice;authpriv,remoteauth,ftp,install,internal.none;local2.none 
/var/log/system.log
local2.*     /usr/local/ldm/logs/ldmd.log

Be sure to invoke the configure(1) script with the option 
"--enable-logging=local2".

You should know that, due to a bug in the Mac OS X kernel, downstream LDM 
processes will eventually hang.  I've been corresponding with Apple on this 
problem for about a year and a half but, so far, I haven't seen any evidence 
that Apple is addressing this issue with sufficient resources.  For more 
information, see <http://www.unidata.ucar.edu/software 
/ldm/ldm-current/known-problems.html#fcntl>.

Regards,
Steve Emmerson

> LDM supporters,
> 
> I just upgraded my LDM server (a Quad-Core Intel Mac) to Snow Leopard. I'm
> in the process of reinstalling and recompiling LDM 6.8.1, following the
> online preinstallation instructions.
> 
> I'm editing the /etc/syslog.conf file. It doesn't resemble the sample
> lines closely enough (for me, anyway) to figure out what analogous changes
> I should try to make. Here's what the file looks like:
> 
> *.notice;authpriv,remoteauth,ftp,install,internal.none /var/log/system.log
> kern.*                                  /var/log/kernel.log
> 
> # Send messages normally sent to the console also to the serial port.
> # To stop messages from being sent out the serial port, comment out this
> line.#*.err;kern.*;auth.notice;authpriv,remoteauth.none;mail.crit
> /dev/tty.serial
> # The authpriv log file should be restricted access; these
> # messages shouldn't go to terminals or publically-readable
> # files.
> auth.info;authpriv.*;remoteauth.crit              /var/log/secure.log
> 
> lpr.info                           /var/log/lpr.log
> mail.*                                  /var/log/mail.log
> ftp.*                                   /var/log/ftp.log
> install.*                          /var/log/install.log
> install.*                          @127.0.0.1:32376
> local0.*                           /var/log/appfirewall.log
> local1.*                           /var/log/ipfw.log
> 
> *.emerg                                 *
> ----------------------------------------------------------------------
> 
> So, I can add a line like "local2.debug  /usr/local/ldm/logs/ldmd.log",
> except that I have no idea if local2 is a reasonable logging facility to
> use. (Looks like local0 and local1 are used by the firewall.)
> 
> There don't seem to be any existing lines to which I might add info to
> prevent LDM from sending messages to the console, etc.
> 
> Guidance would be welcome.
> 
> (The machine is virga.sfsu.edu. Tom Yoksas has information about logging
> on as account "ldm" remotely and getting superuser privileges.)
> 
> -- Dave
> 
> ****************************************************************
> *                                      |         __ __    \|/  *
> *   Dr. Dave Dempsey                   | )   ^  /|| ||\  --0-- *
> *   Dept. of Geosciences               |) ) ^  / ||_|| \  /|\  *
> *   San Francisco State University     | ) )  /  | _ |  \      *
> *   1600 Holloway Ave.                 |)   )/   || ||   \     *
> *   San Francisco, CA   94132          | )   )   ||_||    \    *
> *                                      |)  ) )   | _ |     \   *
> *   Phone:  (415) 338-7716             |  )   )  || ||      \  *
> *   FAX:    (415) 338-7705             |)   )  )~~~~~~~~~~~~~~~*
> *   Email:  address@hidden   |  )  )  )  ~  ~   ~ ~  *
> *                                      |)  )   ) )  ~   ~  ~   *
> ****************************************************************

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: USJ-914724
Department: Support LDM
Priority: Normal
Status: Closed