Search Results

I thought using screen -ls was more elegant. This is what I came up with:



#!/bin/sh
# chkscreen: checks if a screen session is running.
WORKINGDIR=/home/mute/test
PIDFILE=cb.pid...

screen will spawn a child, so I was thinking using $$ from 'exec'


You'll be checking if jd.sh is running. If it's running, java must be.. If it's not running, screen would exit (unless you add...

Well I didn't actually lose sleep but thought of it. As I said, and tested, using -r started new screens each time chkscreen is ran if I was attached, because it checks for attachable screens and it...

There's just many different ways it can be solved. Instead of keeping a PID file (my original trial) I just ask screen if the session is running. It makes it so elegant, eh? :)

Thanks for the...

Having screen as part of the equation at first seemed difficult for me. Then I read the manual...

Firstly, we create the crontab-able script which checks if the screen session is started.

...

And this has to stay inside of a screen session because it's interactive, or just a way to view the output?

running your "exec" script in the background is not sufficient?

shell$ ./exec &
...