unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Fredrik Salomonsson <plattfot@posteo.net>
To: Hartmut Goebel <hartmut@goebel-consult.de>,
	help-guix <help-guix@gnu.org>
Subject: Re: Logging and guix-home
Date: Sat, 20 Nov 2021 21:13:59 +0000	[thread overview]
Message-ID: <871r3a8r8o.fsf@posteo.net> (raw)
In-Reply-To: <0e2120a3-3d19-1d53-d329-8b6c6d82e31a@goebel-consult.de>


Hi,

Sorry for the radio silence, it's been a busy week.

Hartmut Goebel <hartmut@goebel-consult.de> writes:

> Does setting #:log:file to /dev/stdout work for you? ((Just an idea, 
> I've not tested it)

Yes, it has the same behavior as not using #:log:file. And that is to
output everything to the first tty I log into. Which is the behavior I
would like to avoid, it makes the logging ephemeral and also hard to
read. As I have it to automatically spawn sway if I login on tty1.

Right now logging to a file kind of works, as I don't have many user
daemons running (only ssh-agent). And ssh-agent does not output that
much. One downside I don't have any timestamps in the log file or
anything like that. 

Gnupg was hard to convert as my foreign distro needs it and it ships
with systemd socket files which are enable by default. And I'm too lazy
to disable those in case I break something on my foreign distro.

So I've put the logging on the backburner. And I'll revisit it once I
have moved all my dotfiles over to guix home.

-- 
s/Fred[re]+i[ck]+/Fredrik/g


      reply	other threads:[~2021-11-20 21:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-13  1:45 Logging and guix-home Fredrik Salomonsson
2021-11-14 10:55 ` Hartmut Goebel
2021-11-20 21:13   ` Fredrik Salomonsson [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=871r3a8r8o.fsf@posteo.net \
    --to=plattfot@posteo.net \
    --cc=hartmut@goebel-consult.de \
    --cc=help-guix@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.
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).