Basically, I've got a USB/Serial adapter which I have installed the drivers for etc and use to communicate with my routers and switches.

Command to begin comms:


It works a treat, and I can do everything I need to.

The problem is when I'm finished, and I attempt to run screen again it gives an error that the resource is busy.

How can I close screen in such a way that it handles this nicely, and doesn't lock the resource?

Also - is there a way to unlock the resource, other than restarting the machine??

Have you tried:


Not sure if that works, but from the man page:

Ah okay! Thanks for that post forquare.

That doesn't solve my problem, but I've noticed in Activity Monitor that Screen is still running. When inspecting the process, I can see that it has still got the resource open.

I can't remember exactly how I closed Screen before, but I'm assuming that I must have just closed the Terminal window because it's still running!

From Activity Monitor I quit the process and now all is well. I'll have to Google how to exit Screen.

On the down-side, I've now run out of excuses not to crack on with my Cisco IOS studies!

Screen will continue running while any child process is running.

If you just close the Terminal window down or do "Ctrl-a d" within screen, then it will continue to run.
You should be able to reattach using

Cool.

I was just quite surprised it didn't stop running when I logged out.

screen -D wanted a session name, so screen -r probably will too. I don't know what the hell that is, or how I can find it so for now I'm gunna stick to the n00by way of force quitting it from Activity Monitor!

In labs at uni I don't have such a problem because I use two screen sessions (one for each serial port) for the whole three hour lab, then shut the machine down and take the HDD home. I don't think many processes are able to remain open through that ordeal!

Screen is quite a cool tool, but it took me ages to get my head around it. I didn't know you could use it in the way you are using it.
I write a page to remind myself what I know about screen, you can find it here it it's any use:
http://hashbang0.com/?location=tutorial ... &section=7