<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Well, I did figure out one thing.... <BR>
<BR>
My inital post that JNOS was not automatically starting using this line:<BR>
"exec /jnos/jnos -a 40 -d/jnos </dev/tty4> /dev/tty4 2>&1" was, in fact, correct.<BR>
<BR>
Before this issue, when JNOS did auto-run, I did use that command.<BR>
<BR>
After the issue arose, I had to modify the line and drop the last part of "...... 2>&1" so that the line now reads:<BR>"exec /jnos/jnos -a 40 -d/jnos </dev/tty4> /dev/tty4"<BR>
<BR>
I forgot to post that the yesterday when I discovered that JNOS now runs with just a blinking cursor.<BR>
<BR>
If I manually enter the line as "exec /jnos/jnos -a 40 -d/jnos </dev/tty4> /dev/tty4 2>&1" at a command promt, leaving the "2>&1" part in, linux responds with an "ambiguous redirect" error. That gave the clue to remove the "..2>&1" portion, thus getting JNOS to finally run on computer startup/boot.<BR>
<BR>
I should re-state that JNOS was not starting until I removed the last part.<BR>
<BR>
As for the "-a 40" part you asked about, that tells JNOS to allow no more than 40 axip/udp links.<BR>
<BR>So, as it is, JNOS starts. It just doesn't reveal that when I toggle to console 4. <BR>
<BR>
Booting with different kernals has no change.<BR>
<BR>
In the words of Leonard Nimoy, I am still "In search of" ....<BR>
<BR>
Bill<BR>
KG6BAJ<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
> Date: Fri, 4 Feb 2011 22:33:43 -0500<BR>> From: k8rra@ameritech.net<BR>> To: thunderft@hotmail.com<BR>> Subject: Re: My interest is now piqued<BR>> <BR>> OOPS Bill -- sorry I did not remember you spread out the stuff in your <BR>> reflector posts...<BR>> <BR>> <BR>> On 02/04/2011 06:41 PM, Wm Lewis wrote:<BR>> > Skip:<BR>> ><BR>> > JNOS is being started automatically on computer bootup/restart.<BR>> FYI:<BR>> "crw--w---- 1 root tty 4, 4 2011-01-31 00:34 /dev/tty4"<BR>> <BR>> c -> is a "character by character" I/O device<BR>> root -> root user owns the the device<BR>> tty -> is the group of users with special privileged access to the<BR>> device<BR>> rw- -> is the basic "read" and "write" and "execute" privilege set<BR>> rw--w---- -> the set is repeated three times for root, tty, and all<BR>> other users<BR>> 4, 4 -> is the programming linkage from the kernel to the outside world<BR>> 2011-01-31 00:34 -> is the time stamp for the last time it was modified<BR>> /dev/tty4 -> is the name of the device we all use [it's like "COM4"<BR>> in the DOS world].<BR>> <BR>> Does that help?<BR>> <BR>> ><BR>> > Jnos is loaded into TTY4/Console 4.<BR>> Yup -- I got that part.<BR>> Given the /var/log messages output, I'm surprised to see the "ps" return <BR>> jnos as running.<BR>> From your earlier post the following:<BR>> <BR>> Jan 30 19:07:25 linux init: tty4 main process ended, respawning<BR>> Jan 30 19:07:25 linux init: tty4 main process (21226) terminated<BR>> with status 2<BR>> Jan 30 19:07:25 linux init: tty4 main process ended, respawning<BR>> Jan 30 19:07:25 linux init: tty4 main process (21229) terminated<BR>> with status 2<BR>> Jan 30 19:07:25 linux init: tty4 main process ended, respawning<BR>> <BR>> is telling you that the<BR>> <BR>> ========================================================<BR>> rm -f /jnos/spool/mqueue/*.lck 2> /dev/null<BR>> rm -f /jnos/spool/mail/*.lck 2> /dev/null<BR>> exec /jnos/jnos -a 40 -d/jnos </dev/tty4> /dev/tty4 2>&1<BR>> ========================================================<BR>> <BR>> Script is failing and then restarting.<BR>> Notice the short time span for all the respawn cycles? -- its the <BR>> script itself.<BR>> Jnos is never really getting started until the last try [when the kernel <BR>> sorta "gives up trying"]<BR>> The last try is done without fully attaching the sysop console to tty4 <BR>> [that's why the cursor only]<BR>> <BR>> ><BR>> > See my previous posts for the method used. (I don't want to repost it <BR>> > all over, again)<BR>> I'm not comfortable with the:<BR>> <BR>> "exec /jnos/jnos -a 40 -d/jnos </dev/tty4> /dev/tty4 2>&1"<BR>> <BR>> <BR>> line in the init script.<BR>> <BR>> -a 40 -- is a parm I don't recognize<BR>> -d/jnos -- specifies the execution working directory<BR>> </dev/tty4> -- specifies tty4 is used for both input & output<BR>> /dev/tty4 -- HHMMM I wonder why the repeated ref to tty4<BR>> 2>&1 -- put the error message stream together on the<BR>> standard output stream.<BR>> <BR>> But I can't tell you what a better syntax would be.<BR>> Maybe "</dev/tty4> /dev/tty4" should be "</dev/tty4 >/dev/tty4"?<BR>> I suggest you do some google research to get more opinions.<BR>> WB8RCR has some good material for this purpose.<BR>> <BR>> ><BR>> > Yes, the only issue is that JNOS used to be *visible* when I toggled <BR>> > over to console 4.<BR>> > Yes, I would like it to be visible again.<BR>> ><BR>> > Right now, when I toggle over to console 4, it only shows a blinking <BR>> > cursor line.<BR>> Yes -- jnos is not hooking up properly to /dev/tty4 device.<BR>> <BR>> ><BR>> > Bill<BR>> Good luck with the "init tty" approach to starting jnos.<BR>> I'm delighted with the "service" approach including screen -- if you <BR>> want to switch to this method I'd be happy to send you the scripts I use <BR>> as a go-by.<BR>> <BR>> 73<BR>> Skip<BR> </body>
</html>