On Oct 20, 2016 12:40 AM, "Andy Mender" wrote:
>
> Dear colleagues,
>
> I verified my svlogd logging problems on Debian/Devuan and it turned out
> that the error
> I was getting was non-specific and did not really interfere with either
> daemon supervision
> by runsv or
Dear colleagues,
I verified my svlogd logging problems on Debian/Devuan and it turned out
that the error
I was getting was non-specific and did not really interfere with either
daemon supervision
by runsv or generating logs via svlogd. Also, the error appears on my
Gentoo boxen alike.
Below, an
Thank you for the links and the svlogd script. Great help indeed :).
Best regards,
Andy
On 16 Oct 2016 22:19, "Avery Payne" wrote:
I hate using webmail. It always eats your formatting.
The script shows up as a block of text in the mailing list because of this;
just
I hate using webmail. It always eats your formatting.
The script shows up as a block of text in the mailing list because of this;
just click the link for the project and look for the run-svlogd script.
You'll find what you need there.
On Sun, Oct 16, 2016 at 1:16 PM, Avery Payne
On Sat, Oct 15, 2016 at 3:28 PM, Andy Mender
wrote:
> Hello everyone,
>
> I managed to solve some of my problems. It turned out that my terminal was
> being spammed
> with erroneous output, because I didn't add the "exec 2&>1" redirection to
> my ./run files.
>
This
On Tue, Oct 11, 2016 at 3:09 PM, Andy Mender
wrote:
> Hello again,
>
> I'm rewriting some of the standard sysvinit and openrc scripts to ./run
> scripts
>
I would look around a bit. There are little pockets of pre-written scripts
out there, you just need to dig them
On Thu, 13 Oct 2016 12:16:52 +0200
Andy Mender wrote:
> I was recently trying to convert my OpenRC-based Gentoo installation
> into one based on runit. However, I noticed that it's quite easy to
> send runsvdir or runsvchdir into an infinite loop when there is
>
I was recently trying to convert my OpenRC-based Gentoo installation into
one based on runit. However, I noticed that it's quite easy to send runsvdir
or runsvchdir into an infinite loop when there is something wrong with a
service directory or the runlevel dir selected through runsvchdir is
On Oct 11, 2016 4:07 PM, "Steve Litt" wrote:
>
> On Wed, 12 Oct 2016 00:09:02 +0200
> Andy Mender wrote:
>
> > Hello again,
> >
> > I'm rewriting some of the standard sysvinit and openrc scripts
> > to ./run scripts
> > and I have some
On Oct 11, 2016 3:09 PM, "Andy Mender" wrote:
>
> Hello again,
>
> I'm rewriting some of the standard sysvinit and openrc scripts to ./run
> scripts
> and I have some problems with dbus. I took the ./run script from Void
Linux
> as the original runit documentation
Hello again,
I'm rewriting some of the standard sysvinit and openrc scripts to ./run
scripts
and I have some problems with dbus. I took the ./run script from Void Linux
as the original runit documentation doesn't have an exemplary dbus script.
Whenever I check the status of dbus via "sv status
Correct, cgroups can be used from any process supervision system.
As for socket activation, this too can be implemented on top of a
traditional supervision system, with no need for it to be baked into the
core. See http://smarden.org/ipsvd/ for an example implementation. Granted,
this one doesn't
>> 2. If several services rely on a common daemon, like dbus or
udev/eudev, is
>> the said daemon launched multiple times?
No. One service directory = one daemon instance. If you have a service
directory for dbus-daemon, it will be launched once, no matter how many
times you "sv up" that
Hello,
I am a "journeyman" UNIX user, currently trying to implement runit
as a substitute for systemd on a number of GNU/Linux distributions.
I already have the ./run service scripts per the original documentation for
runit (http://smarden.org/runit/).
However, I don't fully understand how
14 matches
Mail list logo