Re: Why sysklog uses its own logrotate and not logrotate script
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/28/2004 01:10 AM, Martin Schulze wrote: | Clemens Schwaighofer wrote: | |Hi, | |I would like to know why sysklog package uses its own logrotation |scripts and not logrotate. | | | Try to convert it to logrotate and soon you will understand why it still | uses savelog. Well I will see, but I think they are very rare special cases. Many people I know converted these to logrotate, and I never heard anything bad about it. - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBhyRpjBz/yQjBxz8RAt+JAJ9h76QXT1k6GvQ4WdjM1jaNbrUp0QCgmmZX XG9kGmi8scgJhbveOyd2n3Y= =uCEX -END PGP SIGNATURE-
Re: Why sysklog uses its own logrotate and not logrotate script
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/28/2004 05:53 PM, Adeodato Simó wrote: | albeit both are Priority: important, sysklogd is Section: base. and, | iiuc, base should be self-contained (that is, packages in base must | not depend on packages outside it). well, logrotate is almost base. I can hardly imagine a normal installation without it (excep perhaps embedded devices). - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBhyUtjBz/yQjBxz8RAj+wAKCLLMyC4/KS6b+91R7NXl8X/kf6ZgCeP6xV tPfpU3xcNxyKlnnbgPVKcUQ= =QXy0 -END PGP SIGNATURE-
Re: Why sysklog uses its own logrotate and not logrotate script
On Thu, 28 Oct 2004 21:42:09 +0400, Nikita V. Youshchenko
[EMAIL PROTECTED] wrote:
and before anybody asks, I already but all the things into logrotate. I
just curious why its not there from beginning.
With current default configuration, if I add some more log files
info /etc/syslog.conf (e.g. to catch localN facilities), they get rotation
automatically. Can the same be achieved with logrotate same (without having
to add new files to logrotate configuration manually - it's always bad to
duplicate configuration)?
It would be easy if all syslogd log files were in a single directory,
which is not the case.
It would be easier for logrotate if it would support backticks in a
logrotate config file:
`syslogd-listfiles` {
}
Geez, one more point for the logrotate++ todo list.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber |Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG Rightful Heir | Fon: *49 621 72739834
Re: Why sysklog uses its own logrotate and not logrotate script
Graham Wilson wrote: On Wed, Oct 27, 2004 at 06:10:43PM +0200, Martin Schulze wrote: Clemens Schwaighofer wrote: I would like to know why sysklog package uses its own logrotation scripts and not logrotate. Try to convert it to logrotate and soon you will understand why it still uses savelog. It seems like he did. It's something I always do on machines I install. I fail to see why sysklogd still uses savelog. Please send me the patch. Regards, Joey -- Those who don't understand Unix are condemned to reinvent it, poorly. Please always Cc to me when replying to me on the lists.
Re: Why sysklog uses its own logrotate and not logrotate script
On Thu, Oct 28, 2004 at 10:53:12AM +0200, Adeodato Simó wrote: * Clemens Schwaighofer [Wed, 27 Oct 2004 23:02:44 +0900]: I would like to know why sysklog package uses its own logrotation scripts and not logrotate. albeit both are Priority: important, sysklogd is Section: base. and, iiuc, base should be self-contained (that is, packages in base must not depend on packages outside it). I don't believe such a restriction exists. Section: base is pretty much a relic, obsoleted long ago by debootstrap. -- Colin Watson [EMAIL PROTECTED]
Re: Why sysklog uses its own logrotate and not logrotate script
On Mon, 1 Nov 2004 15:29:36 +0100, Martin Schulze [EMAIL PROTECTED] wrote: Please send me the patch. Honestly, looking at sysklogd's bug list doesn't make people get the impression that it makes sense to file patches against the sysklogd package. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber |Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG Rightful Heir | Fon: *49 621 72739834
Re: Why sysklog uses its own logrotate and not logrotate script
On Mon, Nov 01, 2004 at 09:39:51PM +0100, Marc Haber wrote: On Mon, 1 Nov 2004 15:29:36 +0100, Martin Schulze [EMAIL PROTECTED] wrote: Please send me the patch. Honestly, looking at sysklogd's bug list doesn't make people get the impression that it makes sense to file patches against the sysklogd package. Honestly, comments like these don't give people the impression that you're interested in working with maintainers to get bugs fixed. If you aren't willing to submit a patch to address the bug in question, you really have no business complaining about the state of another maintainer's package. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Why sysklog uses its own logrotate and not logrotate script
On Wed, Oct 27, 2004 at 06:10:43PM +0200, Martin Schulze wrote: Clemens Schwaighofer wrote: I would like to know why sysklog package uses its own logrotation scripts and not logrotate. Try to convert it to logrotate and soon you will understand why it still uses savelog. It seems like he did. It's something I always do on machines I install. I fail to see why sysklogd still uses savelog. -- gram
Re: Why sysklog uses its own logrotate and not logrotate script
* Clemens Schwaighofer [Wed, 27 Oct 2004 23:02:44 +0900]: Hi, I would like to know why sysklog package uses its own logrotation scripts and not logrotate. albeit both are Priority: important, sysklogd is Section: base. and, iiuc, base should be self-contained (that is, packages in base must not depend on packages outside it). -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 Old men are fond of giving good advice to console themselves for their inability to set a bad example. -- La Rochefoucauld, Maxims
Re: Why sysklog uses its own logrotate and not logrotate script
and before anybody asks, I already but all the things into logrotate. I just curious why its not there from beginning. With current default configuration, if I add some more log files info /etc/syslog.conf (e.g. to catch localN facilities), they get rotation automatically. Can the same be achieved with logrotate same (without having to add new files to logrotate configuration manually - it's always bad to duplicate configuration)?
Re: Why sysklog uses its own logrotate and not logrotate script
Clemens Schwaighofer wrote: Hi, I would like to know why sysklog package uses its own logrotation scripts and not logrotate. Try to convert it to logrotate and soon you will understand why it still uses savelog. Because it uses its own scripts, its rather tricky to configure. Eg its impossible to have the first rotatet log (syslog.0) to be compressed. According to the help test in the cron sysklog file there are reasons of some possible open file handles. Until syslog is reloaded, yes. You are free to modify the scripts. They are marked as configuration files and hence future upgrades will honour your modifications. Regards, Joey -- GNU does not eliminate all the world's problems, only some of them. -- The GNU Manifesto Please always Cc to me when replying to me on the lists.
