Your initial use case explanation was the reason I made this change. See we do
listen to our users, thanks :-)
-Original Message-
From: "nusenu"
Sent: â7/â21/â2015 23:19
To: "misc@openbsd.org"
Cc: "Antoine Jacoutot"
Subject: Re: bug in rc.subr: ki
>>> imagine you have N services named:
>>>
>>> service service1 service2 ...
>>>
>>> or a ab abc ...
>>>
>>> Now you want to stop 'service' and you run: 'rcctl stop
>>> service'
>>>
>>> all (not just one) of them are gone?
>>>
>>>
>>> rc.subr invokes pkill and does a "startswith" match but does
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>>> If you want to match the exact complete command line, adapt
>>> pexp
> accordingly and end it with '$'.
>>>
>>> Can $pexp be set via /etc/rc.conf.local?
> No, you need to edit the rc script for that.
After thinking about creating a custom r
On Sat, Jun 20, 2015 at 10:02:18PM +0200, nusenu wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> >>> Some daemons will happend more stuffs to the command line than
> >>> just
> > $daemon $daemon_flags
> >>>
> >>> Then $pexp should include everything that a daemon can append
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>>> Some daemons will happend more stuffs to the command line than
>>> just
> $daemon $daemon_flags
>>>
>>> Then $pexp should include everything that a daemon can append
>>> via rc.conf.local settings?
> No.
Would you mind elaborating on that?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> What do you think about this patch to require a perfect
> match
> when sending invoking pkill/pgrep?
>
> Won't work. Carefully read pgrep(1) again.
>>>
>>> After reading the man page again I even found something more
>>> f
On Sat, Jun 20, 2015 at 09:44:14PM +0200, nusenu wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> > What do you think about this patch to require a perfect
> > match
> > when sending invoking pkill/pgrep?
> >
> > Won't work. Carefully read pgrep(1) again.
> >
On Sat, Jun 20, 2015 at 03:33:20PM +0200, nusenu wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> >>> imagine you have N services named:
> >>>
> >>> service service1 service2 ...
> >>>
> >>> Now you want to stop 'service' and you run: 'rcctl stop
> >>> service'
> >>>
> >>> all (no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>>> imagine you have N services named:
>>>
>>> service service1 service2 ...
>>>
>>> Now you want to stop 'service' and you run: 'rcctl stop
>>> service'
>>>
>>> all (not just one) of them are gone?
>>>
>>>
>>> rc.subr invokes pkill and does a "
On Tue, Jun 16, 2015 at 10:30:40PM +0200, Antoine Jacoutot wrote:
> On Tue, Jun 16, 2015 at 07:38:28PM +, nusenu wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > Hi,
> >
> > imagine you have N services named:
> >
> > service
> > service1
> > service2
> > ...
> >
> > or
On Tue, Jun 16, 2015 at 07:38:28PM +, nusenu wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi,
>
> imagine you have N services named:
>
> service
> service1
> service2
> ...
>
> or
> a
> ab
> abc
> ...
>
> Now you want to stop 'service' and you run:
> 'rcctl stop service'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
imagine you have N services named:
service
service1
service2
...
or
a
ab
abc
...
Now you want to stop 'service' and you run:
'rcctl stop service'
all (not just one) of them are gone?
rc.subr invokes pkill and does a "startswith" match but
12 matches
Mail list logo
