From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sys-process/psmisc 23.2 broke
Date: Sun, 26 Aug 2018 21:12:44 +0100 [thread overview]
Message-ID: <20180826211244.2d1e9241@digimed.co.uk> (raw)
In-Reply-To: <m3d0u5nia5.wl-covici@ccs.covici.com>
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
On Sun, 26 Aug 2018 13:34:42 -0400, John Covici wrote:
> Hi. 23.2 is broke and has a mandatory new format where you have to
> put -s before the signal when using killall. Killall is not finding
> existing process even though I have the name correct. Downgrading to
> 23.1-r1 fixes the problem. I just thought I'd let people know.
The -s does not appear to be mandatory here, it still sends SIGTERM by
default. However, I have got a 'no process found' error with some
processes, which now require killall `which processname` to work.
--
Neil Bothwick
Help a man when he is in trouble and he will remember you when he is in
trouble again
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-08-26 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 17:34 [gentoo-user] sys-process/psmisc 23.2 broke John Covici
2018-08-26 20:12 ` Neil Bothwick [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180826211244.2d1e9241@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox