| 1 |
Le Lundi 6 Février 2006 01:11, Markus Dittrich a écrit : |
| 2 |
> Hi Guillaume, |
| 3 |
> |
| 4 |
> I've never encountered this myself, but your output |
| 5 |
> seems to suggest to me that something is going wrong when |
| 6 |
> logrotate is reading /etc/logrotate.d/syslog-ng. |
| 7 |
> Take a look at it or try moving it to see |
| 8 |
> if this fixes the problem. |
| 9 |
|
| 10 |
No, this was not the problem ! |
| 11 |
I finally found it (after two weeks looking for the problem...) ! |
| 12 |
|
| 13 |
I simply had a buggy 15M /var/lib/logrotate.status with bad informations in |
| 14 |
it. Probably due to an old wrong logrotate configuration. |
| 15 |
So it has nothing to do with hardened profile ;) |
| 16 |
|
| 17 |
Many thanks for your help, |
| 18 |
|
| 19 |
-- |
| 20 |
Guillaume Castagnino |
| 21 |
guilc@×××××××.net / casta@×××××.info |
| 22 |
GnuPG/PGP key : |
| 23 |
http://wwwkeys.pgp.net:11371/pks/lookup?op=vindex&search=0x8AF468AF |
| 24 |
Fingerprint : CD52 FE40 9592 BA1E E89D 5FB6 820E 4742 8AF4 68AF |
Archives