Re: HEADS UP: periodic(8)-ifying daily security checks

2001-12-07 Thread Crist J . Clark

On Fri, Dec 07, 2001 at 03:58:05PM -0800, Crist J . Clark wrote:
[snip]

> For those who do not have the time to do this the really quick work
> around is,

Oops, in my haste I forgot to put the very easiest workaround, don't
update /etc/periodic/daily/450.status-security.
-- 
"It's always funny until someone gets hurt. Then it's hilarious."

Crist J. Clark | [EMAIL PROTECTED]
   | [EMAIL PROTECTED]
http://people.freebsd.org/~cjc/| [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



HEADS UP: periodic(8)-ifying daily security checks

2001-12-07 Thread Crist J . Clark

I have just committed changes to how the daily security checks are
done in -CURRENT. Long ago, there was just /etc/daily. Then
/etc/security was split out of /etc/daily. Some time later, /etc/daily
became a set of periodic(8) scripts. Now, this evolution continues,
and /etc/security has been broken into periodic(8) scripts to make
local customization easier and more maintainable.

However, like any change, there may be some problems making the
transition to the new system. If you are using the default
/etc/security, the change will be transparent. Next time you update,
mergemaster(8) will take care of everything for you. Note that
/etc/security will no longer be used in any way, it can safely be
removed.

If you have local customizations to /etc/security, the best thing to
do and the ultimate way to fix things "properly" is to break out the
customizations into small scripts and drop the scripts into
/usr/local/etc/periodic/security. Make sure the scripts are set
executable and ls(1) in the order you wish them to execute. If your
customizations are separate from the actions in the default
/etc/security, this is all you need to do. If you have made
customizations to actions in /etc/security, drop your customized
script into /usr/local/etc/periodic/security, and then deactivate the
default script with the same action by placing the appropriate,

  daily_status_security_