Hi all,
Debian 10.13
Is it normal for logrotate service to go from "inactive (dead)" to
"failed (Result: exit-code)" state every time logrotate.timer
(active-waiting) kicks in?
E.g. "sudo systemctl restart logrotate" brings back "inactive (dead)"
t;> > has long since forced most of us that want that log, into moving
> >> > it to /home/username/log and reprogramming logrotate to maintain
> >> > it there years ago.
> >>
> >> So why should user be able to write in /var/log? It is the systems
>
t;> > has long since forced most of us that want that log, into moving
> >> > it to /home/username/log and reprogramming logrotate to maintain
> >> > it there years ago.
> >>
> >> So why should user be able to write in /var/log? It is the systems
>
tchmail, procmail, spamassassin, clamav and its ilk, running as
>> > the user can access /var/log to keep its logs. Debian's legendary
>> > paranoia about who can write a log in /var/log has long since forced
>> > most of us that want that log, into moving it to /
On Tuesday 13 August 2019 13:06:23 Dan Purgert wrote:
> Gene Heskett wrote:
> > On Tuesday 13 August 2019 05:41:52 Dan Purgert wrote:
> >> Gene Heskett wrote:
> >> > On Tuesday 13 August 2019 02:24:34 deloptes wrote:
> >> > [...]
> >> >
> >> >> I am not aware of any program I've been using
> >> >>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Gene Heskett wrote:
> On Tuesday 13 August 2019 05:41:52 Dan Purgert wrote:
>
>> Gene Heskett wrote:
>> > On Tuesday 13 August 2019 02:24:34 deloptes wrote:
>> > [...]
>> >
>> >> I am not aware of any program I've been using
>> >> for the past 15y th
with their own directories in /var/log (or well, at least by default)?
>
No, while they may be callable by anyone, they all become the user
calling them.
> >> [...]
> >> Logrotate also does not need to be modified - only for your custom
> >> stuff, so it is expect
On Tue, Aug 13, 2019 at 09:30:34AM +1200, Philip wrote:
> I just updated from Debian 8 to 9 and I'm getting the following error. I'm
> guessing it's something to do with permissions?
>
> Something to do with the create 640 root adm?
>
> /etc/cron.daily/logrota
:
> While we're talking about logrotate, I'd like to ask if anyone else has
> seen (and solved) the problem I had with logrotate.
>
> There were times in the past when I wanted to do things like keep a log (or
> a backup of one or more files) something like this: 7 daily lo
etchmail, procmail, clamav or spamd running as me, can
> keep their logs in /var/log, the permissions just aren't there after a
> reboot.
Aren't all four of those system services; with their own system users,
with their own directories in /var/log (or well, at least by default)?
&
nning as
> > the user can access /var/log to keep its logs. Debian's legendary
> > paranoia about who can write a log in /var/log has long since forced
> > most of us that want that log, into moving it to /home/username/log
> > and reprogramming logrotate to maintain it
n, clamav and its ilk, running as
> > the user can access /var/log to keep its logs. Debian's legendary
> > paranoia about who can write a log in /var/log has long since forced
> > most of us that want that log, into moving it to /home/username/log
> > and repr
's legendary paranoia about who
> can write a log in /var/log has long since forced most of us that want
> that log, into moving it to /home/username/log and reprogramming
> logrotate to maintain it there years ago.
So why should user be able to write in /var/log? It is the systems log
dir
eep its logs. Debian's legendary paranoia about who
> can write a log in /var/log has long since forced most of us that want
> that log, into moving it to /home/username/log and reprogramming
> logrotate to maintain it there years ago.
Nuthin' wrong with that. An individual user
On 2019-08-13 00:38 -0400, Gene Heskett wrote:
[rant skipped]
> So just where in tunket _are_ we supposed to be able to keep our logs
> then? A place that Just Works would sure be appreciated.
Putting them under /home is fine, see this comment in
/lib/systemd/system/logrotate.service:
,
| #
o do with the create 640 root adm?
>>
>> /etc/cron.daily/logrotate:
>> error: unable to open /home/philip/logs/access.log.1 for compression
>> error: unable to open /home/philip/logs/error.log.1 for compression
>> run-parts: /etc/cron.daily/logrotate exited with r
mething to do with the create 640 root adm?
> >
> > /etc/cron.daily/logrotate:
> > error: unable to open /home/philip/logs/access.log.1 for compression
> > error: unable to open /home/philip/logs/error.log.1 for compression
> > run-parts: /etc/cron.daily/logrotate exited wi
phi...@treads.nz [2019-08-13T09:30:34+12] wrote:
> I just updated from Debian 8 to 9 and I'm getting the following error.
> I'm guessing it's something to do with permissions?
>
> Something to do with the create 640 root adm?
>
> /etc/cron.daily/logrotate:
>
Afternoon,
I just updated from Debian 8 to 9 and I'm getting the following error.
I'm guessing it's something to do with permissions?
Something to do with the create 640 root adm?
/etc/cron.daily/logrotate:
error: unable to open /home/philip/logs/access.log.1 for compressio
ePaths.
>
> Thank you.
>
> Regards,
> Tan Shao Yi
>
> On 21/7/19, 5:55 PM, "Sven Joachim" wrote:
>
> On 2019-07-21 02:42 +, Tan Shao Yi wrote:
> > I upgraded to Debian 10 recently and it looks like logrotate is
> > not working on files
wrote:
On 2019-07-21 02:42 +, Tan Shao Yi wrote:
> I upgraded to Debian 10 recently and it looks like logrotate is not
> working on files outside the /var directory:
This is correct.
> For example,
>
> Jul 21 00:00:01 server-name logr
Sven Joachim, on 2019-07-21:
> On 2019-07-21 02:42 +, Tan Shao Yi wrote:
> > May I know if something has changed recently to cause this?
>
> It is the ProtectSystem=full directive in logrotate.service which causes
> /usr to be mounted read-only for logrotate. See the SANDB
On 2019-07-21 02:42 +, Tan Shao Yi wrote:
> I upgraded to Debian 10 recently and it looks like logrotate is not
> working on files outside the /var directory:
This is correct.
> For example,
>
> Jul 21 00:00:01 server-name logrotate[8874]: error: error renaming
> /usr
Good day Tan Shao Yi,
Tan Shao Yi, on 2019-07-21:
> For example,
>
> Jul 21 00:00:01 server-name logrotate[8874]: error: error renaming
> /usr/local/apache/logs/https-error_log.12.gz to
> /usr/local/apache/logs/https-error_log.13.gz: Read-only file system
Here I would have sugg
Hi,
I upgraded to Debian 10 recently and it looks like logrotate is not working on
files outside the /var directory:
For example,
Jul 21 00:00:01 server-name logrotate[8874]: error: error renaming
/usr/local/apache/logs/https-error_log.12.gz to
/usr/local/apache/logs/https-error_log.13.gz
On mardi 24 avril 2018 18:40:55 CEST John Cunningham wrote:
> I cheated and added logrotate to root's crontab as an ugly hack to get them
> rotating. What is the *right* way to get it going again?
I just noticed a similar problem on my system. I've installed systemd-cron and
p
On Sun, May 6, 2018 at 5:10 AM Jonathan de Boyne Pollard <
j.deboynepollard-newsgro...@ntlworld.com> wrote:
>
> So bear in mind that your learned ideas about what runs what are no
> longer true.
>
>
If I still did sigfiles, this would now be in mine. Thank you very much for
your helpful reply.
--
--
Boyan Penkov
www.boyanpenkov.com
> On May 6, 2018, at 05:10, Jonathan de Boyne Pollard
> wrote:
>
> John Cunningham:
>
>> I hate to wade into the pool of systemd hate, but is this systemd's fault? I
>> noticed anacron doesn't exist on this system. Is it supposed to anymore? Or
>> is that
John Cunningham:
I hate to wade into the pool of systemd hate, but is this systemd's
fault? I noticed anacron doesn't exist on this system. Is it supposed
to anymore? Or is that one of the things that have been deprecated? If
so, how are the /etc/cron.daily jobs getting run these days?
You'l
Really late response here, but thanks — some reading of /etc/anacrontab and
run-parts does make clear that edits of the crontab will then be run by anacron
Thanks kindly!
--
Boyan Penkov
www.boyanpenkov.com
> On Apr 24, 2018, at 14:27, Brad Rogers wrote:
>
> On Tue, 24 Apr 2018 14:09:06 -0400
On Tue, 24 Apr 2018 14:09:06 -0400
Boyan Penkov wrote:
Hello Boyan,
>that this is the case, and automatically read the crontab, then write
>an intelligent anacrontab with sane defaults?
From the anacron page on packages.debian.org;
This package is pre-configured to execute the daily jobs of th
In this vein, is there a way to intelligently indicate to the system
that this is the case, and automatically read the crontab, then write an
intelligent anacrontab with sane defaults?
Cheers!
On 04/24/2018 02:04 PM, Sven Joachim wrote:
If your system is not running 24/7, then anacron is very
On 2018-04-24 16:40 +, John Cunningham wrote:
> I just noticed that logrotate hasn't been running since October 2016 on one
> of my Jessie boxes. Manually running logrotate works without issue. This
> is approximately the time I upgraded it from Wheezy. I hate to wade into
Howdy,
I just noticed that logrotate hasn't been running since October 2016 on one
of my Jessie boxes. Manually running logrotate works without issue. This
is approximately the time I upgraded it from Wheezy. I hate to wade into
the pool of systemd hate, but is this systemd's fault?
kjo...@poczta.onet.pl (Kamil Jońca) writes:
> Andy Smith writes:
>
>> Hi Kamil,
>>
>> On Sat, Feb 04, 2017 at 10:11:00AM +0100, Kamil Jońca wrote:
>>> I have logrotate with config (excerpt)
>>> --8<---cut here---start---
On Sat, 04 Feb 2017 18:04:12 +0100
kjo...@poczta.onet.pl (Kamil Jońca) wrote:
> Andy Smith writes:
>
> > Hi Kamil,
> >
> > On Sat, Feb 04, 2017 at 10:11:00AM +0100, Kamil Jońca wrote:
> >> I have logrotate with config (excerpt)
> >> --8&l
On Sat, 4 Feb 2017 16:12:50 +
Andy Smith wrote:
> Hi Kamil,
>
> On Sat, Feb 04, 2017 at 10:11:00AM +0100, Kamil Jońca wrote:
> > I have logrotate with config (excerpt)
> > --8<---cut here---start->8---
> > compress
>
Andy Smith writes:
> Hi Kamil,
>
> On Sat, Feb 04, 2017 at 10:11:00AM +0100, Kamil Jońca wrote:
>> I have logrotate with config (excerpt)
>> --8<---cut here---start->8---
>> compress
>
> […]
>
>> And since some d
Hi Kamil,
On Sat, Feb 04, 2017 at 10:11:00AM +0100, Kamil Jońca wrote:
> I have logrotate with config (excerpt)
> --8<---cut here---start->8---
> compress
[…]
> And since some days I started to receive *compressed* old syslog files
> :(
I have logrotate with config (excerpt)
--8<---cut here---start->8---
compress
delaycompress
dateext
mail root
compresscmd /usr/bin/xz
uncompresscmd /usr/bin/unxz
compressext .xz
compressoptions -9
tabooext +.dpkg-bak
minsize 1M
[...]
--8<--
> [rsyslog maintainer speaking here]
>
>> One of the culprits in my full /var partition was a 3 gig syslog file
>> which has only been getting bigger since January despite running
>> logrotate -f. I try to run it this time but I'm told that it can't
>
Ok, thank you, it works.
1) /etc/logrotate.d/my_app should be 644 mode and owner must be root
2) I added 'su ' on the top of the
body of the logrotate file
3) /usr/sbin/logrotate -d /etc/logrotate.d/my_app and /usr/sbin/logrotate
-f /etc/logrotate.d/my_app help to debug
2016-01-27 22
On 27/01/16 21:37, Gene Heskett wrote:
What ails the udev maintainer(s) that seem to think the owner and only
human user of this machine is to be denied access to its facilities?
The udev maintainers have no idea how many users your system is going to
have, and udev itself is not sentient.
On Wed, 27 Jan 2016 16:37:20 -0500
Gene Heskett wrote:
>
> What ails the udev maintainer(s) that seem to think the owner and
> only human user of this machine is to be denied access to its
> facilities?
>
> It is MY machine, and I built it for ME to use. And if someone in the
> udev camp gets
On Wednesday 27 January 2016 16:00:59 Glyn Astill wrote:
> > From: ikuzar RABE
> >To: Glyn Astill
> >Cc: "debian-user@lists.debian.org"
> >Sent: Wednesday, 27 January 2016, 16:56
> >Subject: Re: logrotate does not work on my log (Debian Jessie)
> >
> From: ikuzar RABE
>To: Glyn Astill
>Cc: "debian-user@lists.debian.org"
>Sent: Wednesday, 27 January 2016, 16:56
>Subject: Re: logrotate does not work on my log (Debian Jessie)
>
>
>
>the ownership of my_app.log.gz is not root (just a simple user, and a
the ownership of my_app.log.gz is not root (just a simple user, and a
simple group)
2016-01-27 17:43 GMT+01:00 Glyn Astill :
>
> > From: ikuzar RABE
> >To: debian-user@lists.debian.org
> >Sent: Wednesday, 27 January 2016, 16:32
> >Subject: logrotate does not wo
> From: ikuzar RABE
>To: debian-user@lists.debian.org
>Sent: Wednesday, 27 January 2016, 16:32
>Subject: logrotate does not work on my log (Debian Jessie)
>
>
>
>Hi all,
>
>I upgraded my system from Debian 6 to Debian 8 Jessie. logrotate worked on my
>log
Hi all,
I upgraded my system from Debian 6 to Debian 8 Jessie. logrotate worked on
my log on Debian 6 (I got my_app.log.gz when I put
/etc/logrotate.d/my_app). But it no longer works on Debian 8. However, I
see /var/log/syslog.2.gz syslog.3.gz ...etc.
Is that because of systemd ? people who use
Hi all,
I upgraded my system from Debian 6 to Debian 8 Jessie. logrotate worked on
my log on Debian 6 (I got my_app.log.gz when I put
/etc/logrotate.d/my_app). But it no longer works on Debian 8.
Is that because of systemd ? people who use Arch linux creates
logrotate.service and logrotate.timer
Hi.
On Tue, 01 Sep 2015 08:27:39 -0600
"D. R. Evans" wrote:
> D. R. Evans wrote on 08/31/2015 01:09 PM:
>
> >> The solution of this problem should be as simple as:
> >>
> >> chgrp adm /var/log/polipo/pol*
> >> rm -f /var/log/polipo/polipo.log.1.gz
> >
> > OK; I have done that, and will let yo
D. R. Evans wrote on 08/31/2015 01:09 PM:
>> The solution of this problem should be as simple as:
>>
>> chgrp adm /var/log/polipo/pol*
>> rm -f /var/log/polipo/polipo.log.1.gz
>
> OK; I have done that, and will let you know tomorrow whether the problem has
> gone away.
>
Yep; no notification fr
Reco wrote on 08/29/2015 12:17 PM:
>
> Your /etc/logrotate.d/polipo should contain this line:
>
> su proxy adm
>
Yep.
[stuff elided]
>
> The solution of this problem should be as simple as:
>
> chgrp adm /var/log/polipo/pol*
> rm -f /var/log/polipo/polipo.log.1.gz
OK; I have done that, an
Hi.
On Sat, 29 Aug 2015 09:43:27 -0600
"D. R. Evans" wrote:
> Ever since the upgrade from wheezy to jessie a few days ago, I have been
> receiving the following every day:
>
>
>
> /etc/cron.daily/logrotate:
> error: error setting owner of /var/log/polip
On 07/07/15 09:24, Darac Marjal wrote:
> On Mon, Jul 06, 2015 at 06:16:37PM +0100, Tony van der Hoff wrote:
>> Since installing Jessie from scratch on this laptop, I'm getting a
>> nightly error message from logrotate:
>>
>
>> if [ -z "`$MYAD
On Mon, Jul 06, 2015 at 06:16:37PM +0100, Tony van der Hoff wrote:
> Since installing Jessie from scratch on this laptop, I'm getting a
> nightly error message from logrotate:
>
> /etc/cron.daily/logrotate:
> error: error running shared postrotate script for '/var/log/m
Since installing Jessie from scratch on this laptop, I'm getting a
nightly error message from logrotate:
/etc/cron.daily/logrotate:
error: error running shared postrotate script for '/var/log/mysql.log
/var/log/mysql/mysql.log /var/log/mysql/mysql-slow.log
/var/log/mysql/error.log &
raphaelhertzog.com/2010/10/14/correctly-renaming-a-conffile-in-debian-package-maintainer-scripts/
I think you had previously modified the file and the postinst script
detected this and moved it to .dpkg-remove but then the process
stopped there. It wasn't in the tabooext list and was therefo
On Sat, 2015-03-07 at 19:18 +, Brian wrote:
> On Sat 07 Mar 2015 at 11:21:36 -0600, Laverne Schrock wrote:
>
> > cups-daemon is provided by the cups-daemon package, but dpkg cannot find
> > the provider for cups.dpkg-remove
> >
> > I have two questions:
> > 1) Where did /etc/logrotate.d/cups.
On Sat 07 Mar 2015 at 11:21:36 -0600, Laverne Schrock wrote:
> cups-daemon is provided by the cups-daemon package, but dpkg cannot find
> the provider for cups.dpkg-remove
>
> I have two questions:
> 1) Where did /etc/logrotate.d/cups.dpkg-remove come from?
It looks like you have been using test
on-Env:
Date:
/etc/cron.daily/logrotate:
error: cups.dpkg-remove:1 duplicate log entry
for /var/log/cups/access_log
After looking around, I found the culprits
were /etc/logrotate.d/cups-daemon and /etc/logrotate.d/cups.dpkg-remove
cups-daemon:
erly in the pid file. (Sure, I can kill
it by hand but I really want to know why start-stop-daemon can't kill it
because there is probably some underlying problem that needs solving!)
>
> On Mon, Oct 6, 2014 at 8:06 PM, Joe wrote:
>>
>> On Mon, 6 Oct 2014 19:51:38 +0100
&g
because there is probably some underlying problem that needs solving!)
On Mon, Oct 6, 2014 at 8:06 PM, Joe wrote:
> On Mon, 6 Oct 2014 19:51:38 +0100
> Michael Grant wrote:
>
> > When logrotate fired this month, almost all of my logs remain at zero
> > length and the .1 log cont
On Mon, 6 Oct 2014 19:51:38 +0100
Michael Grant wrote:
> When logrotate fired this month, almost all of my logs remain at zero
> length and the .1 log continues to grow. For example:
>
> ls -l /var/log
> ...
> -rw-r- 1 root adm 0 Oct 5 06:25 messages
&
When logrotate fired this month, almost all of my logs remain at zero
length and the .1 log continues to grow. For example:
ls -l /var/log
...
-rw-r- 1 root adm 0 Oct 5 06:25 messages
-rw-r- 1 root adm 4938 Oct 6 06:56 messages.1
...
-rw-r- 1 root
On 15/06/2014 10:49 AM, André Nunes Batista wrote:
> # logrotate -f -v /etc/logrotate.d/ 2> logrotate.txt
>
> # cat logrotate.txt | grep syslog
> reading config file rsyslog
> rotating pattern: /var/log/syslog
> considering log /var/log/syslog
> rotating log /var/log/sys
On Sat, 14 Jun 2014 21:49:35 -0300
André Nunes Batista wrote:
> 0 -rw-r- 1 root adm 0 Feb 9 07:35 /var/log/syslog.1.gz
Move out syslog* to another place and restart syslog
(looks like you have a hole in file numbering).
If that doesn't work, try to reinstall logrotate and
rsy
Hello debianers!
I recently noticed that some log files on a wheezy box are not being
rotated anymore and are getting rather large. I went through
logrotate.conf and logrotate.d and did not spot anything wrong. When I
run logrotate -f -v /etc/logrotate.conf, some error messages are shown,
but
On Wed, Feb 26, 2014 at 06:43:36AM -0500, Tony Baldwin wrote:
> On Wed, Feb 26, 2014 at 06:41:22AM -0500, Tony Baldwin wrote:
> > On Wed, Feb 26, 2014 at 12:09:05PM +0200, Andrei POPESCU wrote:
> > > On Ma, 25 feb 14, 13:53:39, Tazman Deville wrote:
> > > >
> > > > I DO have anacron installed.
> >
On Mi, 26 feb 14, 06:41:22, Tony Baldwin wrote:
> On Wed, Feb 26, 2014 at 12:09:05PM +0200, Andrei POPESCU wrote:
> > On Ma, 25 feb 14, 13:53:39, Tazman Deville wrote:
> > >
> > > I DO have anacron installed.
> >
> > Well, purge (not remove) it then, or adjust /etc/anacrontab as needed ;)
>
> Th
2014-02-26 12:43 GMT+01:00 Tony Baldwin :
> On Wed, Feb 26, 2014 at 06:41:22AM -0500, Tony Baldwin wrote:
> > On Wed, Feb 26, 2014 at 12:09:05PM +0200, Andrei POPESCU wrote:
> > > On Ma, 25 feb 14, 13:53:39, Tazman Deville wrote:
> > > >
> > > > I DO have anacron installed.
> > >
> > > Well, purge
On Wed, Feb 26, 2014 at 06:41:22AM -0500, Tony Baldwin wrote:
> On Wed, Feb 26, 2014 at 12:09:05PM +0200, Andrei POPESCU wrote:
> > On Ma, 25 feb 14, 13:53:39, Tazman Deville wrote:
> > >
> > > I DO have anacron installed.
> >
> > Well, purge (not remove) it then, or adjust /etc/anacrontab as nee
On Wed, Feb 26, 2014 at 12:09:05PM +0200, Andrei POPESCU wrote:
> On Ma, 25 feb 14, 13:53:39, Tazman Deville wrote:
> >
> > I DO have anacron installed.
>
> Well, purge (not remove) it then, or adjust /etc/anacrontab as needed ;)
>
> Kind regards,
> Andrei
Thanks, Andrei,
But could you explain
On Ma, 25 feb 14, 13:53:39, Tazman Deville wrote:
>
> I DO have anacron installed.
Well, purge (not remove) it then, or adjust /etc/anacrontab as needed ;)
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alio
( cd / && run-parts
> --report /etc/cron.weekly )
> 52 1 � �1 * * � root � �test -x /usr/sbin/anacron || ( cd / && run-parts
> --report /etc/cron.monthly )
>
> I DO have anacron installed.
> I do not know what is relevant from syslog.
> I find no mention of cron,
n || ( cd / && run-parts
> --report /etc/cron.monthly )
>
>
> I DO have anacron installed.
> I do not know what is relevant from syslog.
> I find no mention of cron, crontab, or logrotate in /var/log/syslog
> at all.
>
That's quite weird, indeed you should hav
On Tue, Feb 25, 2014 at 01:10:38PM +, Darac Marjal wrote:
> On Mon, Feb 24, 2014 at 01:57:02PM +0100, Tazman Deville wrote:
> > I have a little server running here in my office,
> > and logrotate kept running at c. 7am, and using up 100% CPU.
>
> Logrotate *itself* should
On Mon, Feb 24, 2014 at 01:57:02PM +0100, Tazman Deville wrote:
> I have a little server running here in my office,
> and logrotate kept running at c. 7am, and using up 100% CPU.
Logrotate *itself* shouldn't use much CPU. But there are a couple of
things I can think that might make it
On Mon, Feb 24, 2014 at 07:38:24PM -0300, André Nunes Batista wrote:
> On Mon, 2014-02-24 at 13:57 +0100, Tazman Deville wrote:
> > I have a little server running here in my office,
> > and logrotate kept running at c. 7am, and using up 100% CPU.
> > I changed the line i
On Mon, Feb 24, 2014 at 11:15:19PM +0200, Andrei POPESCU wrote:
> On Lu, 24 feb 14, 15:06:48, Tazman Deville wrote:
> > On Mon, Feb 24, 2014 at 01:57:02PM +0100, Tazman Deville wrote:
> > > I have a little server running here in my office,
> > > and logrotate kept runn
On Mon, 2014-02-24 at 13:57 +0100, Tazman Deville wrote:
> I have a little server running here in my office,
> and logrotate kept running at c. 7am, and using up 100% CPU.
> I changed the line in /etc/crontab to run cron.daily scripts
> at 4:15am, instead of 7:whateveritwas am.
> 15
On Lu, 24 feb 14, 15:06:48, Tazman Deville wrote:
> On Mon, Feb 24, 2014 at 01:57:02PM +0100, Tazman Deville wrote:
> > I have a little server running here in my office,
> > and logrotate kept running at c. 7am, and using up 100% CPU.
> > I changed the line in /etc/cron
On Mon, Feb 24, 2014 at 01:57:02PM +0100, Tazman Deville wrote:
> I have a little server running here in my office,
> and logrotate kept running at c. 7am, and using up 100% CPU.
> I changed the line in /etc/crontab to run cron.daily scripts
> at 4:15am, instead of 7:whateveritwa
I have a little server running here in my office,
and logrotate kept running at c. 7am, and using up 100% CPU.
I changed the line in /etc/crontab to run cron.daily scripts
at 4:15am, instead of 7:whateveritwas am.
15 4 * * *
Also, in cron.daily/logrotate
I added
nice -n 15
I made these changes
Steffen Dettmer wrote:
> logrotate seems to execute "postrotate" scripts using /bin/sh and I
> found no way where to specify which script interpreter to use.
> Starting with a she-bang line seem to have no effect. Even if I
> manually run logrotate as root who has /bin/bash
On Thu, 2013-12-05 at 17:03 +, Darac Marjal wrote:
> Just a thought, how about making your postrotate command be "/bin/bash
> /path/to/myscript.sh"?
This was already mentioned, resp. the shebang would work, if the script
is called by simply path/myscript.sh, IOW without a leading sh, which
usu
On Thu, Dec 05, 2013 at 10:31:01AM +0100, Steffen Dettmer wrote:
> Hi,
>
> logrotate seems to execute "postrotate" scripts using /bin/sh and I
> found no way where to specify which script interpreter to use.
> Starting with a she-bang line seem to have no effect.
Steffen Dettmer grabbed a keyboard and wrote:
> Hi,
>
> logrotate seems to execute "postrotate" scripts using /bin/sh and I
> found no way where to specify which script interpreter to use.
> Starting with a she-bang line seem to have no effect. Even if I
> manually r
On Thu, 2013-12-05 at 10:44 +0100, Ralf Mardorf wrote:
> On Thu, 2013-12-05 at 10:43 +0100, Ralf Mardorf wrote:
> > On Thu, 2013-12-05 at 10:31 +0100, Steffen Dettmer wrote:
> > > logrotate seems to execute "postrotate" scripts using /bin/sh and I
> > > found
On Thu, 2013-12-05 at 10:43 +0100, Ralf Mardorf wrote:
> On Thu, 2013-12-05 at 10:31 +0100, Steffen Dettmer wrote:
> > logrotate seems to execute "postrotate" scripts using /bin/sh and I
> > found no way where to specify which script interpreter to use.
> > Starti
On Thu, 2013-12-05 at 10:31 +0100, Steffen Dettmer wrote:
> logrotate seems to execute "postrotate" scripts using /bin/sh and I
> found no way where to specify which script interpreter to use.
> Starting with a she-bang line seem to have no effect. Even if I
> manually run
Hi,
logrotate seems to execute "postrotate" scripts using /bin/sh and I
found no way where to specify which script interpreter to use.
Starting with a she-bang line seem to have no effect. Even if I
manually run logrotate as root who has /bin/bash as login shell,
/bin/sh is used.
H
Hi,
I am sorry for blank post - my mistake.
Dňa 18.08.2013 11:00 Pertti Kosunen wrote / napísal(a):
> On Thu, 26 Jul 2012 10:42:30 +0200, Slavko wrote:
>> in last days (perhaps weeks) i get daily mail from cron's logrotate task
>> with this:
>>
>> /etc/cron.daily
Dňa 18.08.2013 11:00 Pertti Kosunen wrote / napísal(a):
> On Thu, 26 Jul 2012 10:42:30 +0200, Slavko wrote:
>> in last days (perhaps weeks) i get daily mail from cron's logrotate task
>> with this:
>>
>> /etc/cron.daily/logrotate:
>> gzip: stdin: file size
On Thu, 26 Jul 2012 10:42:30 +0200, Slavko wrote:
in last days (perhaps weeks) i get daily mail from cron's logrotate task
with this:
/etc/cron.daily/logrotate:
gzip: stdin: file size changed while zipping
I had this too over a year on testing/unstable. I did put --verbose to
logrotat
s, and changed the rights to the user from the script:
> mkdir /var/log/script
> chown script.root /var/log/script
> chmod 640 /var/log/script
>
> But logrotate "complains":
> =
> ~# logrotate -d
> /etc/logrotate.d/scrip
/script
chown script.root /var/log/script
chmod 640 /var/log/script
But logrotate "complains":
=====
~# logrotate -d /etc/logrotate.d/script
reading config file /etc/logrotate.d/script
reading config info for /var/log/script/script.log
Handling 1 logs
Meike Stone writes:
>> >From your explanations, I understand that logrotate would create the
>> file if logrotate rotates the file, which requires the file to exist in
>> the first place, so create it manually and let logrotate rotate and
>> create the file in the futu
On Fri, 21 Sep 2012 13:55:33 +0200, Meike Stone wrote:
>> >From your explanations, I understand that logrotate would create the
>> file if logrotate rotates the file, which requires the file to exist in
>> the first place, so create it manually and let logrotate rotate and
> >From your explanations, I understand that logrotate would create the
> file if logrotate rotates the file, which requires the file to exist in
> the first place, so create it manually and let logrotate rotate and
> create the file in the future. Does that work? (This somewhat i
1 - 100 of 361 matches
Mail list logo
