Please add a way to send signals to running commands.
For example when you do ping www.google.com there's no way to terminate it. Only killall ping.
Thanks.
Hi.
Please add a way to send signals to running commands.
For example when you do ping www.google.com there's no way to terminate it. Only killall ping.
Thanks.
<!-- github-sync-id:1813539 -->
Please add a way to send signals to running commands.
For example when you do ping www.google.com there's no way to terminate it. Only killall ping.
Thanks.
What's wrong with doing "ps ux" and then "kill 12345"?
We can't even handle Ctrl-C due to how does IRC work...
On 04.10.2011 20:33, Daniel Fort wrote:
> Hi.
>
> Please add a way to send signals to running commands.
> For example when you do ping www.google.com there's no way to terminate it. Only killall ping.
>
> Thanks.
>
> What's wrong with doing "ps ux" and then "kill 12345"?
> We can't even handle Ctrl-C due to how does IRC work...
<!-- github-comment-id:2286250 -->
If ZNC started the process, it can signal it, surely?
Presumably, if you started a process via ZNC's shell module, you did so because you didn't want to SSH to the box in question and use a real shell; so being able to signal the processes you created does sound reasonably sane.
(Personally, I don't use the shell module, but thought I'd add my feedback)
If ZNC started the process, it can signal it, surely?
Presumably, if you started a process via ZNC's shell module, you did so because you didn't want to SSH to the box in question and use a real shell; so being able to signal the processes you created does sound reasonably sane.
(Personally, I don't use the shell module, but thought I'd add my feedback)
<!-- github-comment-id:2286795 -->
If ZNC started the process, it can signal it, surely?
Sure, any your process (including ZNC) can signal any your process
(including the one which shell module started).
Presumably, if you started a process via ZNC's shell module, you did so because you didn't want to SSH to the box in question and use a real shell; so being able to signal the processes you created does sound reasonably sane.
So, what is suggested way to send the signal, and how is it easier than
running pkill through the same shell module?
On 04.10.2011 21:21, David Precious wrote:
> If ZNC started the process, it can signal it, surely?
> Sure, any your process (including ZNC) can signal any your process
> (including the one which shell module started).
> Presumably, if you started a process via ZNC's shell module, you did so because you didn't want to SSH to the box in question and use a real shell; so being able to signal the processes you created does sound reasonably sane.
>
> So, what is suggested way to send the signal, and how is it easier than
> running pkill through the same shell module?
<!-- github-comment-id:2286851 -->
So, what is suggested way to send the signal, and how is it easier than running pkill through the same shell module?
Yeah, true, you could run pkill yourself through the same module easily enough.
I was thinking of a "signal" command which would deliver the requested signal (via kill() ) to the given PID (or, perhaps, by default to the PID of the last command started via the shell module). You're right though, just executing pkill takes care of it.
> So, what is suggested way to send the signal, and how is it easier than running pkill through the same shell module?
Yeah, true, you could run pkill yourself through the same module easily enough.
I was thinking of a "signal" command which would deliver the requested signal (via `kill()` ) to the given PID (or, perhaps, by default to the PID of the last command started via the shell module). You're right though, just executing pkill takes care of it.
<!-- github-comment-id:2286986 -->
I know about ps ux& kill way. Just thought such thing should be more convinient.
The convenient way is to press ^C.
But since IRC client won't send that to server, it's impossible to use
it here.
If to invent a new way to do that, it will be even less convenient than
running kill/pkill, as it would be specific to ZNC shell module.
No another shell has that, as they just use simple ^C
On 05.10.2011 03:23, Daniel Fort wrote:
> I know about ps ux& kill way. Just thought such thing should be more convinient.
>
> The convenient way is to press ^C.
> But since IRC client won't send that to server, it's impossible to use
> it here.
If to invent a new way to do that, it will be even less convenient than
running kill/pkill, as it would be specific to ZNC shell module.
No another shell has that, as they just use simple ^C
<!-- github-comment-id:2293648 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Hi.
Please add a way to send signals to running commands.
For example when you do ping www.google.com there's no way to terminate it. Only killall ping.
Thanks.
On 04.10.2011 20:33, Daniel Fort wrote:
If ZNC started the process, it can signal it, surely?
Presumably, if you started a process via ZNC's shell module, you did so because you didn't want to SSH to the box in question and use a real shell; so being able to signal the processes you created does sound reasonably sane.
(Personally, I don't use the shell module, but thought I'd add my feedback)
On 04.10.2011 21:21, David Precious wrote:
Yeah, true, you could run pkill yourself through the same module easily enough.
I was thinking of a "signal" command which would deliver the requested signal (via
kill()) to the given PID (or, perhaps, by default to the PID of the last command started via the shell module). You're right though, just executing pkill takes care of it.I know about ps ux & kill way. Just thought such thing should be more convinient.
sorry. wrong button :)
On 05.10.2011 03:23, Daniel Fort wrote:
If to invent a new way to do that, it will be even less convenient than
running kill/pkill, as it would be specific to ZNC shell module.
No another shell has that, as they just use simple ^C