all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 33362@debbugs.gnu.org
Subject: bug#33362: System tests stuck in "shepherd[1]: waiting for udevd..."
Date: Fri, 30 Nov 2018 00:19:08 +0100	[thread overview]
Message-ID: <20181130001908.45041457@scratchpost.org> (raw)
In-Reply-To: <87woovpk2v.fsf@netris.org>

[-- Attachment #1: Type: text/plain, Size: 1494 bytes --]

Hmm, I wonder whether it might make sense to add "--debug" to udevd in gnu/services/base.scm in order to track down this problem.

The loop looks rather harmless and only checks whether the actual udev socket is available - which it must be for udevd to work.

It does the following right now:

         (start #~(lambda ()
                    (define udevd
                      ;; 'udevd' from eudev.
                      #$(file-append udev "/sbin/udevd")) ; TODO: Add ' "--debug"' here

                    (define (wait-for-udevd)
                      ;; Wait until someone's listening on udevd's control
                      ;; socket.
                      (let ((sock (socket AF_UNIX SOCK_SEQPACKET 0)))
                        (let try ()
                          (catch 'system-error
                            (lambda ()
                              (connect sock PF_UNIX "/run/udev/control")
                              (close-port sock))
                            (lambda args
                              (format #t "waiting for udevd...~%")
                              (usleep 500000)
                              (try))))))
[...]
                    (let ((pid (fork+exec-command (list udevd))))
                      ;; Wait until udevd is up and running.  This appears to
                      ;; be needed so that the events triggered below are
                      ;; actually handled.
                      (wait-for-udevd)



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-11-29 23:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13  1:09 bug#33362: System tests stuck in "shepherd[1]: waiting for udevd..." Mark H Weaver
2018-11-13 20:51 ` Mark H Weaver
2018-11-29 22:58   ` Mark H Weaver
2018-11-29 23:19     ` Danny Milosavljevic [this message]
2018-12-09  8:33     ` Mark H Weaver
2018-12-14 23:52   ` Mark H Weaver
2018-11-20 16:02 ` Ludovic Courtès
2018-12-09 21:46 ` Mark H Weaver
2021-11-26  1:34 ` zimoun
2021-11-26 23:21   ` Mark H Weaver
2022-01-04 23:21     ` zimoun
2022-02-03  2:37       ` zimoun

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=20181130001908.45041457@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=33362@debbugs.gnu.org \
    --cc=mhw@netris.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.