Re: pkg_add/pkg_delete: include PID in syslog messages

2012-05-28 Thread Lawrence Teo
On Mon, Mar 19, 2012 at 12:50:12PM +0100, Marc Espie wrote: On Wed, Mar 07, 2012 at 12:31:48AM -0500, Lawrence Teo wrote: This simple diff makes pkg_add and pkg_delete include their PID when logging to syslog. This is useful when trying to determine whether several packages were added (or

Re: pkg_add/pkg_delete: include PID in syslog messages

2012-05-28 Thread Stuart Henderson
On 2012/05/28 10:53, Lawrence Teo wrote: On Mon, Mar 19, 2012 at 12:50:12PM +0100, Marc Espie wrote: The more I think about it, the more I fail to see the value. Consider that any pkg_add/pkg_delete that actually changes installed packages *will* lock the database anyways, so by nature, all

Re: pkg_add/pkg_delete: include PID in syslog messages

2012-05-28 Thread Marc Espie
On Mon, May 28, 2012 at 10:53:15AM -0400, Lawrence Teo wrote: My goal is to help the bleary-eyed sysadmin figure out what in the world s/he did after working on a project all night long. :) I think the PIDs would help them answer questions like, Why did I install $PACKAGE again? (where

Re: pkg_add/pkg_delete: include PID in syslog messages

2012-03-19 Thread Marc Espie
On Wed, Mar 07, 2012 at 12:31:48AM -0500, Lawrence Teo wrote: This simple diff makes pkg_add and pkg_delete include their PID when logging to syslog. This is useful when trying to determine whether several packages were added (or removed) by the same pkg_add (or pkg_delete) process. Here is

pkg_add/pkg_delete: include PID in syslog messages

2012-03-06 Thread Lawrence Teo
This simple diff makes pkg_add and pkg_delete include their PID when logging to syslog. This is useful when trying to determine whether several packages were added (or removed) by the same pkg_add (or pkg_delete) process. Here is some sample output: Mar 3 22:15:17 obsd-amd64 pkg_add[3530]: