Bug#526201: runit: Environment variables in run script

[KAction]

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 better to be proposed to upstream.

Seems there is no much activity about this issue lately, so closing bug.
Should any strong arguments why this feature request shoudl be fulfilled
appear, feel free to reopen bug.

Bug#526201: runit: Environment variables in run script

[Dmitry Bogatov]

[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 for configuration variables:
>
> eg. for atftpd
> exec chpst -e env sh -c atftpd --no-fork --daemon \$OPTIONS
>
> with OPTIONS populated it gets much nicer:
> exec atftpd --no-fork --daemon $OPTIONS

control: tags -1 +moreinfo

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 better to be proposed to upstream.

-- 
X-Web-Site: https://sinsekvu.github.io | Note that I process my email in batch,
Accept-Languages: eo,ru,en | at most once every 24 hours. If matter
Accept: text/plain, text/x-diff| is urgent, you have my phone number.


pgp78TrxyXods.pgp
Description: PGP signature

Bug#526201: runit: Environment variables in run script

[Jameson Rollins]

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 cumbersome, but it gets the job done, and lets one keep
all the relevant variables in a single directory, ie. env.

hth.

jamie.


signature.asc
Description: Digital signature

Bug#526201: runit: Environment variables in run script

[Michael Gebetsroither]

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

with OPTIONS populated it gets much nicer:
exec atftpd --no-fork --daemon $OPTIONS

currently i'm using a directory 'conf' much like env, but with manual
parsing of variables which is also not ideal.

OPTIONS=$(cat conf/OPTIONS)

Or are there any better methods for tasks like this with runit?

michael

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.23-grml64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.iso885915, LC_CTYPE=en_US.iso885915 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

runit depends on no packages.

Versions of packages runit recommends:
ii  fgetty0.6-4  very small, efficient, console-onl

Versions of packages runit suggests:
pn  runit-run none (no description available)
pn  socklog-run   none (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org