Kernel-2.2.20-3 i oidentd

[Jarosław Kamper]

On Thu, Jan 03, 2002 at 04:14:37PM +0100, Stacho Pal wrote:
> Witam!
> Po wymianie kernela na 2.2.20-3 w logach pokazuje się coś
> takiegon jak poniżej i za maskarady nie można się połączyć. 
> Oidentd stary 1.7.1-5 Jest na to jakaś rada???
> =============================
> Jan  3 15:31:27 orion oidentd[1191]: Connection from poznan.irc.pl 
> (150.254.64.64):3286
> Jan  3 15:31:27 orion oidentd[1191]: [192.168.1.59] Successful lookup (by 
> forward): 63303 , 6665 : USERID : UNIX : bourne
> Jan  3 15:31:27 orion kernel: Security: signal 11 (read or execute addr 
> 0xbff00000) sent to oidentd[1191], UID 99, EUID 99, parent rlinetd[8959], UID 
> 0, EUID 0, by oidentd[1191], UID 99, EUID 99, parent rlinetd[8959], UID 0, EUID 
> 0

To normlalne, gdy:
Security options  ---> [*] Extra logging of unusual events

CONFIG_SECURE_LOGGING:
? This turns on some extra kernel logging.  Right now this includes:
?
? * some extra verbosity in the network layer (reporting about arp cache                  ?
?   changes, and complaining if someone tries to route throughius and                     ?
?   we're not a router)	  								  ?
? * also causes some packets that used to be dropped silently to get                      ?
?   whined about       									  ?
? * logs of who/what/when the system time changes					  ?
? * logs when/why forks fail								  ?
? * logs certain "lethal" signals: SIGSEGV, SIGBUS, SIGABRT, SIGILL                       ?
? This is of limited use, and has some extra overhead, but isn't likely                   ?
? to cause any problems.								  ?

;)

-- 
Jarosław Kamper	  	         jack w jack.eu.org	           UIN: 35713516
http://jack.eu.org		                  Registered Linux User # 165846
Jeżeli chcesz pomóc to rób tylko tyle ile możesz. Robienie cudów pozostaw innym 
                 kloczek at pld-devel-pl w pld.org.pl