On Fri, Aug 10, 2007 at 02:19:55PM +0300, Artis Caune wrote:
> How about aditional flag ("X") to newsyslog, which don't compress first
> log file?
> This is useful for apache.
>...
After a bit of discussion here, and using a patch to newsyslog.c
supplied by Dir
On Sun, Aug 12, 2007 at 02:24:20PM +0200, Ulrich Spoerlein wrote:
> I'd rather see an extension for newsyslog which would rotate foo to
> foo.2007-08-12.gz, iff rotation is done every day at midnight.
Sorry to hijack the thread, but this is something that I've been looking
for fo
On Fri, 10.08.2007 at 09:13:18 -0700, David Wolfskill wrote:
> On Fri, Aug 10, 2007 at 02:19:55PM +0300, Artis Caune wrote:
> > How about aditional flag ("X") to newsyslog, which don't compress first
> > log file?
> >...
>
> Interesting idea, but it
rol
of those of us who run the machines, we need to keep some number of the
most recent of them uncompressed.
> I'd rather see an extension for newsyslog which would rotate foo to
> foo.2007-08-12.gz, iff rotation is done every day at midnight.
>
> That way, you get a 'stab
> Ah -- well, then: by all means. I'm even more willing to test other
> folks' work than I am to hack away at code. :-}
>
> And since I had tested my own Perl script, I think I should be able to
> help out with this. :-)
>
> And "after Sunday" is not a problem at all: thank you!
I tested the
On Sat, Aug 11, 2007 at 04:39:42PM +0200, Dirk GOUDERS wrote:
>
> > We could extend the 'count' field to accept 'N+M'. N being the number of
> > plain log files and M the number of compressed ones.
> >
> > This would also negate the need for a new flag.
>
> It could also be done with a numerical
On Sat, Aug 11, 2007 at 04:12:29PM +0200, Joost Bekkers wrote:
> On Fri, August 10, 2007 18:13, David Wolfskill wrote:
> >
> > Biggest problem I can see (with what I want to accomplish) is how to
> > specify it in the config file.
> >
>
> We could extend the 'count' field to accept 'N+M'. N being
> We could extend the 'count' field to accept 'N+M'. N being the number of
> plain log files and M the number of compressed ones.
>
> This would also negate the need for a new flag.
It could also be done with a numerical flag "n" where n is a number that
specifies the extension of the logfile up
On Fri, August 10, 2007 18:13, David Wolfskill wrote:
>
> Biggest problem I can see (with what I want to accomplish) is how to
> specify it in the config file.
>
We could extend the 'count' field to accept 'N+M'. N being the number of
plain log files and M the number of compressed ones.
This woul
> How about using the flag "0" similar to that in newsyslog written by
> Theodore Ts'o of MIT Project Athena:
Sorry, I have to correct myself:
The flag "0" appears in the enhanced version of newsyslog that
is mai
On Fri, Aug 10, 2007 at 02:19:55PM +0300, Artis Caune wrote:
> How about aditional flag ("X") to newsyslog, which don't compress first
> log file?
>...
Interesting idea, but it still falls short of something we recently
needed to do at work:
We have a requirement
> How about aditional flag ("X") to newsyslog, which don't compress first
> log file?
How about using the flag "0" similar to that in newsyslog written by
Theodore Ts'o of MIT Project Athena:
0 The 0 flag means that the most recent archive o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 10 Aug 2007 13:51+0200, Trond Endrest�l wrote:
Why do you need to complicate matters?
My bad. I didn't read your entire post. I thought you wanted to
drop compression of every generation of the log files.
Sorry for the noise.
- --
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 10 Aug 2007 14:19+0300, Artis Caune wrote:
How about aditional flag ("X") to newsyslog, which don't compress first log
file?
Why do you need to complicate matters? Just remove the Z flag from the
applicable lines in /etc
How about aditional flag ("X") to newsyslog, which don't compress first
log file?
This is useful for apache.
# cat /etc/newsyslog.conf
/var/log/httpd-access.log www:www 640 64 * $W1D0 BCZX
/var/run/httpd.pid 30
# ls /var/log/archive2/
httpd-access.log.0
httpd-access
On Mon, Oct 04, 2004 at 10:33:25PM -0400, Christopher Nehren wrote:
> On Mon, 2004-10-04 at 23:35 +, Brooks Davis wrote:
> > brooks 2004-10-04 23:35:13 UTC
> >
> > FreeBSD src repository
> >
> > Modified files:
> > usr.sbin/newsysl
At 10:33 PM -0400 10/4/04, Christopher Nehren wrote:
On Mon, 2004-10-04 at 23:35 +, Brooks Davis wrote:
brooks 2004-10-04 23:35:13 UTC
FreeBSD src repository
Modified files:
usr.sbin/newsyslog newsyslog.8 newsyslog.c
Log:
> Add a new -d argument which is used
On Mon, 2004-10-04 at 23:35 +, Brooks Davis wrote:
> brooks 2004-10-04 23:35:13 UTC
>
> FreeBSD src repository
>
> Modified files:
> usr.sbin/newsyslog newsyslog.8 newsyslog.c
> Log:
> Add a new -d argument which is used to specify an alternat
+ <[EMAIL PROTECTED]>, Cyrille Lefevre wrote:
>> I add script call features to newsyslog. This adds a one field to
>> newsyslog.conf. When newsyslog processed log file, this can execute
>> arbitrary program.
>>
>> Situation to assume:
>> * For the lo
Toshihiko ARAI wrote:
> Hello,
>
> I add script call features to newsyslog. This adds a one field to
> newsyslog.conf. When newsyslog processed log file, this can execute
> arbitrary program.
>
> Situation to assume:
> * For the log file which cannot use signal.
>
Hello,
I add script call features to newsyslog. This adds a one field to
newsyslog.conf. When newsyslog processed log file, this can execute
arbitrary program.
Situation to assume:
* For the log file which cannot use signal.
* Cases to do statistical application for log file.
A sample
Can anybody confirm that the examples in newsyslog's manpage for things
like:
$MLD0 , $M1D0 and such
actually work.
No matter which I use I keep getting these mails from newsyslog:
newsyslog: malformed interval/at:
/var/log/news/news.notice 644 2 *$M1D0 Z
AFAIK
I've hacked newsyslog(8) to accept a list of log files to process on
the command line (very useful in combination with -F). See attached
patches. I'll commit this in a few days if noone objects.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
Index: n
I've put a tarball of my enhancements to newsyslog on
http://www.freebsd.org/~hm/newsyslog.tar.gz
The differences to the in-tree versions are:
- ability to archive rotated logfiles into a separate configurable
directory
- provide another method (in addition to the ISO 8601 forma
> A better patch would check to see if the text to the right of the '.'
> is a valid group... However, the above will still parse
>
> fred.jones:fred.jones
>
> in the most desirable way, so I suppose the validity checking is
> overkill.
This is what I plan to commit (w/in minutes):
-
In message <19755.933088...@axl.noc.iafrica.com> Sheldon Hearn writes:
: +#ifdef SUPPORT_DOT
: +/* Older configurations used '.' between user and group */
: +if ((group = strchr(q, ':')) != NULL ||
: +(group = strchr(q, '.')) != NULL) {
: +#else
:
> A better patch would check to see if the text to the right of the '.'
> is a valid group... However, the above will still parse
>
> fred.jones:fred.jones
>
> in the most desirable way, so I suppose the validity checking is
> overkill.
This is what I plan to commit (w/in minutes):
-
In message <[EMAIL PROTECTED]> Sheldon Hearn writes:
: +#ifdef SUPPORT_DOT
: +/* Older configurations used '.' between user and group */
: +if ((group = strchr(q, ':')) != NULL ||
: +(group = strchr(q, '.')) != NULL) {
: +#else
:
On Tue, 27 Jul 1999 09:07:34 MST, "David O'Brien" wrote:
> To paraphase Bill Paul:
>
> G that's part of my last name.
N! I was chatting to a buddy about this just after I sent you the
diffs and actually mentioned to him that I thought I might have made
this mistake again.
Since th
On Tue, Jul 27, 1999 at 05:25:23PM +0200, Sheldon Hearn wrote:
>
> Hi Brian,
To paraphase Bill Paul:
G that's part of my last name.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the
d me that we do as much as (but no more than) we can to
make the upgrade path as smooth as possible. I don't think that the
extra line of code is more than we can do. :-)
I'm acting out of self-preservation here. If a line of code can save me
5 PR's on 4.0-RELEASE, I'll take t
On Tue, 27 Jul 1999 09:07:34 MST, "David O'Brien" wrote:
> To paraphase Bill Paul:
>
> G that's part of my last name.
N! I was chatting to a buddy about this just after I sent you the
diffs and actually mentioned to him that I thought I might have made
this mistake again.
Since t
On Tue, Jul 27, 1999 at 05:25:23PM +0200, Sheldon Hearn wrote:
>
> Hi Brian,
To paraphase Bill Paul:
G that's part of my last name.
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the bo
r- and
groupnames which include dots. I took my lead from chown(8).
Ciao,
Sheldon.
Index: Makefile
===
RCS file: /home/ncvs/src/usr.sbin/newsyslog/Makefile,v
retrieving revision 1.6
diff -u -d -r1.6 Makefile
--- Makefile1999/01/22 19
> COMPATIBILITY
> Previous versions of the chown utility used the dot (``.'')
> character to distinguish the group name. Begining with FreeBSD
> 4.0, this has been changed to be a colon (``:'') character so that
> user and group names may contain the dot character.
Hum... I th
> This one raised a number of eyebrows and a few people asked you to hold
> on to legacy support for a single release. It's a reasonable request,
> given the obscure error message one gets for providing the previously
> supported syntax:
>
> newsyslog: error in confi
d me that we do as much as (but no more than) we can to
make the upgrade path as smooth as possible. I don't think that the
extra line of code is more than we can do. :-)
I'm acting out of self-preservation here. If a line of code can save me
5 PR's on 4.0-RELEASE, I'll take t
r- and
groupnames which include dots. I took my lead from chown(8).
Ciao,
Sheldon.
Index: Makefile
===
RCS file: /home/ncvs/src/usr.sbin/newsyslog/Makefile,v
retrieving revision 1.6
diff -u -d -r1.6 Makefile
--- Makefile1999/01/22
> COMPATIBILITY
> Previous versions of the chown utility used the dot (``.'')
> character to distinguish the group name. Begining with FreeBSD
> 4.0, this has been changed to be a colon (``:'') character so that
> user and group names may contain the dot character.
Hum... I t
> This one raised a number of eyebrows and a few people asked you to hold
> on to legacy support for a single release. It's a reasonable request,
> given the obscure error message one gets for providing the previously
> supported syntax:
>
> newsyslog: error in confi
On Tue, 27 Jul 1999 06:57:49 -0400, Tim Vanderhoek wrote:
> Consider also adding owner:group support to -stable in order to
> provide the longest change-over period possible.
You have to read the CURRENT newsyslog(8) manpage before you realize
that this is a lose-lose situation:
COMPATI
On Tue, Jul 27, 1999 at 12:08:10PM +0200, Sheldon Hearn wrote:
>
> strongly opposed to it, or because you don't have time? If it's the
> latter, I'll do it. If the former, note that your commit message was
Consider also adding owner:group support to -stable in order to
provide the longest change-
On Tue, 27 Jul 1999 06:57:49 -0400, Tim Vanderhoek wrote:
> Consider also adding owner:group support to -stable in order to
> provide the longest change-over period possible.
You have to read the CURRENT newsyslog(8) manpage before you realize
that this is a lose-lose sit
er of eyebrows and a few people asked you to hold
on to legacy support for a single release. It's a reasonable request,
given the obscure error message one gets for providing the previously
supported syntax:
newsyslog: error in config file; bad permissions:
/var/log/exim/mainlog exim.mail
On Tue, Jul 27, 1999 at 12:08:10PM +0200, Sheldon Hearn wrote:
>
> strongly opposed to it, or because you don't have time? If it's the
> latter, I'll do it. If the former, note that your commit message was
Consider also adding owner:group support to -stable in order to
provide the longest change
er of eyebrows and a few people asked you to hold
on to legacy support for a single release. It's a reasonable request,
given the obscure error message one gets for providing the previously
supported syntax:
newsyslog: error in config file; bad permissions:
/var/log/exim/mainlog exim.mail
46 matches
Mail list logo
