Date: Thu, 17 Aug 2000 18:03:41 +0100 From: Brian Somers <brian@Awfulhak.org> To: David Wolfskill <dhw@whistle.com> Cc: freebsd-stable@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: Observation re: /etc/security (1.36.2.5 2000/08/08 18:05:26) Message-ID: <200008171703.e7HH3gq06756@hak.lan.Awfulhak.org> In-Reply-To: Message from David Wolfskill <dhw@whistle.com> of "Thu, 17 Aug 2000 08:51:24 PDT." <200008171551.IAA03253@pau-amma.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Have a look at periodic.conf(5), specifically:
daily_status_security_noamd
(bool) Set to ``YES'' if you want to ignore amd(8) mounts when
comparing against yesterdays filesystem mounts.
If you think it would be useful to have a
daily_status_security_noamdpid variable that uses a new -A switch to
/etc/security, I'd appreciate the patch :-)
> Please note that this is an observation -- not a complaint, whine, or even
> a suggestion for change: merely something I noticed that makes sense
> after I think about it, but caught me a little off-guard, so I thought it
> might be worth mentioning so others will have a chance to think about it
> before they see it. OK?
>
> I upgraded a couple of laptops & my desktop from earlier 4.1-STABLEs to
> the "snapshot" captured as of our local CVS server's CVSup yesterday
> morning. Things seem to be going well, as many of us have come to expect
> -- I'll take this opportunity to express my appreciation for both the
> technical work and the coordination of same that goes into the project.
> (Yes, I realize that things aren't always smooth. This is, after all, a
> human endeavor....)
>
> What I noticed was that in the list of "changes in mounted filesystems",
> changes in the amd PID count as reported changes.
>
> Of course, this doesn't affect folks who don't use an automounter; we do.
>
> And given that this is goming from /etc/security, it's arguably the
> Right Thing To Do, as well. But it might also be considered mere noise
> -- depending on one's perspective.
>
> In this case, the PID change was an artifact of the re-boot to implement
> the newer 4.1-S on my desktop; there were quite a few other messages
> (differences in binaries; dmesg chatter, ...).
>
> As above, I was merely a little surprised at this; no harm done....
>
> Cheers,
> david
> --
> David Wolfskill dhw@whistle.com UNIX System Administrator
> Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823
--
Brian <brian@Awfulhak.org> <brian@[uk.]FreeBSD.org>
<http://www.Awfulhak.org>; <brian@[uk.]OpenBSD.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008171703.e7HH3gq06756>