Hi Reco,
On 02/14/18 14:55, Reco wrote:
True. There's one tiny bit though - try
pidof -o %PPID -x /usr/sbin/sshd
and watch it output several pids as well.
Yes, indeed. If pidofproc would rely upon the pidfile only, then
there is no reason to call pidof.
And you don't have to spawn yet
Hi.
On Wed, Feb 14, 2018 at 02:33:16PM +0100, Harald Dunkel wrote:
> Hi Reco,
>
> wrt "pgrep --ns 1 -f /usr/sbin/sshd":
>
> The executable path simply doesn't tell if this is the right service
> to stop. If I run 2 services in parallel (e.g. for different network
> interfaces), then
Hi Reco,
wrt "pgrep --ns 1 -f /usr/sbin/sshd":
The executable path simply doesn't tell if this is the right service
to stop. If I run 2 services in parallel (e.g. for different network
interfaces), then this approach is already broken. Sample:
# pgrep --ns 1 -f /usr/sbin/sshd
12602
# ps -ef |
Hi.
On Mon, Feb 05, 2018 at 04:04:37PM +0100, Harald Dunkel wrote:
> Hi Reco,
>
> you mean this is a known issue???
Well, it's known to me (since then) at least as I merely read the
contents of /lib/lsb/init-functions in my Debian system.
Pinpointing the problem is easy, anyone who has
Hi Reco,
you mean this is a known issue???
Harri
Hi.
On Fri, Feb 02, 2018 at 11:35:04AM +0100, Harald Dunkel wrote:
> Hi folks,
>
> I see a weird effect of pidofproc (defined in /lib/lsb/init-functions):
> If there is no local daemon with a given search path running, then it
> returns the PIDs the daemons running in the LXC containers.
6 matches
Mail list logo
