[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::seal

Title:	SEAL

Moderator:	GALVIA::SMITH

Created:	Mon Mar 21 1994
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1989
Total number of notes:	8209

1866.0. "wwwproxy.log has telnet log info in it." by CSC32::GLAUNER () Fri Mar 14 1997 19:11

    Why would there be telnetxd  
    and smtpxd records in the wwwproxy.log in altavista firewall for unix
    I don't know which version yet.  Any pointers would be wonderful.
    
    thanks
    Ray
    wwwproxy.log belwo                                               
                                                                                    
    Jan  7 10:28:07 bluekeeper telnetxd[14090]: Log: REPORTSTATS: user
    'thompson'   
    local host 'ith212.clarityconnect.com/206.64.143.212' remote host               
    'FASTER.CORNING.COM/149.42.16.98' imported 227164 bytes, exported 904
    bytes,    
    in 1214 seconds                                                                 
    Jan  7 11:36:11 bluekeeper smtpxd[25683]: Log: REPORTSTATS: user
    'postmaster'   
    local host 'bluekeeper.corning.com/199.197.129.1' remote host                   
    'mail.clarityconnect.com/206.64.143.5' imported 304 bytes, exported
    1224        
    bytes, in 3 seconds                                                             
    Jan  7 15:11:36 bluekeeper telnetxd[30073]: Log: REPORTSTATS: user
    'thompson'   
    local host 'ith154.clarityconnect.com/206.64.143.154' remote host               
    'FASTER.CORNING.COM/149.42.16.98' imported 1054 bytes, exported 140
    bytes, in   
    135 seconds

T.R Title User Personal
Name Date Lines

1866.1 CHEFS::espol1.gmt.dec.com::PITT Gone with the winsock ... Mon Mar 17 1997 07:31 12

T.R	Title	User	Personal Name	Date	Lines
1866.1		CHEFS::espol1.gmt.dec.com::PITT	Gone with the winsock ...	`Mon Mar 17 1997 07:31`	12
	There is a (very long-standing) bug in Digital UNIX syslogd that causes it to put log information in the wrong log file. It happens most often when syslog is very busy logging to disk. I have observed this very frequently when one has an internal packet screen machine receiving a copy of the firewall log files - it very often breaks the information up incorrectly into different file. I have no idea whether this bug has ever been logged, or what versions are affected, or whether there is a patch available. T

There is a (very long-standing) bug in Digital UNIX syslogd that causes
it to put log information in the wrong log file.  It happens most often
when syslog is very busy logging to disk.

I have observed this very frequently when one has an internal packet
screen machine receiving a copy of the firewall log files - it very
often breaks the information up incorrectly into different file.

I have no idea whether this bug has ever been logged, or what versions
are affected, or whether there is a patch available.

T