From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org, Csepp <raingloom@riseup.net>,
Andy Tai <atai@atai.org>
Subject: Re: guix on foreign distribution: /var/log/guix/* removal safe?
Date: Tue, 05 Sep 2023 07:04:29 +0200 [thread overview]
Message-ID: <BFC3482A-FB1C-4AE4-B9D0-E07FBC396755@lepiller.eu> (raw)
In-Reply-To: <87a5u1sdad.fsf@riseup.net>
Le 5 septembre 2023 01:56:08 GMT+02:00, Csepp <raingloom@riseup.net> a écrit :
>
>Andy Tai <atai@atai.org> writes:
>
>> I run Guix on top of a foreign distribution (Fedora). The directory
>> /var/log/guix contains log files and keeps growing in size. I wonder
>> if I can remove existing log files in /var/log/guix without any
>> harmful effect (with no guix pull or build in progress)?
>>
>> Thanks for info
>
>AFAIK yes. I've done so a few times.
>
Yes, it's perfectly safe. You could setup a rotation job so you don't have to care about cleaning them manually. See your distro's documentation to learn how to do that ;)
prev parent reply other threads:[~2023-09-05 5:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 23:28 guix on foreign distribution: /var/log/guix/* removal safe? Andy Tai
2023-09-04 23:56 ` Csepp
2023-09-05 5:04 ` Julien Lepiller [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
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=BFC3482A-FB1C-4AE4-B9D0-E07FBC396755@lepiller.eu \
--to=julien@lepiller.eu \
--cc=atai@atai.org \
--cc=help-guix@gnu.org \
--cc=raingloom@riseup.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).