Conference turris::digital_unix

9481.0. "Problem :syslog forward" by TJOV01::YAMAZAKI () Sun Apr 13 1997 19:25

I am SE(GOV) of DEC Japan. 

There is the case that can't forward syslog with Digital UNIX v4.0a. 
I gathered up question matter to the following. 


1. Movement defectiveness about forward of syslog.conf 

Forward point doesn't recognize "facility" and "priority" to establish 
setting of "syslog.conf" in forward (@ host name) in normality. 
As a command is less than it. 

	/usr/bin/logger -f (Message file ) -p local0.crit

Priority should be "202", but originally becomes "0" in case of abnormality. 
As a result forward point handles facility as kern and handles priority as 
emerg. 

     Note) priority is a value of "pri =" when syslogd starts with "-d" 
	   option. 

And an origin of forward becomes abnormal by all means after having 
transmitted HUP signal to "syslogd". 

This phenomenon occurs, when a character number of message becomes 114 
characters or more��
If it is 113 characters or less, there is not a problem.
 (I lose message file with one line )

If I turn message file into two lines and will turn the first line into 113 
characters or less, Syslog act without a problem even if the second line is
 114 characters or more. 


2.Supplement information 

A phenomenon mentioned above is confirmed by the following patterns. 
	���ݡ�from DEC��to��DEC
	���ݡ�from SUN��to��DEC


Or greater

/Yuusuke��Yamazaki

Hi

 I suggest you file a QAR, or if you need a patch, file a
CLD.  This notes file is not a problem reporting mechanism.