control: tag -1 +wontfix
control: close -1
[2017-01-06 11:38] Dmitry Bogatov
> What is wrong with
>
> $ cd /etc/service/foo
> $ echo 'OPTIONS=-bar > conf
> $ cat run
> #!/bin/sh
> . conf
> [...]
>
> I dislike idea to complicate runit itself, but it is not in my
> competence. Such change is be
[2009-04-29 22:38] Michael Gebetsroither
>
> part text/plain1289
> Package: runit
> Version: 2.0.0-1
> Severity: wishlist
>
> Hi,
>
> would it be possibel to include environment variables parsing within run
> script itself, like chpst -e?
>
> It's rather ugly to use chpst fo
Hi, Michael. The way I usually handle this issue is similar to your
suggestion, but instead I just keep the variables in the env/
directory and then retrieve them from there. For instance:
OPTIONS=$(head -1 env/OPTIONS)
exec chpst -e env atftpd --no-fork --daemon $OPTIONS
It's a little cumberso
Package: runit
Version: 2.0.0-1
Severity: wishlist
Hi,
would it be possibel to include environment variables parsing within run
script itself, like chpst -e?
It's rather ugly to use chpst for configuration variables:
eg. for atftpd
exec chpst -e env sh -c atftpd --no-fork --daemon \$OPTIONS
wi
4 matches
Mail list logo
