On Wed, Oct 04, 2017 at 05:02:27PM +0200, Kees Bos wrote:
> On wo, 2017-10-04 at 09:35 -0500, Serge E. Hallyn wrote:
> > Quoting Kees Bos (cornelis@gmail.com):
> > >
> > > I'm not using it, but do expect the extra args:
> > >
> > > while [ {{ '${#@}' }} -gt 3 ] ; do
> > > ...
> > > shif
On wo, 2017-10-04 at 09:35 -0500, Serge E. Hallyn wrote:
> Quoting Kees Bos (cornelis@gmail.com):
> >
> > I'm not using it, but do expect the extra args:
> >
> > while [ {{ '${#@}' }} -gt 3 ] ; do
> > ...
> > shift
> > done
> >
> > It might be that some users will need the last extra a
Quoting Kees Bos (cornelis@gmail.com):
> I'm not using it, but do expect the extra args:
>
> while [ {{ '${#@}' }} -gt 3 ] ; do
> ...
> shift
> done
>
> It might be that some users will need the last extra argument (stage:
> pre-start|start|post-stop). This is currently not available in
I'm not using it, but do expect the extra args:
while [ {{ '${#@}' }} -gt 3 ] ; do
...
shift
done
It might be that some users will need the last extra argument (stage:
pre-start|start|post-stop). This is currently not available in the
environment.
I can live without these extra arguments,
Quoting Andrey Repin (anrdae...@yandex.ru):
> Greetings, Serge Hallyn!
>
> > Since the start, lxc container startup hooks have gotten some redundant
> > information as command line arguments, which is also available as
> > environment variables.
>
> > Is anyone making use of that? I'm wondering
Greetings, Serge Hallyn!
> Since the start, lxc container startup hooks have gotten some redundant
> information as command line arguments, which is also available as environment
> variables.
> Is anyone making use of that? I'm wondering whether any existing
> installations would have broken scr
Hi everyone,
Since the start, lxc container startup hooks have gotten some redundant
information as command line arguments, which is also available as environment
variables.
Is anyone making use of that? I'm wondering whether any existing installations
would have broken scripts if we get rid
