more so (for the base system I just install them always, as it doesn't pay off
in the long run to skip them). Portaudit for a (web)server has a lot of
notifications that are not critical, like several issues over the last year
with php's safe mode that any sane webserver admin doesn't use.
i
Hi
I'm looking for a generel guide / howto for maintaining a FreeBSD
system - not all the ports, just the base system. One that describe
how often you should update your port-tree, which basic ports like
audit you should have. Its a server I have that runs different
services, so I'm also looking
Freebsd.org - docs; several docs there
- Original Message -
From: owner-freebsd-questi...@freebsd.org owner-freebsd-questi...@freebsd.org
To: freebsd-questions@freebsd.org freebsd-questions@freebsd.org
Sent: Wed May 06 19:43:07 2009
Subject: Maintaining a FreeBSD system - Workcycle
Hi
On Wed, May 6, 2009 at 6:43 PM, Kalle Møller kalle.mol...@gmail.com wrote:
Hi
I'm looking for a generel guide / howto for maintaining a FreeBSD
system - not all the ports, just the base system. One that describe
how often you should update your port-tree, which basic ports like
audit you
On Thursday 07 May 2009 05:48:10 Tim Judd wrote:
2) Install portaudit and watch the periodic mailings that are sent to you.
They list vulnerabilities in ports that really should be addressed.
Not really. You can use the same common sense as with the base system and even
more so (for the base
