On Jan 11, 2008 3:45 PM, mouss <[EMAIL PROTECTED]> wrote:
>
> does your daemon run chrooted?
No.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Bart Schaefer wrote:
> On Jan 11, 2008 12:13 PM, Filipe Brandenburger <[EMAIL PROTECTED]> wrote:
>> IIRC, the datestamp is put by the process that is logging, not by syslog
>> itself. Maybe when that process started you hadn't configured the right
>> /etc/localtime and the process still thinks it's
On Jan 11, 2008 12:13 PM, Filipe Brandenburger <[EMAIL PROTECTED]> wrote:
>
> IIRC, the datestamp is put by the process that is logging, not by syslog
> itself. Maybe when that process started you hadn't configured the right
> /etc/localtime and the process still thinks it's running in UTC (process
On Jan 11, 2008 2:51 PM, Bart Schaefer <[EMAIL PROTECTED]> wrote:
> With CentOS-5.1, they're dated in UTC *most* of the time,
> but occasionally in the local timezone. This has seriously confused a
> couple of our homegrown process monitoring scripts.
IIRC, the datestamp is put by the process t
We recently upgraded (as in, backup, reinstall, selective restore) a
couple of servers from CentOS-3.9 to CentOS-5.1. This generally went
smoothly but we've encountered one confusing problem with syslog.
Under CentOS-3, syslog entries were always dated in the host local
timezone. With CentOS-5.1
5 matches
Mail list logo
