Hello,
I've been been recently working on changes to improve how the server
logs are handled to make it more straightforward to use commonly
used tools for log rotation (like logrotate) out of the box. I'd
like to solicit some comments on the subject.
Currently, the when doing file-based
I am looking for a way to tune the timeout before failing over to another
AFS server for replicated volumes, but cannot seem to find any suitable
runtime parameters to tweak. Do any such parameters exist?
We have some replicated web servers serving data from replicated RO volumes.
If one of the
On Thu, 2 Dec 2010 13:56:07 -0500 (EST)
Thomas M. Payerle paye...@umd.edu wrote:
I am looking for a way to tune the timeout before failing over to
another AFS server for replicated volumes, but cannot seem to find any
suitable runtime parameters to tweak. Do any such parameters exist?
Sort
On Thu, 02 Dec 2010 13:50:36 -0500
Michael Meffie mmef...@sinenomine.net wrote:
I propose in some future release of openafs this behavior be
deprecated and, by default, the server would simply append to the
already existing log file on startup. Also, each server would handle
the HUP signal to
On Thu, 02 Dec 2010 13:50:36 -0500
Michael Meffie mmef...@sinenomine.net wrote:
I propose in some future release of openafs this behavior be
deprecated and, by default, the server would simply append to the
already existing log file on startup. Also, each server would handle
the HUP signal to
On Thu, 2 Dec 2010 14:39:35 -0500
chas williams - CONTRACTOR c...@cmf.nrl.navy.mil wrote:
could the afs servers optionally use the existing syslog mechanism.
this would allow for a couple other things, like centralized logging.
Fileserver can already do that (option -syslog), but yeah,
chas williams - CONTRACTOR wrote:
On Thu, 02 Dec 2010 13:50:36 -0500
Michael Meffie mmef...@sinenomine.net wrote:
I propose in some future release of openafs this behavior be
deprecated and, by default, the server would simply append to the
already existing log file on startup. Also, each
Andrew Deason wrote:
On Thu, 02 Dec 2010 13:50:36 -0500
Michael Meffie mmef...@sinenomine.net wrote:
I propose in some future release of openafs this behavior be
deprecated and, by default, the server would simply append to the
already existing log file on startup. Also, each server would
I've been been recently working on changes to improve how the server
logs are handled to make it more straightforward to use commonly
used tools for log rotation (like logrotate) out of the box. I'd
like to solicit some comments on the subject.
Currently, the when doing file-based logging,
The changes in the kernel that makes us unable to build the NFS
translator appeared in 2.6.29. So I would guess that SLES 11 (no SP)
would work (2.6.27), but that SLES 11 SP1 (2.6.32), OpenSUSE 11.3
(2.6.34) or anything newer would not.
Marc
I tried with SLES 11 (no SP) and still get the same
On Thu, Dec 2, 2010 at 6:15 PM, Karen Eldredge
karen.eldre...@infoprint.com wrote:
The changes in the kernel that makes us unable to build the NFS
translator appeared in 2.6.29. So I would guess that SLES 11 (no SP)
would work (2.6.27), but that SLES 11 SP1 (2.6.32), OpenSUSE 11.3
(2.6.34) or
Andrew Deason adea...@sinenomine.net writes:
The fileserver already automatically checks every five minutes (I think)
if it needs to reopen the log, and does so if the log file was moved. If
people would find that acceptable, I'd rather just do something similar
for all daemons.
I think that
Michael Meffie mmef...@sinenomine.net writes:
I've been been recently working on changes to improve how the server
logs are handled to make it more straightforward to use commonly used
tools for log rotation (like logrotate) out of the box. I'd like to
solicit some comments on the subject.
I
On 12/2/2010 8:06 PM, Russ Allbery wrote:
I think you should just deprecate all logging methods other than syslog,
at least on UNIX. There's a perfectly useable system service that handles
all this already. I don't think it's a useful use of our development
resources to do a halfway
On Thu, Dec 2, 2010 at 3:28 PM, David R Boldt dbo...@usgs.gov wrote:
I've been been recently working on changes to improve how the server
logs are handled to make it more straightforward to use commonly
used tools for log rotation (like logrotate) out of the box. I'd
like to solicit some
On Thu, 02 Dec 2010 17:05:31 -0800
Russ Allbery r...@stanford.edu wrote:
Andrew Deason adea...@sinenomine.net writes:
The fileserver already automatically checks every five minutes (I
think) if it needs to reopen the log, and does so if the log file
was moved. If people would find that
Andrew Deason adea...@sinenomine.net writes:
Russ Allbery r...@stanford.edu wrote:
I think that won't work. You need to be able to trigger the rotation
immediately; five minutes later, the file that the server is still
writing to has probably been unlinked after being compressed, and all
If the wish list is open, the ability to log to a pipe so that one could
use a tool such a cronolog would be convenient for us.
Hello David,
Yes, logging to a pipe is already possible, and what I'm
suggesting would not change that. And, as others have mentioned,
logging to syslog is also
On 12/2/2010 10:22 PM, Michael Meffie wrote:
If the wish list is open, the ability to log to a pipe so that one
could use a tool such a cronolog would be convenient for us.
Hello David,
Yes, logging to a pipe is already possible, and what I'm
suggesting would not change that. And, as
On 12/2/2010 10:45 PM, Russ Allbery wrote:
Jeffrey Altman jalt...@secure-endpoints.com writes:
Of course that requires that there be a log rotation tool. I don't
think that OpenAFS by default should fill the disk partition simply
because it is permitted to run for years without restarts and
Jeffrey Altman jalt...@secure-endpoints.com writes:
Of course that requires that there be a log rotation tool. I don't
think that OpenAFS by default should fill the disk partition simply
because it is permitted to run for years without restarts and the admin
has not configured a log rotation
Jeffrey Altman jalt...@secure-endpoints.com writes:
My one concern to switching to something like syslog by default is that
bos getlog will need to be re-implemented in a different fashion.
Yeah, this is a very good point. I think I've used bos getlog maybe three
times in the past fifteen
Russ Allbery r...@stanford.edu wrote:
Jeffrey Altman jalt...@secure-endpoints.com writes:
My one concern to switching to something like syslog by default is
that bos getlog will need to be re-implemented in a different
fashion.
Yeah, this is a very good point. I think I've used bos getlog
Christopher D. Clausen cclau...@acm.org writes:
Russ Allbery r...@stanford.edu wrote:
Yeah, this is a very good point. I think I've used bos getlog maybe
three times in the past fifteen years, so I never think about it, but
I suspect others use it more than I do.
I'd say that you could
24 matches
Mail list logo
