Using the GNU Screen Instead of Demonstrating

I just took on an outdated application that runs background processes in GNU screen sessions, rather than unmounting them. I am trying to understand why the original programmer wrote it like this. Is there a good reason to start processes on the screen rather than fork them or start them with nohup ?

+4
source share
1 answer

Comment @Marc B represents a very good point (as, unfortunately, this is not the answer, that would be nice!). In any case, another reason I see this is the fact that it is simply too simple to use the screen to pseudo-dipon the application.

For example, I do this a lot. For example, I am developing a Django application for my company, which I will introduce in the future. It is not complete, but useful to me, so I started it on a screen session and left it available for use when I need it.

+2
source

All Articles