Deutsch   English   Français   Italiano  
<87ed3pkxru.fsf@jemoni.to>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Wolfgang Agnes <wagnes@jemoni.to>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: syslogd and sendmail question: I removed maillog
Date: Tue, 05 Nov 2024 21:32:05 -0300
Organization: A noiseless patient Spider
Lines: 23
Message-ID: <87ed3pkxru.fsf@jemoni.to>
References: <87fro5nwy5.fsf@jemoni.to> <lovl8gFh8vdU2@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Wed, 06 Nov 2024 01:32:07 +0100 (CET)
Injection-Info: dont-email.me; posting-host="3a024203ed4b4dc2f11f6dc7682e8355";
	logging-data="1875058"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+TbTFlcL9XXMZPj/Vk08R40D5biWel0XQ="
Cancel-Lock: sha1:942IV0DpUKKtTSVTxztsd5ky/9Q=
	sha1:eU+IPHhta4NNOxxVG2+XXAIbey0=
Bytes: 1994

Bob Eager <news0009@eager.cx> writes:

> On Tue, 05 Nov 2024 19:21:38 -0300, Wolfgang Agnes wrote:
>
>> I changed the timezone in my system and decided to start over with the
>> mail log.  Without stopping sendmail, I removed /var/log/maillog.  Then
>> I stopped it and started it.  I did not see a new maillog being created.
>> I then restarted syslogd.  And also restarted sendmail.  Still no
>> maillog.  I tried touching maillog and set the same permissions as the
>> old file, which I renamed.  No messages written to maillog this way.  I
>> looked at /var/log/messages to see if maybe mail messages were being
>> logged there---I saw some, but they were still in the previous timezone,
>> so they were not new.  I'm puzzled.  How wrong was what I did?
>
> Best way to recreate any longfile is illustrated by this example for 
> maillog:
>
>   rm -f /var/log/maillog
>   newsyslog -C /var/log/maillog

Thanks!  That did it.  I had to issue the newsyslog command and then
restart syslogd.  (As soon as I'm done with Sendmail, I'll read a book
on syslogd.)