Re: PACKAGESITE spam

On 12/22/2013 6:00 AM, Frank Seltzer wrote:
> Adrian Chadd said:
>
> The point is that some people like an audit trail. The audit trail for
> some people involves remote logging of syslog messages to a log host.
> This would include when packages are installed.

There are two more:

1. When a port was deinstalled
2. History of a port (previous installs/deinstalls)

For example, my logs have:

Sep  9 16:05:28 chombo pkg-static: postfix-2.10.0,1 deinstalled
Sep  9 16:05:36 chombo pkg-static: postfix-2.10.0,1 installed
Nov 30 00:25:02 chombo pkg: postfix-2.10.0,1 deinstalled
Nov 30 00:25:09 chombo pkg-static: postfix-2.10.2,1 installed

Which tells me I recompiled postfix on Sept 9 (this would have been when 
I changed it over to openssl from ports) and updated it to 2.10.2 on Nov 
30 using portmaster.

How do I know that?

Because of that deinstall log.  When you use `pkg install` to upgrade a 
port, you get something like this:

Jul 10 23:06:40 chombo pkg-static: ca_root_nss-3.15.1 installed
Nov 29 15:04:52 chombo pkg: ca_root_nss reinstalled: 3.15.2_1

That information does not exist in the pkg database.

> My thought:
>
> Then why can't the messages about installed ports have it's own log file
> rather than /var/log/messages?

I have never understood why anyone would enable the use of syslog 
without also providing a way of specifying the facility and level.  I'd 
much rather do stuff like this:

local0.*	/var/log/dovecot.log
local1.*	/var/log/postgres.log
local2.*	/var/log/php-fpm.log

_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"