From: Amon Ott <ao@rsbac.org>
Subject: Re: success
Date: Wed, 28 Mar 2001 09:18:46 +0200
Next Article (by Date): Re: RSBAC v1.1.1 problem Amon Ott
Previous Article (by Date): syslog-ng Bencsath Boldizsar
Top of Thread: success Bencsath Boldizsar
Articles sorted by: [Date]
[Author]
[Subject]
On Sam, 24 Mär 2001 Bencsath Boldizsar wrote: > After yesterdays investigations I simly copied my fd_aci (29)=/rsbac to > fd_aci (18). With the change from kmalloc to vmalloc rsbac has been > started well. > Now it is fully working on that (complicated) computer. > /dev/md0 on / type ext2 (rw,errors=remount-ro,errors=remount-ro) > proc on /proc type proc (rw) > devpts on /dev/pts type devpts (rw,gid=5,mode=620) > /dev/sda1 on /boot2 type ext2 (rw) > /dev/sdb1 on /boot type ext2 (rw) > /dev/md2 on /tmp type ext2 (rw,nosuid,nodev,errors=remount-ro) > /dev/md1 on /var type ext2 (rw,nosuid,nodev,errors=remount-ro) > /dev/sdc1 on /data type ext2 (rw,nosuid,nodev,errors=remount-ro) > /dev/hda1 on /data2 type reiserfs (rw,nosuid,nodev) > > You can see, reiserfs, raid, smp kernel: Linux db 2.4.2-rsbac #6 SMP, > I hope Amon will find the true reasons next week. The final release includes a bugfix against pre8. The FD entry for /rsbac dir was put to the wrong list - the last one read. This is the reason for the entry at the wrong place. I will see, why moving an item makes the system hang. Sure a locking problem. Memory allocation is going to be moved to our own slab cache, but this will have to be investigated first. Amon. - To unsubscribe from the rsbac list, send a mail to majordomo@rsbac.org with unsubscribe rsbac as single line in the body.
Next Article (by Date): Re: RSBAC v1.1.1 problem Amon Ott
Previous Article (by Date): syslog-ng Bencsath Boldizsar
Top of Thread: success Bencsath Boldizsar
Articles sorted by: [Date]
[Author]
[Subject]