unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: phodina via Guix-patches via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "59683@debbugs.gnu.org" <59683@debbugs.gnu.org>,
	Florian <florhizome@posteo.net>
Subject: [bug#59683] [PATCH] gnu: Add bolt
Date: Sun, 25 Dec 2022 17:33:41 +0000	[thread overview]
Message-ID: <uVEz0dhebkLVzAio0eirTxRkVlXMoYxsW2gj60lIKRpZWTNJ1dXHPXRbrhQj9m-hpz4Bb7GK4GrWODTAFQpJSHUh07aUrDR2733P472--dQ=@protonmail.com> (raw)
In-Reply-To: <87wn6fxxlf.fsf@gnu.org>

Hello Ludo’,


> > I've tried to simplify the service.
> > 
> > However, for some reason the client boltctl does not work. It is restarted under different PID and the service does not fail.
> 
> 
> Since it’s a D-Bus service, maybe we do not need to create a Shepherd
> service for boltd? In that case, it will be started on-demand by
> dbus-daemon, for instance the first time someone runs ‘boltctl’.
> 
> Is that acceptable or does it have to be started at boot time?

Not sure about that. I'll ask Christian Kellner (author of the project).
The issue is that user is able to define if the device is allowed to connect or not. And my assumption is that this is the knowledge of the daemon.
So it would have to be started by some udev event that sends dbus-event.
Or maybe the "IDs" of the devices are stored in the Thunderbolt controller (I'm not familar with the specs either) and it's done transparently.
 
> > 
> > $ ls /var/log/bolt*
> > ls: cannot access '/var/log/bolt*': No such file or directory
> 
> 
> Perhaps /var/log/messages has details?

Not sure the content of the '/var/log/messages' is useful:

Dec 25 13:56:48 localhost shepherd[1]: Service bolt has been started.
Dec 25 13:56:48 localhost shepherd[1]: Service nix-daemon has been started.
Dec 25 13:56:48 localhost shepherd[1]: Respawning bolt.
Dec 25 13:56:48 localhost shepherd[1]: Service bolt has been started.
Dec 25 13:56:48 localhost shepherd[1]: Respawning bolt.
Dec 25 13:56:48 localhost shepherd[1]: Service bolt has been started.
Dec 25 13:56:48 localhost shepherd[1]: Respawning bolt.
Dec 25 13:56:48 localhost shepherd[1]: Service bolt has been started.
Dec 25 13:56:48 localhost shepherd[1]: Respawning bolt.
Dec 25 13:56:48 localhost shepherd[1]: Service bolt has been started.
Dec 25 13:56:48 localhost shepherd[1]: Respawning bolt.
Dec 25 13:56:48 localhost shepherd[1]: Service bolt has been started.
Dec 25 13:56:48 localhost shepherd[1]: Respawning bolt.
Dec 25 13:56:48 localhost shepherd[1]: Service bolt has been started.
Dec 25 13:56:48 localhost shepherd[1]: Service bolt has been disabled.
Dec 25 13:56:48 localhost shepherd[1]:   (Respawning too fast.)


----
Petr




  reply	other threads:[~2022-12-25 17:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 15:32 [bug#59683] [PATCH] gnu: Add bolt florhizome
2022-12-13 12:52 ` [bug#59683] Bolt package phodina via Guix-patches via
2022-12-14 11:24   ` [bug#59683] [PATCH] gnu: Add bolt Ludovic Courtès
2022-12-20 17:04     ` Florian
2022-12-20 20:51       ` phodina via Guix-patches via
2022-12-25 16:22         ` Ludovic Courtès
2022-12-25 17:33           ` phodina via Guix-patches via [this message]
2023-01-16 13:36     ` bug#59683: " Maxim Cournoyer

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='uVEz0dhebkLVzAio0eirTxRkVlXMoYxsW2gj60lIKRpZWTNJ1dXHPXRbrhQj9m-hpz4Bb7GK4GrWODTAFQpJSHUh07aUrDR2733P472--dQ=@protonmail.com' \
    --to=guix-patches@gnu.org \
    --cc=59683@debbugs.gnu.org \
    --cc=florhizome@posteo.net \
    --cc=ludo@gnu.org \
    --cc=phodina@protonmail.com \
    /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).