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

Bug#1121617: runit: default-syslog not ready for incoming metalog package

From	Andrew Bower <andrew@bower.uk>
Newsgroups	linux.debian.bugs.dist
Subject	Bug#1121617: runit: default-syslog not ready for incoming metalog package
Date	2026-01-31 20:30 +0100
Message-ID	<MjoPo-eLDY-5@gated-at.bofh.it> (permalink)
References	(2 earlier) <LY11n-8yC-3@gated-at.bofh.it> <LWtEt-gDRl-1@gated-at.bofh.it> <MjocF-eL7A-1@gated-at.bofh.it> <LWtEt-gDRl-1@gated-at.bofh.it> <MjocF-eL7A-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

I forgot the 'verb' in this example - adding now to avoid
any confusion:

On Sat, Jan 31, 2026 at 06:43:37PM +0000, Andrew Bower wrote:
> > ===> /usr/sbin/facility <===
> > 
> > #!/usr/bin/perl -w
> > 
> > use strict;
> > use File::Basename;
> > use File::Glob qw(bsd_glob);
> > 
> > my $svdir = $ENV{SVDIR} // "/etc/service";
> > my $command = shift or die "usage: $0 command facility...";
> > my %providers = map {
> >   map {
> >     basename(dirname($_)) => 1
> >   } bsd_glob("$svdir/*/provides-$_")
> > } @ARGV;
> > 
> > exec ("sv", $command, keys %providers) if %providers;
> 
> I think for 'facility check' one might need to be able to define whether
> we want an AND or OR relationship - the default 'sv' behaviour would be
> to AND them together, whereas for some types of facility we may be
> content with any one passing, so we could have something like:
> 
>   facility --any network

  facility --any check network
 
> which would then have to explode into one 'sv' invocation for each
> discovered provider and then OR the results together.

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

Thread

Bug#1121617: runit: default-syslog not ready for incoming metalog package Andrew Bower <andrew@bower.uk> - 2025-11-29 15:00 +0100
  Bug#1121617: runit: default-syslog not ready for incoming metalog package Lorenzo <plorenzo@disroot.org> - 2025-12-03 12:40 +0100
    Bug#1121617: runit: default-syslog not ready for incoming metalog package Andrew Bower <andrew@bower.uk> - 2025-12-03 20:50 +0100
      Bug#1121617: runit: default-syslog not ready for incoming metalog package Andrew Bower <andrew@bower.uk> - 2026-01-31 19:50 +0100
        Bug#1121617: runit: default-syslog not ready for incoming metalog package Andrew Bower <andrew@bower.uk> - 2026-01-31 20:30 +0100

csiph-web