Hi,
NOTE: Kindly CC me when replying, I am not subscribed.
I picked up the reply from the list archive.
On Sat, 31 Oct 2009 02:15:19 +0200 Jari Fredriksson wrote:
> 30.10.2009 22:56, P K kirjoitti:
> > Hi,
> >
> > Kindly CC me when replying, I am not subscribed. Thanks. Now:
> >
> > I am using D
30.10.2009 22:56, P K kirjoitti:
> Hi,
>
> Kindly CC me when replying, I am not subscribed. Thanks. Now:
>
> I am using Debian/Sid (sidux actually) on a i686 machine. Over the
> past few months, I have seen various logs being logged to the wrong
> files, ie, they are being logged to the xyzlog.
Hi,
Kindly CC me when replying, I am not subscribed. Thanks. Now:
I am using Debian/Sid (sidux actually) on a i686 machine. Over the
past few months, I have seen various logs being logged to the wrong
files, ie, they are being logged to the xyzlog.1 file instead of the
xyzlog files. For example,
On Tue, 4 Sep 2007, Tony Heal wrote:
I have a remote server at a client site that had /etc/localtime pointing to
Eastern instead of Central. I have fixed
this. Is there a way for this to take affect without rebooting the server?
Tony Heal
After you reset your time, you will have to restart
Hi there,
On Tue, 4 Sep 2007 Tony Heal wrote:
> I have a remote server at a client site that had /etc/localtime
> pointing to Eastern instead of Central. I have fixed this. Is there
> a way for this to take affect without rebooting the server?
It has already taken effect. You don't need to rebo
BTW, this is causing all my logs to report in Eastern time
Tony Heal
_
From: Tony Heal [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 04, 2007 5:17 PM
To: debian-user@lists.debian.org
Subject: system logs and localtime
I have a remote server at a client site that had /etc
I have a remote server at a client site that had /etc/localtime pointing to
Eastern instead of Central. I have fixed
this. Is there a way for this to take affect without rebooting the server?
Tony Heal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Dec 30, 2006 at 02:39:34PM -0500, Rick Reynolds wrote:
> I've seen this happening on my etch laptop more often recently (not
> exactly sure when I first saw it, but it has probably been within the
> last 3 months). I generally keep the syste
I've seen this happening on my etch laptop more often recently (not
exactly sure when I first saw it, but it has probably been within the
last 3 months). I generally keep the system relatively up-to-date
(almost always within a couple weeks of current testing).
I typically leave my laptop on
According to various tcpd docs (manpage, READMEs) it logs information via
syslog.
However, when I do 'grep -i tcpd /var/log/*' I see nothing.
I have tcpd 7.6.dbs-8 and sysklogd 1.4.1-17 on my machine.
I have stripped my /etc/syslogd.conf down to the following single line, (and
restarted inetd)
Hi,
I have the following in /etc/syslog.conf:
auth,authpriv.* /var/log/auth.log
*.*;auth,authpriv.none /var/log/syslog
cron.* /var/log/cron.log
daemon.*/var/log/daemon.log
kern.* /var/log/kern.log
l
On Mon, Apr 08, 2002 at 08:57:44AM -0400, Rick Pasotto wrote:
> Somehow my system has the old init.d/sysklogd script and the new
> cron.daily script.
>
> I just did 'apt-get --reinstall install sysklogd' and the init.d script
> did *not* get updated. Is that behavior correct? Do I need to uninsta
Well, this is interesting.
I was just going to post about this.
I noticed that my /var/log/messages was getting longer and longer, and still had
the entries from March 17 when I did this install. I installed anacron, thinking
that not having a 24-our installation might be the problem, though it has
On Mon, Apr 08, 2002 at 02:06:29AM -0500, Mark S. Reglewski wrote:
> On Mon, Apr 08, 2002 at 01:19:52AM -0500, Mark S. Reglewski wrote:
>
> > I just flipped a potato installation to woody on Saturday, April 6.
> > My cron.daily/sysklogd script has the same line with the
> > 'reload-or-restart' arg
On Mon, Apr 08, 2002 at 01:19:52AM -0500, Mark S. Reglewski wrote:
> I just flipped a potato installation to woody on Saturday, April 6. My
> cron.daily/sysklogd script has the same line with the 'reload-or-restart'
> argument, which should be bogus according to Debian Policy, section 10.3.2,
> w
On Mon, Apr 08, 2002 at 12:04:27AM -0400, Rick Pasotto wrote:
> Thanks. With your help I have found what the problem *is*. Now I'd like
> to know *why* and *how* the problem came to be.
Don't thank me too fast. See below.
> The cron.daily/sysklogd script passes the argument 'reload-or-restart'
>
he problem doesn't still
exist.
On Sun, Apr 07, 2002 at 12:54:20PM -0500, Mark S. Reglewski wrote:
> On Sun, Apr 07, 2002 at 10:50:19AM -0400, Rick Pasotto wrote:
> > ii logrotate 3.5.9-7Log rotation utility
> >
> > For several weeks now my system logs have
On Sun, Apr 07, 2002 at 10:50:19AM -0400, Rick Pasotto wrote:
> ii logrotate 3.5.9-7Log rotation utility
>
> For several weeks now my system logs have not been getting rotated. All
> logging is going to the .0 files. syslog, daemon.log, auth.log, etc.
> remain at
ii logrotate 3.5.9-7Log rotation utility
For several weeks now my system logs have not been getting rotated. All
logging is going to the .0 files. syslog, daemon.log, auth.log, etc.
remain at zero length and syslog.0, daemon.log.0, auth.log.0, etc keep
growing. If I reboot logging
On Fri, 20 Jul 2001, john gennard wrote:
> I've decided to have a look at /var/log which over the months
> has become quite large. The man page for syslog.conf and
> /etc/syslog.conf I basically understand, but I can't find any
> config file which relates to the savelog program, yet files.0
> and
On Fri, 20 Jul 2001, john gennard <[EMAIL PROTECTED]> wrote:
>I've decided to have a look at /var/log which over the months
>has become quite large. The man page for syslog.conf and
>/etc/syslog.conf I basically understand, but I can't find any
>config file which relates to the savelog program, y
On Fri, Jul 20, 2001 at 06:09:32PM +0100, john gennard wrote:
> Can someone please explain how/where savelog operates from?
grep -r savelog /etc/cron*
Cheers,
Joost
I've decided to have a look at /var/log which over the months
has become quite large. The man page for syslog.conf and
/etc/syslog.conf I basically understand, but I can't find any
config file which relates to the savelog program, yet files.0
and .x.gz have been created in /var/log.
I have little
On Sun, 5 Dec 99 20:33:06 GMT
John <[EMAIL PROTECTED]> wrote:
> What steps do users take to keep logs down to reasonable sizes? I
> have seen nothing on this aspect of management and so have been
> using 'rm' and then creating a new file.
Look into the logrotate package.
> If it is possible,
What steps do users take to keep logs down to
reasonable sizes? I have seen nothing on this aspect
of management and so have been using 'rm' and then
creating a new file.
If it is possible, I would like to remove everything
older than say seven days on a twice monthly basis
after checking there
On Sun, Jun 27, 1999 at 07:49:25PM -, Pollywog wrote:
> A few minutes ago, I started getting this about every five minutes. My
> /etc/crontab has not been changed, so I am stumped
>
> > Unusual System Events
> > =-=-=-=-=-=-=-=-=-=-=
> > Jun 27 19:40:32 lilypad /usr/bin/crontab[7692]: (root)
A few minutes ago, I started getting this about every five minutes. My
/etc/crontab has not been changed, so I am stumped
> Unusual System Events
> =-=-=-=-=-=-=-=-=-=-=
> Jun 27 19:40:32 lilypad /usr/bin/crontab[7692]: (root) LIST (root)
> Jun 27 19:40:32 lilypad crontab[7695]: (root) REPLACE (
27 matches
Mail list logo
