Does it continue to run if you logout?

Question

Does it continue to run if you logout?

twerthi opened this issue 2 years ago · 7 comments

Greetings! I SSH into a RPi machine and started the script manually (versus configuring to run on boot). I logged out of the session and noted that the HDD activity light on my HDD dock was still blinking, may I assume that means it's still running? If so, may I also assume the dock HDD activity light will stop blinking once it's complete?

Answer 1 · 2022-08-24T01:40:31.000Z

You can check if there is a shred process still running like this. It sounds like that's the case. ``` ps aux | grep shred ```

…

On Tue, Aug 23, 2022, 8:38 PM Shawn Sesna ***@***.***> wrote: Greetings! I SSH into a RPi machine and started the script manually (versus configuring to run on boot). I logged out of the session and noted that the HDD activity light on my HDD dock was still blinking, may I assume that means it's still running? If so, may I also assume the dock HDD activity light will stop blinking once it's complete? — Reply to this email directly, view it on GitHub <#6>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASFVZPM3DSOSOKANFWW47TV2VVJHANCNFSM57NNF2SQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

Answer 2 · 2022-08-24T01:43:16.000Z

If you run the program in `screen`, it will continue to run after you log out. At that point you can keep inserting drives to wipe.

…

On Tue, Aug 23, 2022, 9:40 PM Phil Porada ***@***.***> wrote: You can check if there is a shred process still running like this. It sounds like that's the case. ``` ps aux | grep shred ``` On Tue, Aug 23, 2022, 8:38 PM Shawn Sesna ***@***.***> wrote: > Greetings! I SSH into a RPi machine and started the script manually > (versus configuring to run on boot). I logged out of the session and noted > that the HDD activity light on my HDD dock was still blinking, may I assume > that means it's still running? If so, may I also assume the dock HDD > activity light will stop blinking once it's complete? > > — > Reply to this email directly, view it on GitHub > <#6>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AASFVZPM3DSOSOKANFWW47TV2VVJHANCNFSM57NNF2SQ> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >

Answer 3 · 2022-08-24T01:58:00.000Z

I apologize for my lack of *nix knowledge. The output is

avahi      413  0.0  0.0   6916  2648 ?        Rs   Aug22   0:47 avahi-daemon: running [shredder.local]
root       832  0.0  0.0   3160   580 ?        S    Aug22   0:00 bash -c shred --force --zero --iterations=3 /dev/sda 2>/dev/null; if [ 0 -eq 0 ]; then echo 1 > /sys/block/sda/device/delete; fi;
root       836 10.4  0.0   1932   424 ?        D    Aug22 143:32 shred --force --zero --iterations=3 /dev/sda
shawn     5812  0.0  0.0   2840   592 pts/1    S+   18:56   0:00 grep --color=auto shred

I see two processes that reference shred, 832 and 836, did I accidentally start two?

Answer 4 · 2022-08-24T02:42:56.000Z

You're good to go is what I'm trying to say.

…

On Tue, Aug 23, 2022, 10:42 PM Phil Porada ***@***.***> wrote: Nope, that looks fine. 832 is a bash process running the shred program. 836 is the actual shred process forked from 832. On Tue, Aug 23, 2022, 9:58 PM Shawn Sesna ***@***.***> wrote: > I apologize for my lack of *nix knowledge. The output is > > avahi 413 0.0 0.0 6916 2648 ? Rs Aug22 0:47 avahi-daemon: running [shredder.local] > root 832 0.0 0.0 3160 580 ? S Aug22 0:00 bash -c shred --force --zero --iterations=3 /dev/sda 2>/dev/null; if [ 0 -eq 0 ]; then echo 1 > /sys/block/sda/device/delete; fi; > root 836 10.4 0.0 1932 424 ? D Aug22 143:32 shred --force --zero --iterations=3 /dev/sda > shawn 5812 0.0 0.0 2840 592 pts/1 S+ 18:56 0:00 grep --color=auto shred > > I see two processes that reference shred, 832 and 836, did I accidentally > start two? > > — > Reply to this email directly, view it on GitHub > <#6 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AASFVZJZ3JXYCWRJQL7O7RLV2V6THANCNFSM57NNF2SQ> > . > You are receiving this because you commented.Message ID: > ***@***.***> >

Answer 5 · 2022-08-24T02:44:33.000Z

Excellent. I very much appreciate your prompt responses, thank you.

Answer 6 · 2022-08-25T00:15:10.000Z

One last question, if I may. Am I correct in that once it's complete, the HDD activity light should stop blinking? I've it running on an RPi4 against a 4TB HDD on a USB 2.0 connection, it's been running for almost two days.

Answer 7 · 2022-10-11T06:58:03.000Z

Nope, that looks fine. 832 is a bash process running the shred program. 836 is the actual shred process forked from 832.

…

On Tue, Aug 23, 2022, 9:58 PM Shawn Sesna ***@***.***> wrote: I apologize for my lack of *nix knowledge. The output is avahi 413 0.0 0.0 6916 2648 ? Rs Aug22 0:47 avahi-daemon: running [shredder.local] root 832 0.0 0.0 3160 580 ? S Aug22 0:00 bash -c shred --force --zero --iterations=3 /dev/sda 2>/dev/null; if [ 0 -eq 0 ]; then echo 1 > /sys/block/sda/device/delete; fi; root 836 10.4 0.0 1932 424 ? D Aug22 143:32 shred --force --zero --iterations=3 /dev/sda shawn 5812 0.0 0.0 2840 592 pts/1 S+ 18:56 0:00 grep --color=auto shred I see two processes that reference shred, 832 and 836, did I accidentally start two? — Reply to this email directly, view it on GitHub <#6 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASFVZJZ3JXYCWRJQL7O7RLV2V6THANCNFSM57NNF2SQ> . You are receiving this because you commented.Message ID: ***@***.***>