Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.os.linux > #57081
| From | Dan Purgert <dan@djph.net> |
|---|---|
| Newsgroups | alt.os.linux |
| Subject | Re: misterious behavior of either kill or terminal |
| Date | 2019-06-21 18:21 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <slrnqgq80t.ds3.dan@djph.net> (permalink) |
| References | <qej6cu$61p$1@dont-email.me> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 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>'. > [...] > 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. -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEBcqaUD8uEzVNxUrujhHd8xJ5ooEFAl0NIB0ACgkQjhHd8xJ5 ooGvRAgAsBh8qO1jopKr9B1esSOV5yt8ZbI0JN6/F8YSsfoGXQU1U6KOaVdxhjKi 0m7p1r2y9QZ0XbAldhkt4p5HUPD7VqsoV6sSAHJAVSdn88s56XmWac3RZqZV+DsG 09YuWQlTZNK2XJzSq25X0o0yGPCENh2ilfMLIYVJohJre3In3Sj30/sHGCeQQ3Sl 0LmhQ2R1Vw+ljGFpcO7TOdavgW3RVIZ9eNP7CAksM/BOsbUIvsVs8jBqj779bkTk 6es9h6m6ICoKJu8iVDwBd0cFJ2UCvhcDV35mxVCop1poVFUGN89Zi4YRGiS4ccEy Ezl5qWeb4rFYj3TFYo6T0doEX6DAFQ== =j8ok -----END PGP SIGNATURE----- -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5 4AEE 8E11 DDF3 1279 A281
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