From: Raghu <raghujindia@gmail.com>
To: Martin Castillo <castilma@uni-bremen.de>
Cc: supervision@list.skarnet.org
Subject: Re: svlogd log rotation
Date: Fri, 13 Dec 2019 10:05:45 -0500 [thread overview]
Message-ID: <CAMhTLK=hNjRgCKZL0TZ-OOT6g-gP-jY1hFJVp2ufNqqUFF-00w@mail.gmail.com> (raw)
In-Reply-To: <4db43fdb-4b78-86b8-eeaa-af22397bd81e@uni-bremen.de>
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
Sorry, please ignore.
On Thu, Dec 12, 2019 at 4:15 PM Martin Castillo <castilma@uni-bremen.de>
wrote:
> Hi,
>
> On 12.12.19 15:25, Raghu wrote:
> > I have redirected the svlogd log file my custom name instead of current
> in
> > my run script as below.
> > touch /testlogs/logs/Y5Consolelog.txt.0
> > exec svlogd -tt /testlogs/logs/ Y5Consolelog.txt.0
>
> I have never heard of this feature and couldn't find anything on the
> manpage. Running these 2 commands gets me
> $ svlogd -tt "$(realpath log)"/ mylog.0
> svlogd: warning: unable to open log directory: mylog.0: file does not exist
>
> and the current file is still called 'current'.
> I have artix' linux runit 2.1.2-15 and svlogd version
> 5e55a90e0a1b35ec47fed3021453c50675ea1117.
>
> What version are you running?
>
> Marti
> >
> > And my config file as below:
> > s10000
> > n2
> >
> > I do see the log file getting updated but it not getting rotated when the
> > size limit is reached. I don't see the old log file with timestamp
> appended
> > to it after rotation which would actually happen to a current file.
> >
> > Can you please let me know if I'm missing anything?
> > Thank you.
> >
>
> --
> GPG: 7FDE 7190 2F73 2C50 236E 403D CC13 48F1 E644 08EC
>
--
Thanks
Raghu
SAVE TREES..GO GREEN
prev parent reply other threads:[~2019-12-13 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 14:25 Raghu
[not found] ` <4db43fdb-4b78-86b8-eeaa-af22397bd81e@uni-bremen.de>
2019-12-13 15:05 ` Raghu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMhTLK=hNjRgCKZL0TZ-OOT6g-gP-jY1hFJVp2ufNqqUFF-00w@mail.gmail.com' \
--to=raghujindia@gmail.com \
--cc=castilma@uni-bremen.de \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).