Module Name:src
Committed By: roy
Date: Mon Oct 7 06:14:05 UTC 2024
Modified Files:
src/usr.bin/pkill: pkill.1 pkill.c
Log Message:
pkill(1): Add -F option to use a pidfile and -L to ensure it's locked
Taken from FreeBSD
To generate a diff of this commit:
cvs rdiff -u
Module Name:src
Committed By: roy
Date: Mon Oct 7 06:14:05 UTC 2024
Modified Files:
src/usr.bin/pkill: pkill.1 pkill.c
Log Message:
pkill(1): Add -F option to use a pidfile and -L to ensure it's locked
Taken from FreeBSD
To generate a diff of this commit:
cvs rdiff -u
Module Name:src
Committed By: simonb
Date: Sat Oct 29 08:17:16 UTC 2022
Modified Files:
src/usr.bin/pkill: pkill.1 pkill.c
Log Message:
Add a -q option for pgrep to not print anything; similar to grep -q.
To generate a diff of this commit:
cvs rdiff -u -r1.31 -r1.32 src/
Module Name:src
Committed By: simonb
Date: Sat Oct 29 08:17:16 UTC 2022
Modified Files:
src/usr.bin/pkill: pkill.1 pkill.c
Log Message:
Add a -q option for pgrep to not print anything; similar to grep -q.
To generate a diff of this commit:
cvs rdiff -u -r1.31 -r1.32 src/
Module Name:src
Committed By: ad
Date: Sat Jul 2 20:50:26 UTC 2022
Modified Files:
src/usr.bin/pkill: pkill.c
Log Message:
Cosmetic tweak. No functional change.
To generate a diff of this commit:
cvs rdiff -u -r1.31 -r1.32 src/usr.bin/pkill/pkill.c
Please note that di
Module Name:src
Committed By: ad
Date: Sat Jul 2 20:50:26 UTC 2022
Modified Files:
src/usr.bin/pkill: pkill.c
Log Message:
Cosmetic tweak. No functional change.
To generate a diff of this commit:
cvs rdiff -u -r1.31 -r1.32 src/usr.bin/pkill/pkill.c
Please note that di
In article <20404.1353628...@splode.eterna.com.au>,
matthew green wrote:
>
>> | this seems like a fairly big semantic change to me.
>> |
>> | could you change it to take a new option to look in argv[0] instead
>> | of p_comm? p_comm is not changeable by the user.
>>
>> You could already do thi
> | this seems like a fairly big semantic change to me.
> |
> | could you change it to take a new option to look in argv[0] instead
> | of p_comm? p_comm is not changeable by the user.
>
> You could already do this with -f. The point was to make the default case
> behave intuitively. Adding an
On Nov 21, 1:36pm, i...@bsdimp.com (Warner Losh) wrote:
-- Subject: Re: CVS commit: src/usr.bin/pkill
| How could you guarantee this short of moving this into the kernel so you =
| could do all the comparisons while keeping all forks from happening?
You could not; this was more tongue-in-cheek
On Nov 21, 2012, at 1:55 PM, David Laight wrote:
> On Wed, Nov 21, 2012 at 01:36:01PM -0700, Warner Losh wrote:
Is pkill() guaranteed to do an atomic traversal of the process list?
So it will kill something that keeps using fork() to change its pid.
>>>
>>> I don't think our libkvm off
On Wed, Nov 21, 2012 at 01:36:01PM -0700, Warner Losh wrote:
> >> Is pkill() guaranteed to do an atomic traversal of the process list?
> >> So it will kill something that keeps using fork() to change its pid.
> >
> > I don't think our libkvm offers that.
>
> How could you guarantee this short of
;>> -- Subject: re: CVS commit: src/usr.bin/pkill
>>>
>>> | this seems like a fairly big semantic change to me.
>>> |
>>> | could you change it to take a new option to look in argv[0] instead
>>> | of p_comm? p_comm is not changeable by the us
In article <20121121200309.gn...@snowdrop.l8s.co.uk>,
David Laight wrote:
>On Wed, Nov 21, 2012 at 12:43:20PM -0500, Christos Zoulas wrote:
>> On Nov 22, 4:39am, m...@eterna.com.au (matthew green) wrote:
>> -- Subject: re: CVS commit: src/usr.bin/pkill
>>
>&g
On Wed, Nov 21, 2012 at 12:43:20PM -0500, Christos Zoulas wrote:
> On Nov 22, 4:39am, m...@eterna.com.au (matthew green) wrote:
> -- Subject: re: CVS commit: src/usr.bin/pkill
>
> | this seems like a fairly big semantic change to me.
> |
> | could you change it to take a new
On Nov 22, 4:39am, m...@eterna.com.au (matthew green) wrote:
-- Subject: re: CVS commit: src/usr.bin/pkill
| this seems like a fairly big semantic change to me.
|
| could you change it to take a new option to look in argv[0] instead
| of p_comm? p_comm is not changeable by the user.
You could
> In article <20121121080326.gl...@snowdrop.l8s.co.uk>,
> David Laight wrote:
> >On Tue, Nov 20, 2012 at 05:52:02PM -0500, Christos Zoulas wrote:
> >> Module Name: src
> >> Committed By: christos
> >> Date: Tue Nov 20 22:52:02 UTC 2012
> >>
> >> Modified Files:
> >>s
In article <20121121080326.gl...@snowdrop.l8s.co.uk>,
David Laight wrote:
>On Tue, Nov 20, 2012 at 05:52:02PM -0500, Christos Zoulas wrote:
>> Module Name: src
>> Committed By:christos
>> Date:Tue Nov 20 22:52:02 UTC 2012
>>
>> Modified Files:
>> src/usr.bin/pkill: p
On Tue, Nov 20, 2012 at 05:52:02PM -0500, Christos Zoulas wrote:
> Module Name: src
> Committed By: christos
> Date: Tue Nov 20 22:52:02 UTC 2012
>
> Modified Files:
> src/usr.bin/pkill: pkill.c
>
> Log Message:
> Don't use p_comm since it is only 16 characters long and you can fin
> cvs rdiff -u -r1.25 -r1.26 src/usr.bin/pkill/pkill.c
Looks like -l option is necessary for prenice also.
enami.
19 matches
Mail list logo