[rsbac] Upgrading from 1.2.2 to 1.2.3

[Amon Ott]

On Donnerstag, 12. August 2004 15:59, Patrique Wolfrum wrote:
> >No, not really. Do you have any log messages for me? Maybe a copy 
of 
> >the RSBAC init messages?
> >
> >It may be that there was too heavy pressure on the logging system, 
you 
> >might retry with rsbac_nosyslog kernel param. But this is only a 
> >vague guess.
> >  
> >
> The heavy pressure could be an answer to the problem. Below are the 
> error messages from one try to start the system (this is only a 
short 
> excerpt since these messages repeat themselves for several minutes 
> (resulting in a very big logfile)):
> 
> 
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> 
> Aug 11 13:51:06 pille /usr/sbin/cron[1529]: (CRON) STARTUP (fork ok)
> Aug 11 13:51:11 pille kernel: check_comp_rc: rsbac_get_attr() for 
rc_type_fd returned error!
> Aug 11 13:51:11 pille kernel: rsbac_get_super_block(): device 00:00 
not yet available, sleeping

> Aug 11 13:51:12 pille kernel: rsbac_adf_request(): request 
GET_STATUS_DATA, pid 1578, ppid 1, prog_name mingetty, uid 0, 
target_type FILE, tid Device 00:00 Inode 1059 Path socket:/[1059], 
attr none, value 0, result NOT_GRANTED (Softmode) by RC

Why does this socket fs access not work correctly, and why does it use 
dev 00:00?

Could you please mail me your .config?

Amon.
-- 
http://www.rsbac.org - GnuPG: 2048g/5DEAAA30 2002-10-22
-------------- nächster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde geschreddert...
Dateiname   : nicht verf?gbar
Dateityp    : application/pgp-signature
Dateigr??e  : 189 bytes
Beschreibung: signature
URL         : http://www.rsbac.org/pipermail/rsbac/attachments/20040813/50cb849a/attachment.bin