[Aoetools-discuss] Persisting vblade exports

[Christoph B. <sou...@ma...>]

Hello,

for all the years I've been wondering how people persist their vblade
instances, i.e. have some exports that are automatically started at
bootup. Some hand-crafted shell scripts that call vbladed?

In the Debian project, there is a vblade-persist package which uses
runit, and the maintainer/upstream (Cc:'d) has expressed his
consideration of either giving it into other hands for major rework, or
just removing (RM) it entirely.[1]

Now I am thinking about going the rework way: Create a simple
configuration file format[2] for persistent vblade exports, and add
support for at least systemd (via generators) and sysv (probably using
the daemon[3] program as a supervisor).

Before re-inventing the wheel: Did I miss anything similar out there?
Is this something for the vblade package? I could do this within
Debian, but avoiding distribution-specific extensions was a plus.

    Christoph

[1] https://bugs.debian.org/862873

[2] Basically a POSIX shell fragment key/value store for
    netif, shelf, slot, source, opts, mac, and ionice.

[3] http://www.libslack.org/daemon/
--