Conversation

Notices

1. Embed this notice
   Christmas Sun (sun@shitposter.world)'s status on Thursday, 12-Dec-2024 00:18:52 JST Christmas Sun
   tfw you start a script in a shell but not in tmux and you realize how long it's gonna take
   • snacks likes this.
   • Embed this notice
     Matt Hamilton (eriner@noauthority.social)'s status on Thursday, 12-Dec-2024 00:23:13 JST Matt Hamilton

     in reply to

     @sun reptyr: https://xai.sh/2020/10/16/Move-running-process-into-tmux-session.html

     Christmas Sun likes this.
   • Embed this notice
     Christmas Sun (sun@shitposter.world)'s status on Thursday, 12-Dec-2024 00:32:40 JST Christmas Sun

     in reply to

     • Matt Hamilton
     @eriner this is scary but there's no downside to trying, the process could be restarted.
   • Embed this notice
     billiam :4chan: (billiam@shitposter.world)'s status on Thursday, 12-Dec-2024 00:53:07 JST billiam :4chan:

     in reply to
     @sun this won't work?
     >If a process is already in execution, such as the tar command example below, simply press Ctrl+Z to stop it then enter the command bg to continue with its execution in the background as a job.
     https://www.tecmint.com/run-linux-command-in-background/
   • Embed this notice
     Christmas Sun (sun@shitposter.world)'s status on Thursday, 12-Dec-2024 00:53:07 JST Christmas Sun

     in reply to

     • billiam :4chan:
     @billiam yeah that might be good enough
   • Embed this notice
     Christmas Sun (sun@shitposter.world)'s status on Sunday, 15-Dec-2024 07:19:18 JST Christmas Sun

     in reply to

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

     in reply to

     @sun ctrl+z, then run ‘bg’

   • Embed this notice
     anemone@ebiverse.social's status on Sunday, 15-Dec-2024 07:19:19 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?

   • Embed this notice
     BSD/r000t (r000t@ligma.pro)'s status on Sunday, 15-Dec-2024 07:57:02 JST BSD/r000t

     in reply to

     • mr64bit
     • anemone

     @mr64bit

     @anemone @sun

     Christmas Sun likes this.
   • Embed this notice
     mr64bit (mr64bit@p.mr64.net)'s status on Sunday, 15-Dec-2024 07:57:03 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.
   • Embed this notice
     BSD/r000t (r000t@ligma.pro)'s status on Sunday, 15-Dec-2024 07:57:04 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.