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

[LDM #PXK-681085]: LDM v6.12.6 on Mac OS X v10.8.5

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: [LDM #PXK-681085]: LDM v6.12.6 on Mac OS X v10.8.5
  • Date: Sat, 17 Jan 2015 13:10:39 -0700
Dave,

> Could it be that “ps -e” lists the “grep -q syslog-ng” command, so “grep -q 
> syslog-ng” catches itself  and triggers “echo Problem found” regardless of 
> whether or not syslog-ng is running?
...
> To illustrate what I was trying to say:
> 
> ldm_virga% ps -e | grep syslog
> 18 ??         9:35.82 /usr/sbin/syslogd
> 5881 ttys003    0:00.00 grep syslog

This output of "ps -e | grep syslog" differs from what you send previously 
(which didn't show the grep(1) command).

> and
> 
> ldm_virga% ps -e | grep syslog-ng
> 7888 ttys003    0:00.00 grep syslog-ng

Yes, the "grep -e" command is seeing itself, as opposed to grep(1)s on other 
Unix systems which don't.

I've modified the installation procedure so this won't happen in the next 
release. If you want to try modifying yours, then edit the file "configure" in 
the top-level source-directory, search for the string "syslog-ng" and change 
the line

    if ps -e | grep -q syslog-ng; then

to

    if ps -e | grep -v grep | grep -q syslog-ng; then

the line

    elif ps -e | grep -q rsyslog; then

to

    elif ps -e | grep -v grep | grep -q rsyslog; then

and the line

    elif ps -e | grep -q syslog; then

to

    elif ps -e | grep -v grep | grep -q syslog; then

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: PXK-681085
Department: Support LDM
Priority: Normal
Status: Closed