Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.os.linux > #57304
| From | Georges <georges@prout.com> |
|---|---|
| Newsgroups | alt.os.linux |
| Subject | Re: misterious behavior of either kill or terminal |
| Date | 2019-06-28 11:35 +0200 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <qf4n03$8cd$1@gioia.aioe.org> (permalink) |
| References | <qej6cu$61p$1@dont-email.me> <slrnqgq80t.ds3.dan@djph.net> <qen2qn$fmb$2@gonzo.revmaps.no-ip.org> <171huf-87h.ln1@Telcontar.valinor> |
Le 28/06/2019 à 10:54, Carlos E.R. a écrit : > On 23/06/2019 07.31, Jasen Betts wrote: >> On 2019-06-21, Dan Purgert <dan@djph.net> wrote: >>> >>> Soviet_Mario wrote: >>>> >>>> I had launched a very long "dd" proc. un the laptop in a >>>> TERMINAL (500 gb to transfer). >>>> The light of the drive blinked but no sign of progress were >>>> reported on screen >>> >>> This is normal. >>> >>>> [...] >>>> "sudo kill -SIGUSR1 44356" >>>> the 44356 was original Terminal PID containing dd >>> >>> You sent the wrong signal 'SIGUSR1' is (as I recall) 'kill -USR1 <pid>'. >> >> Either form works: "SIG" is optional. >> >>>> [...] >>>> Now I have relaunched the command (hours later), hoping that >>>> would simply OVERWRITE again ... and I won't try to send >>>> signal to the process >>> >>> It'll overwrite, yes. >>> >>>> [...] >>>> but I'd like to understand what would be the right mode to >>>> locate a child nested process in the PID list or how to pass >>>> signal to the container (terminal) in order for it to pass >>>> the signal to its child .... >>> >>> You send the signal to DD, not anything else. >> >> yeah, SIGUSR1 is, by default, fatal; a process must set a handler for >> it, if you send it the wrong way: processes die. > > Why should a process die if sent a signal that it doesn't handle? > SIGUSR1,2 are defined by the application. What they mean is entirely up > to the application, there is no default action. > Hi Carlos, if no handler found, the SIGUSR1 and SIGUSR2 default action is 'term'(inate) the process. http://man7.org/linux/man-pages/man7/signal.7.html ;) -- () /\
Back to alt.os.linux | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
misterious behavior of either kill or terminal Soviet_Mario <SovietMario@CCCP.MIR> - 2019-06-21 20:07 +0200
Re: misterious behavior of either kill or terminal Dan Purgert <dan@djph.net> - 2019-06-21 18:21 +0000
Re: misterious behavior of either kill or terminal marrgol <marrgol@address.invalid> - 2019-06-22 13:27 +0200
Re: misterious behavior of either kill or terminal Jasen Betts <jasen@xnet.co.nz> - 2019-06-23 05:31 +0000
Re: misterious behavior of either kill or terminal "Carlos E.R." <robin_listas@es.invalid> - 2019-06-28 10:54 +0200
Funny... (Was: misterious behavior of either kill or terminal) gazelle@shell.xmission.com (Kenny McCormack) - 2019-06-28 09:15 +0000
Re: misterious behavior of either kill or terminal Georges <georges@prout.com> - 2019-06-28 11:35 +0200
Re: misterious behavior of either kill or terminal "Carlos E.R." <robin_listas@es.invalid> - 2019-06-28 11:50 +0200
Re: misterious behavior of either kill or terminal Georges <georges@prout.com> - 2019-06-28 12:21 +0200
Re: misterious behavior of either kill or terminal Richard Kettlewell <invalid@invalid.invalid> - 2019-06-28 13:26 +0100
Re: misterious behavior of either kill or terminal "Carlos E.R." <robin_listas@es.invalid> - 2019-06-28 14:51 +0200
Re: misterious behavior of either kill or terminal Richard Kettlewell <invalid@invalid.invalid> - 2019-06-28 14:10 +0100
Re: misterious behavior of either kill or terminal "Carlos E.R." <robin_listas@es.invalid> - 2019-06-28 20:06 +0200
Re: misterious behavior of either kill or terminal Georges <georges@prout.com> - 2019-06-28 20:54 +0200
Re: misterious behavior of either kill or terminal owl <owl@rooftop.invalid> - 2019-06-28 14:51 +0000
Re: misterious behavior of either kill or terminal "F. Russell" <frussell@random.info> - 2019-06-28 17:40 +0000
Re: misterious behavior of either kill or terminal Soviet_Mario <SovietMario@CCCP.MIR> - 2019-06-28 16:45 +0200
Re: misterious behavior of either kill or terminal Jasen Betts <jasen@xnet.co.nz> - 2019-06-28 10:29 +0000
Re: misterious behavior of either kill or terminal "Carlos E.R." <robin_listas@es.invalid> - 2019-06-28 14:54 +0200
Re: misterious behavior of either kill or terminal "Carlos E.R." <robin_listas@es.invalid> - 2019-06-21 20:26 +0200
Re: misterious behavior of either kill or terminal Soviet_Mario <SovietMario@CCCP.MIR> - 2019-06-22 00:02 +0200
Re: misterious behavior of either kill or terminal "Carlos E.R." <robin_listas@es.invalid> - 2019-06-22 13:17 +0200
Re: misterious behavior of either kill or terminal marrgol <marrgol@address.invalid> - 2019-06-22 13:32 +0200
Re: misterious behavior of either kill or terminal Soviet_Mario <SovietMario@CCCP.MIR> - 2019-06-23 17:57 +0200
Re: misterious behavior of either kill or terminal Paul <nospam@needed.invalid> - 2019-06-21 15:14 -0400
Re: misterious behavior of either kill or terminal Melzzzzz <Melzzzzz@zzzzz.com> - 2019-06-21 20:42 +0000
Re: misterious behavior of either kill or terminal Soviet_Mario <SovietMario@CCCP.MIR> - 2019-06-22 00:23 +0200
Re: misterious behavior of either kill or terminal "J.O. Aho" <user@example.net> - 2019-06-22 09:50 +0200
Re: misterious behavior of either kill or terminal gazelle@shell.xmission.com (Kenny McCormack) - 2019-06-22 19:13 +0000
Re: misterious behavior of either kill or terminal "J.O. Aho" <user@example.net> - 2019-06-22 23:41 +0200
Re: misterious behavior of either kill or terminal "Carlos E.R." <robin_listas@es.invalid> - 2019-06-22 13:30 +0200
Re: misterious behavior of either kill or terminal "J.O. Aho" <user@example.net> - 2019-06-21 21:39 +0200
Re: misterious behavior of either kill or terminal Soviet_Mario <SovietMario@CCCP.MIR> - 2019-06-22 00:33 +0200
Re: misterious behavior of either kill or terminal "J.O. Aho" <user@example.net> - 2019-06-22 09:28 +0200
Re: misterious behavior of either kill or terminal "Carlos E.R." <robin_listas@es.invalid> - 2019-06-22 13:34 +0200
csiph-web