[nos-bbs] tty lock file mystery solved

[Michael Fox - N6MEF]

We start up JNOS in a detached "screen" session.  Then we can reattach from an SSH session.
M

-- Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: "George \[ham\] VerDuin" <k8rra at ameritech.net>
Sender: nos-bbs-bounces at tapr.org
Date: Sat, 26 Feb 2011 00:03:11 
To: TAPR xNOS Mailing List<nos-bbs at tapr.org>
Reply-To: TAPR xNOS Mailing List <nos-bbs at tapr.org>
Subject: Re: [nos-bbs] tty lock file mystery solved

You might be a bit hard on yourself Michael.


On 02/25/2011 08:34 PM, Michael Fox - N6MEF wrote:
>
> I was updating some configurations on the production machine. I was so 
> used to not having JNOS running continuously on my laptop, that I 
> started it (again) with a quick “sudo ./jnos.exe” to check my updates. 
> Well, trying to start it a second time, the ports were already locked, 
> so the attach commands failed and it then complained about every other 
> port-related command after that.
>
This scenario prompts another question from here. How do you get access 
to the sysop console on the production host at the location where you 
are doing the work? Just wondering...

I don't suggest it eliminates the double start, but it does present a 
second way of checking some config changes?

Cheers -- glad you solved the mystery.
Skip

_______________________________________________
nos-bbs mailing list
nos-bbs at tapr.org
https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs