log pid in our log, RT#80211

diff --git a/FS/FS/Schema.pm b/FS/FS/Schema.pm
index 431f125..1ee7093 100644 (file)
--- a/FS/FS/Schema.pm
+++ b/FS/FS/Schema.pm
@@ -5909,6 +5909,7 @@ sub tables_hashref {
         'path',           'varchar',     '', 2*$char_d, '', '',
         '_date',                   @date_type,          '', '',
         'render_seconds',     'int', 'NULL',        '', '', '',
+        'pid',                'int', 'NULL',        '', '', '',
       ],
       'primary_key'  => 'lognum',
       'unique'       => [],

diff --git a/FS/FS/access_user_log.pm b/FS/FS/access_user_log.pm
index 026670c..552dd2a 100644 (file)
--- a/FS/FS/access_user_log.pm
+++ b/FS/FS/access_user_log.pm
@@ -53,6 +53,10 @@ _date
 
 =back
 
+=item pid
+
+=back
+
 =head1 METHODS
 
 =over 4
@@ -84,6 +88,7 @@ sub insert_new_path {
     'path'           => $path,
     '_date'          => time,
     'render_seconds' => $render_seconds,
+    'pid'            => $$,
   } );
 
   #so we can still log pages after a transaction-aborting SQL error (and then
@@ -127,6 +132,7 @@ sub check {
     || $self->ut_text('path')
     || $self->ut_number('_date')
     || $self->ut_numbern('render_seconds')
+    || $self->ut_numbern('pid')
   ;
   return $error if $error;