Conversation

Notices

1. Angry Sun (sun@shitposter.world)'s status on Thursday, 12-Dec-2024 00:19:46 JST Angry Sun
   tfw you start a script in a shell but not in tmux and you realize how long it's gonna take
   • matrix07012 :thotpatrol: and Dushman like this.
   • BSD/r000t (r000t@ligma.pro)'s status on Sunday, 15-Dec-2024 07:04:34 JST BSD/r000t

     in reply to

     @sun ctrl+z, then run ‘bg’

   • anemone@ebiverse.social's status on Sunday, 15-Dec-2024 07:11:31 JST anemone

     in reply to

     • BSD/r000t

     @r000t@ligma.pro @sun@shitposter.world it's still owned by the shell so will stop if you close/disconnect though wont it?

   • BSD/r000t (r000t@ligma.pro)'s status on Sunday, 15-Dec-2024 07:11:31 JST BSD/r000t

     in reply to

     • anemone

     @anemone @sun The orphaned process will become owned by init. Same as if you ran &

     You could test it. Run a loop that increments a counter and appends it to a file. Suspend the shell, background the process, reconnect and `tail -f` the file. Then find and kill the process you started.

   • Angry Sun (sun@shitposter.world)'s status on Sunday, 15-Dec-2024 07:37:36 JST Angry Sun

     in reply to

     • BSD/r000t
     • anemone
     @anemone @r000t yes
   • BSD/r000t (r000t@ligma.pro)'s status on Sunday, 15-Dec-2024 07:37:36 JST BSD/r000t

     in reply to

     • anemone

     @sun @anemone well, fuck. I guess if you nohup’d it first….

     Or just only connected through sth like mosh

   • BSD/r000t (r000t@ligma.pro)'s status on Sunday, 15-Dec-2024 07:50:24 JST BSD/r000t

     in reply to

     • mr64bit
     • anemone

     @mr64bit

     @anemone @sun

   • mr64bit (mr64bit@p.mr64.net)'s status on Sunday, 15-Dec-2024 07:50:25 JST mr64bit

     in reply to

     • BSD/r000t
     • anemone
     @r000t @anemone @sun I believe it still receives a SIGHUP, some things may quit in response. You can still `disown` the job to prevent that though.