Hi,

On Fri, 17 Oct 2025 23:16:23 +0100
Andrew Bower <[email protected]> wrote:

>
> > ok I'm going to try this, but I have few questions:
> > 
> > * why map scope= to a number, if I can filter for the word? do we
> > need to filter for something within each scope (and it can be done
> > with the numeric mapping)?
> 
> The reason was that I was thinking the scope runs theoretically
> between 0 and 255 and although most aren't used now in any situations
> I am aware of, they could be, and we should be agnostic to this, so
> you'd say you need something of at least a certain scope, which works
> better with a number. It's probably excessive.

ok

> 
> It might be worth us trying out an example implementation and seeing
> if it looks sensible or silly.

will try something this weekend

> 
> > * what to do if scope= and or family= are not passed to the command?
> >   just fail or have some default for both?
> 
> No family would mean any family; missing scope I'm not sure, I think
> possibly >=link-local or >=global.
> 
> I'm not particularly wedded to those arguments, by the way, I just
> came up with it as an example of the sort of thing we could have.
> 
> > * what if ip (and or ifconfig) are not found in the system? is it
> > safe to assume that network is not configured and fail in this case?
> 
> That's a good question. Needs further thought. Might be worth noting
> we're probably doing more than the initscripts would here - they would
> just wait until networkmanager/dhclient/networking or whatever
> services have been started and possibly failed. So maybe we're over
> thinking this and actually need to wait on default-network instead
> which can launch those like default-rsyslog does. But I think it
> would be ugly to have a service launch another service to do this -
> is there a way of having an alias for whichever network setup service
> is configured

default-syslog is a first attempt, and I'm not happy about it.
I don't find attractive to play with symlinks and alternatives either..

Recently I was thinking:
* define a facility "suffix" in runit; for example '-log' for sysloggers
  (could be '-net' for network)
* rename all services that belong to the group appending the common
  '-log' suffix to the end of the service name. For example rsyslog-log,
  socklog-unix-log and so on
* in run files of services that require one service of the '-log' group
  check the service with full path and wildcards, for example
  'sv check /etc/service/*-log'
but I still have to test if it works as expected..

Lorenzo






  

Reply via email to