Control: tags -1 moreinfo unreproducible
Hi,
can reproduce the second issue with the recent version 3.14.0-2?
Also can you post the configuration file that lead to the first issue,
maybe logrotate should give a better error message.
Best regards
Christian Göttsche
Firstly, why have you got all those zero length .gz files in
/var/log/syslog-ng/current_logs ?
Also, can you do:
ls -altr /var/log/syslog-ng/current_logs
Do you have both log.1 and log.1.gz files left over from earlier
experiments?
--
Paul Martin
Le 23/01/2016 13:16, Paul Martin a écrit :
any idea ?
Try running logrotate with the "-v" option?
Paul,
please many thanks to read output of my tests, either with --debug,
either with --debug --verbose options
root@srv-dhcp-1:/etc# logrotate --verbose /tmp/logrotate_test ; echo $?
readi
> any idea ?
Try running logrotate with the "-v" option?
--
Paul Martin
Paul,
thanks for your reply,
After looking at all my scripts, my problem was due to a bad character
in one config file.The logrotate interpreter could not understand this
command.
But i have still one problem with this simple script:
root@srv-dhcp-1:/etc# cat /tmp/logrotate_test
/var/log/s
On Sun, Nov 08, 2015 at 07:37:31PM +0100, LACROIX Jean Marc wrote:
> Le 08/11/2015 14:33, Paul Martin a écrit :
> >On Sun, Nov 08, 2015 at 08:32:39AM +0100, LACROIX Jean Marc wrote:
> >
> >>Im am using logrotate on the host and the same logrotate on one
> >>container managed by LXC, with of
Le 08/11/2015 14:33, Paul Martin a écrit :
On Sun, Nov 08, 2015 at 08:32:39AM +0100, LACROIX Jean Marc wrote:
Im am using logrotate on the host and the same logrotate on one
container managed by LXC, with of course the same Debian release.
Are the two logrotate binaries the same, or ha
On Sun, Nov 08, 2015 at 08:32:39AM +0100, LACROIX Jean Marc wrote:
> Im am using logrotate on the host and the same logrotate on one
> container managed by LXC, with of course the same Debian release.
Are the two logrotate binaries the same, or has LXC replaced the
containerized one with s
Package: logrotate
Version: 3.8.7-1+b1
Dears Maintainers,
I have a strange behaviour on Debian Jessie on ARM platform with 2
differents contexts when using logotate with default config Debian
files.
Im am using logrotate on the host and the same logrotate on one
container managed
9 matches
Mail list logo