Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1129789

Bug#1023557: rygel: consider After=network.target in rygel.service for lingering

From "Barak A. Pearlmutter" <barak@pearlmutter.net>
Newsgroups linux.debian.bugs.dist
Subject Bug#1023557: rygel: consider After=network.target in rygel.service for lingering
Date 2022-12-21 15:30 +0100
Message-ID <FF8gx-cckn-1@gated-at.bofh.it> (permalink)
References <FF7ua-cbNV-7@gated-at.bofh.it> <FF7ua-cbNV-5@gated-at.bofh.it> <FF8gx-cckn-3@gated-at.bofh.it> <FoRjH-1PVs-1@gated-at.bofh.it> <FF8gx-cckn-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Cool!

I had assumed, from the log messages etc, that this was likely a race
condition between the network configuration changing and rygel being
notified of, and adjusting to, said configuration.

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#1023557: rygel: consider After=network.target in rygel.service for lingering "Barak A. Pearlmutter" <bap@debian.org> - 2022-11-06 18:10 +0100
  Bug#1023557: rygel: consider After=network.target in rygel.service for lingering Jens Georg <jens.georg@jensge.org> - 2022-11-07 12:40 +0100
  Bug#1023557: rygel: consider After=network.target in rygel.service for lingering "Barak A. Pearlmutter" <barak@pearlmutter.net> - 2022-12-21 14:40 +0100
    Bug#1023557: rygel: consider After=network.target in rygel.service for lingering Jens Georg <listen@jensgeorg.de> - 2022-12-21 15:10 +0100
  Bug#1023557: rygel: consider After=network.target in rygel.service for lingering "Barak A. Pearlmutter" <barak@pearlmutter.net> - 2022-12-21 15:30 +0100
    Bug#1023557: rygel: consider After=network.target in rygel.service for lingering "Barak A. Pearlmutter" <barak@pearlmutter.net> - 2023-01-01 22:40 +0100

csiph-web