From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Guix Devel <guix-devel@gnu.org>
Subject: Guix services, logging, and log rotation
Date: Tue, 16 Nov 2021 22:52:06 -0600 [thread overview]
Message-ID: <87bl2jwfih.fsf@gmail.com> (raw)
Hey Guix!
I'm slowly working on contributing rsyslog with a Guix service. I have just arrived at trying to allow the user to specify where the Shepherd service sends its log file, and I began thinking about log rotation.
In the manual, SS10.8.3, it says:
> (usually, services that produce log files already take care of that)
I found an excellent example in =hpcguix-web-service-type=. It looks like you can achieve this by extending the =rottlog-service-type=?
#+BEGIN_SRC scheme
(define hpcguix-web-service-type
(service-type
(name 'hpcguix-web)
(description "Run the hpcguix-web server.")
(extensions
(list (service-extension account-service-type
(const %hpcguix-web-accounts))
(service-extension activation-service-type
(const %hpcguix-web-activation))
(service-extension rottlog-service-type
(const %hpcguix-web-log-rotations))
(service-extension shepherd-root-service-type
(compose list hpcguix-web-shepherd-service))))))
#+END_SRC
However, I noticed not all services allow users to specify where log files go, or setup log rotation. E.g.:
#+BEGIN_SRC scheme
(define syncthing-service-type
(service-type (name 'syncthing)
(extensions (list (service-extension shepherd-root-service-type
syncthing-shepherd-service)))
(description
"Run @uref{https://github.com/syncthing/syncthing, Syncthing}
decentralized continuous file system synchronization.")))
#+END_SRC
Are these bugs?
Why don't all services allow you to specify where logs go?
I guess if no log location is specified, it just goes in the master shepherd log which is rotated?
Thank you,
--
Katherine
next reply other threads:[~2021-11-17 4:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 4:52 Katherine Cox-Buday [this message]
2021-11-17 11:40 ` Guix services, logging, and log rotation Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bl2jwfih.fsf@gmail.com \
--to=cox.katherine.e@gmail.com \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).