cvs commit: src/etc/rc.d Makefile auditd

Doug Barton dougb at
Fri Feb 3 11:44:26 PST 2006

Robert Watson wrote:
> On Thu, 2 Feb 2006, Doug Barton wrote:
>> I have a couple concerns about this. First the more general, I'm not
>> sure that /etc/security is a reasonable place for your config files.
>> That's a very general name, and the audit stuff is a very specific
>> project. That said, I'm not sure that we need yet another directory
>> under /etc, but I'm curious about what others think about this issue.
> If I were picking a new directory name, it would be /etc/audit. 
> However, the name we picked was for compatibility with Solaris and Mac
> OS X, both of which store audit configuration files of the same names in
> the /etc/security directory.  

Ok, that's good enough for me. Sorry if I missed this detail in a previous

> Tom wrote these bits of the rc.d script, so I can't speak to the
> details.

Tom was kind enough to reply already to say that he'll test some of my

> However, I do know that auditd needs to be run strictly before
> any daemon that allows user login or authentication, such as inetd,
> sshd, etc.  Ideally it should run after syslog, though, since auditd
> errors are reported via syslogd.

Ok, this and Brooks comment make things more clear. I don't see anything
that runs prior to DAEMON that fits the criteria you state here, so for now
you should be ok. Going forward, if there is anything which runs before
DAEMON which needs auditd support, it would (IMO) be better for that service
to REQUIRE: auditd. Making the ordering specific becomes increasingly
important as we add local/ports scripts to the base rcorder, and REQUIRE
generally works "better" than BEFORE. It's also a lot easier to debug.

Thanks for your (and Tom's) response. I'm relieved to hear that these issues
have already been well thought out, and I hope that this additional
information is useful.



    This .signature sanitized for your protection

More information about the cvs-src mailing list