syslog beeps and logs to console.... sometimes!?

Bruce Edge bedge at troikanetworks.com
Sat Mar 24 02:04:45 CET 2001


I use syslog for debug info. It beeps and prints a:

  Message from syslogd at mead at Fri Mar 23 16:56:19 2001 ... mead cli:   
  CTREE: tokenize "cr"

type message to the console, both my xterm and text console 0 (Linux).

The behavior as to which messages beep changes depending on whether it's
running under pdb or not.

Here's my open log line, no console logging requested: 

	openlog( name, 0, LOG_USER )

Anyone else ever seen this?

This happens on 2.0 and 2.1b1.

Here's some output showing the normal syslog output interleaved with the
"Message from..." things that beep:


Mar 23 16:56:09 mead cli: INIT: loading topcmds...
Mar 23 16:56:09 mead cli: INIT: ...topcmds complete
Mar 23 16:56:10 mead cli: INIT: ...init complete

Message from syslogd at mead at Fri Mar 23 16:56:19 2001 ...
mead cli:    CTREE: tokenize "cr"

Message from syslogd at mead at Fri Mar 23 16:56:19 2001 ...
mead cli:    CTREE: ctree::tokenize tokens=['cr'], tokpos=[0], tokix=0
Mar 23 16:56:19 mead cli:    CTREE: tokenize "cr"
Mar 23 16:56:19 mead cli:    CTREE: ctree::tokenize 
Mar 23 16:56:20 mead cli:   CTREE: complete active_tok = 0

Message from syslogd at mead at Fri Mar 23 16:56:20 2001 ...
mead cli:    CTREE: parse tokix=0, active_tok=0
Mar 23 16:56:20 mead cli:    CTREE: parse tokix=0, active_tok=0
Mar 23 16:56:21 mead cli:     CTREE: getMatches self=root str=cr
Mar 23 16:56:21 mead cli:      CTREE: getLocalMatches self=root str=cr
Mar 23 16:56:22 mead cli:      CTREE: getRemoteMatches self=root str=cr
Mar 23 16:56:22 mead cli:     CTREE: parse type:0 Matches=['create']



More information about the Python-list mailing list