clone 546250 -1
retitle -1 readahead-fedora: init script fails to profile without existing 
files lists
severity -1 grave
severity 546250 normal
retitle 546250 readahead-fedora: CONFIG_AUDITSYSCALL is also needed
thanks

On Friday 11 September 2009 17:05:39 Nelson A. de Oliveira wrote:
[...]
>
> Hi Raphael!
>
> > On Friday 11 September 2009 11:20:51 Nelson A. de Oliveira wrote:
> >> After installing readahead-fedora (1.5.0-4) and doing a
> >> "touch /.readahead_collect" I see both early-readahead and
> >> later-readahead failing at boot time. Nothing is created in
> >> /var/lib/readahead/ nor /sbin/readahead is started.
> >>
[...]
> >
> > Actually, the non-backgrounded readahead is intended to be done even when
> > profiling (so that the boot is not slowed down very much). I'll
> > workaround the bug directly in get_lists()
>
> Good.
>

Each issue is a different bug, so cloning it.

> >> But again, nothing appears inside /var/lib/readahead
> >> What could be wrong, please?
> >
> > Are you using a stock Debian kernel? insserv? dash? does any error
> > message show up?
>
> It's my own kernel, 2.6.31. From what I saw, it needs CONFIG_AUDIT and
> I have it:
>
> $ grep CONFIG_AUDIT .config
> # CONFIG_AUDIT_ARCH is not set
> CONFIG_AUDIT=y
> # CONFIG_AUDITSYSCALL is not set
> CONFIG_AUDIT_GENERIC=y
>
> Maybe CONFIG_AUDITSYSCALL is also needed?
>

Er, yes, seems logic. The syscalls are the ones being traced to determine
the accessed files, and that's exactly what CONFIG_AUDITSYSCALL permits.

> Booting it with RAC_DEBUG="on" in /etc/readahead.conf I have:
>
> $ cat /dev/.readahead-rac.debug
> ***DEBUG:
>
> HAVE SIGNAL 15
>
> ***DEBUG: deleting audit rule
> readahead-collector: ERROR: deleting rule (Invalid argument)
> ***DEBUG: starting reordering data
> ***DEBUG: done: success
>

I would have expected audit_rule_syscallbyname_data to actually fail if
CONFIG_AUDITSYSCALL is not enabled, which would have made it write
a good error message.

>
> What else can I use to debug this, please?

Could you please try with a kernerl with CONFIG_AUDITSYSCALL enabled? I'm
almost sure that's why it is failing.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to