On 27/09/18 20:16, Ferenc Wágner wrote:
> Christine Caulfield writes:
>
>> I'm also looking into high-res timestamps for logfiles too.
>
> Wouldn't that be a useful option for the syslog output as well? I'm
> sometimes concerned by the batching effect added by the transport
> between the
Christine Caulfield writes:
> I'm also looking into high-res timestamps for logfiles too.
Wouldn't that be a useful option for the syslog output as well? I'm
sometimes concerned by the batching effect added by the transport
between the application and the (local) log server (rsyslog or
Ken Gaillot writes:
> libqb would simply provide the API for reopening the log, and clients
> such as pacemaker would intercept the signal and call the API.
Just for posterity: you needn't restrict yourself to signals. Logrotate
has nothing to do with signals. Signals are a rather limited
On Thu, 2018-09-27 at 16:09 +0100, Christine Caulfield wrote:
> On 27/09/18 16:01, Ken Gaillot wrote:
> > On Thu, 2018-09-27 at 09:58 -0500, Ken Gaillot wrote:
> > > On Thu, 2018-09-27 at 15:32 +0200, Ferenc Wágner wrote:
> > > > Christine Caulfield writes:
> > > >
> > > > > TBH I would be quite
On 27/09/18 16:01, Ken Gaillot wrote:
> On Thu, 2018-09-27 at 09:58 -0500, Ken Gaillot wrote:
>> On Thu, 2018-09-27 at 15:32 +0200, Ferenc Wágner wrote:
>>> Christine Caulfield writes:
>>>
TBH I would be quite happy to leave this to logrotate but the
message I
was getting here is
On Thu, 2018-09-27 at 09:58 -0500, Ken Gaillot wrote:
> On Thu, 2018-09-27 at 15:32 +0200, Ferenc Wágner wrote:
> > Christine Caulfield writes:
> >
> > > TBH I would be quite happy to leave this to logrotate but the
> > > message I
> > > was getting here is that we need additional help from
On Thu, 2018-09-27 at 15:32 +0200, Ferenc Wágner wrote:
> Christine Caulfield writes:
>
> > TBH I would be quite happy to leave this to logrotate but the
> > message I
> > was getting here is that we need additional help from libqb. I'm
> > willing
> > to go with a consensus on this though
>
>
Christine Caulfield writes:
> TBH I would be quite happy to leave this to logrotate but the message I
> was getting here is that we need additional help from libqb. I'm willing
> to go with a consensus on this though
Yes, to do a proper job logrotate has to have a way to get the log files
On 27/09/18 12:52, Ferenc Wágner wrote:
> Christine Caulfield writes:
>
>> I'm looking into new features for libqb and the option in
>> https://github.com/ClusterLabs/libqb/issues/142#issuecomment-76206425
>> looks like a good option to me.
>
> It feels backwards to me: traditionally,
Christine Caulfield writes:
> I'm looking into new features for libqb and the option in
> https://github.com/ClusterLabs/libqb/issues/142#issuecomment-76206425
> looks like a good option to me.
It feels backwards to me: traditionally, increasing numbers signify
older rotated logs, while this
On 26/09/18 09:21, Ferenc Wágner wrote:
> Jan Friesse writes:
>
>> wagner.fer...@kifu.gov.hu writes:
>>
>>> triggered by your favourite IPC mechanism (SIGHUP and SIGUSRx are common
>>> choices, but logging.* cmap keys probably fit Corosync better). That
>>> would enable proper log rotation.
>>
Ferenc,
Jan Friesse writes:
wagner.fer...@kifu.gov.hu writes:
triggered by your favourite IPC mechanism (SIGHUP and SIGUSRx are common
choices, but logging.* cmap keys probably fit Corosync better). That
would enable proper log rotation.
What is the reason that you find "copytruncate"
Jan Friesse writes:
> wagner.fer...@kifu.gov.hu writes:
>
>> triggered by your favourite IPC mechanism (SIGHUP and SIGUSRx are common
>> choices, but logging.* cmap keys probably fit Corosync better). That
>> would enable proper log rotation.
>
> What is the reason that you find "copytruncate"
Ferenc,
Jan Friesse writes:
Default example config should be definitively ported to newer style of
nodelist without interface section. example.udpu can probably be
deleted as well as example.xml (whole idea of having XML was because
of cluster config tools like pcs, but these tools never
Jan Friesse writes:
> Default example config should be definitively ported to newer style of
> nodelist without interface section. example.udpu can probably be
> deleted as well as example.xml (whole idea of having XML was because
> of cluster config tools like pcs, but these tools never used
>
Ferenc,
Jan Friesse writes:
Have you had a time to play with packaging current alpha to find out
if there are no issues? I had no problems with Fedora, but Debian has
a lot of patches, and I would be really grateful if we could reduce
them a lot - so please let me know if there is patch
On 24/09/18 13:12, Ferenc Wágner wrote:
> Jan Friesse writes:
>
>> Have you had a time to play with packaging current alpha to find out
>> if there are no issues? I had no problems with Fedora, but Debian has
>> a lot of patches, and I would be really grateful if we could reduce
>> them a lot -
Jan Friesse writes:
> Have you had a time to play with packaging current alpha to find out
> if there are no issues? I had no problems with Fedora, but Debian has
> a lot of patches, and I would be really grateful if we could reduce
> them a lot - so please let me know if there is patch which
Ferenc,
Jan Friesse writes:
Currently I'm pretty happy with current Corosync alpha stability so it
would be possible to release final right now, but because I want to
give us some room to break protocol/abi (only if needed and right now
I don't see any strong reason for such breakage), I
Jan Friesse writes:
> Currently I'm pretty happy with current Corosync alpha stability so it
> would be possible to release final right now, but because I want to
> give us some room to break protocol/abi (only if needed and right now
> I don't see any strong reason for such breakage), I didn't
Ferenc,
Jan Friesse writes:
try corosync 3.x (current Alpha4 is pretty stable [...]
Hi Honza,
Can you provide an estimate for the Corosync 3 release timeline? We
have to plan the ABI transition in Debian anf the freeze date is drawing
closer.
Currently I'm pretty happy with current
Jan Friesse writes:
> try corosync 3.x (current Alpha4 is pretty stable [...]
Hi Honza,
Can you provide an estimate for the Corosync 3 release timeline? We
have to plan the ABI transition in Debian anf the freeze date is drawing
closer.
--
Thanks,
Feri
22 matches
Mail list logo
