[nos-bbs] Ubuntu 10.04 file run error
Don LaBrenz
dlabrenz at comcast.net
Sat Nov 27 20:10:58 EST 2010
I use a similar command in the script I start jnos as well.
The difference is that I have the command as "cd ../jnos"
Seems to work for me
On 11/27/2010 07:57 PM, Wm Lewis wrote:
> Ok.... So I had to turn off the computer for a while and take a break.
>
> When I turned the computer back on, my eyes caught something I had
> not paid attention too.
>
> In all the various configuration tweeks, JNOS had *tried* (I believe
> in console 5) to run and left me a bread crumb.
>
> If one is not in the JNOS directory, or doesn't tell a called script
> to be in the JNOS directory when trying to run JNOS, JNOS starts, then
> not seeing some important directories (because is was called outside
> of the JNOS directory), JNOS will create the missing directories, and
> attempt to finish booting. Usually with an error that it could not
> find the "autoexec.nos" file.
>
> The directories JNOS will create if it doesn't see them are *FINGER*
> *LOGS* *SPOOL* *WWWLOGS* *WWWSTATS*
>
> So, finally I take note that these directories exists in the root
> folder, when they should not.
>
> What this boils down to is the fact that when I boot, and have any
> script called, and that script has this line "cd /jnos", the
> script ignores it as an error and *appears* to try to run jnos, but
> not being in the jnos directory, that attempt fails.
>
> So, I would presume that maybe several variations of what I tried did
> actually get the tty5 console to flicker on, then off as jnos failed.
>
> Now I need to diagnose why the command line "cd /jnos" wont process
> when called from the "startnos" file.
>
> Bob, also a note to you. I tried doing it with "dojnos" and your file
> provided (making the changes needed) and got the same results.
>
> So..... Anyone know why Ubuntu 10.04 hates to change directories from
> a called file?
>
> Bill
> KG6BAJ
>
>
>
> ------------------------------------------------------------------------
> Date: Sat, 27 Nov 2010 14:47:46 -0500
> From: bobtenty at gmail.com
> To: nos-bbs at tapr.org
> Subject: Re: [nos-bbs] Ubuntu 10.04 autoboot JNOS & respawn
>
> NO, they don't need su/sudo in them
>
>
>
> /etc/init/tty5.conf
>
> # tty5 - getty
> #
> # This service maintains a getty on tty5 from the point the system is
> # started until it is shut down again.
>
> start on runlevel [23]
> stop on runlevel [!23]
>
> respawn
> #exec /sbin/getty -8 38400 tty5
> exec /srv/home-remote/hamradio/jnos/dojnos
>
>
> -rw-r--r-- 1 root root 258 2009-10-31 15:32 tty5.conf
>
> (never touched the owner of this file)
>
>
> On 10-11-27 02:16 PM, Wm Lewis wrote:
>
> Another thought.
>
> These command appear to work when I manally enter them at a
> different console **BECAUSE I'M LOGGED IN AS ROOT**
>
> During a power up boot, **THE SCRIPTS CALLED ARE NOT ROOT**
> Which could be why they fail.
>
> So, again I'll ask.... do any of theses commands require some sort
> of SU or SUDO injection in them?
>
> Bill
> KG6BAJ
>
> ------------------------------------------------------------------------
> From: thunderft at hotmail.com <mailto:thunderft at hotmail.com>
> To: nos-bbs at tapr.org <mailto:nos-bbs at tapr.org>
> Date: Sat, 27 Nov 2010 10:29:15 -0800
> Subject: Re: [nos-bbs] Ubuntu 10.04 autoboot JNOS & respawn
>
> ok, here's the next problem..
>
> From concole 4, I typed what you said, and console 5 did come to life.
>
> The issue was now JNOS could not find the "autoexec.nos" file because
> the "startnos" crashed on the very first command of "cd /jnos"
>
> So... now what?
>
> ------------------------------------------------------------------------
> Date: Sat, 27 Nov 2010 13:17:28 -0500
> From: bobtenty at gmail.com <mailto:bobtenty at gmail.com>
> To: nos-bbs at tapr.org <mailto:nos-bbs at tapr.org>
> Subject: Re: [nos-bbs] Ubuntu 10.04 autoboot JNOS & respawn
>
> The error is in "startnos".
>
>
> In your "startnos" file you have:
>
> exec /jnos/jnos -d/jnos -v </dev/tty5>/dev/tty5 2>&1
>
> The error is "jnos -d/jnos -v"
>
>
> You should use:
>
>
> exec /jnos/jnos -d -v </dev/tty5>/dev/tty5 2>&1
>
> -----
>
> tty5.conf itself is OK
>
>
>
> 73,
>
> Bob VE3TOK
>
>
> On 10-11-27 07:01 AM, Wm Lewis wrote:
>
> Bob:
>
> I tried updating as you said. Still no Joy.
>
> Do I need to be using some sort of SUDO command in any of this
> for it to work on boot?
>
> Here are my updated files.
>
> "startnos" file (in /jnos directory
> ==============================================
> cd /jnos
> rm -f /jnos/spool/mqueue/*.lck 2> /dev/null
> rm -f /jnos/spool/mail/*.lck 2> /dev/null
> export TZ=PST8PDT
> exec /jnos/jnos -d/jnos -v </dev/tty5>/dev/tty5 2>&1
> ==============================================
>
> and the "tty5.conf" file
>
> ==============================================
> # tty5 - getty
> #
> # This service maintains a getty on tty5 from the point the
> system is
> # started until it is shut down again.
>
> start on runlevel [23]
> stop on runlevel [!23]
>
> respawn
> exec /jnos/startnos
> ==============================================
>
> What am I missing ?
>
> Bill
> KG6BAJ
> ------------------------------------------------------------------------
> Date: Sat, 27 Nov 2010 01:23:29 -0500
> From: bobtenty at gmail.com <mailto:bobtenty at gmail.com>
> To: nos-bbs at tapr.org <mailto:nos-bbs at tapr.org>
> Subject: Re: [nos-bbs] ubuntu 9.1 compiles OK now, but...
>
> Bill:
>
> To start it in virtual tty5 add </dev/tty5>/dev/tty5 2>&1 to
> the "exec"
> line in your startnos file.
>
> like:
>
> exec ./jnos -g2 -w7+4 -d </dev/tty5>/dev/tty5 2>&1
>
>
> export TERM=linux is not necessary
>
>
> Don't use tty5 (or whatever console not in use) to your
> tty5.conf file if you use
> </dev/tty5>/dev/tty5 2>&1 , etc in your startnos file.
>
>
>
>
> You can stop and start tty5 with the commands:
>
> initctl stop tty5
> initctl start tty5
>
>
>
> 73,
>
> Bob VE3TOK
>
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org <mailto:nos-bbs at tapr.org>
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>
>
>
> _______________________________________________ nos-bbs mailing
> list nos-bbs at tapr.org <mailto:nos-bbs at tapr.org>
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
> _______________________________________________ nos-bbs mailing
> list nos-bbs at tapr.org <mailto:nos-bbs at tapr.org>
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org <mailto:nos-bbs at tapr.org>
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>
>
>
> _______________________________________________ nos-bbs mailing list
> nos-bbs at tapr.org https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20101127/31743ff8/attachment.html>
More information about the nos-bbs
mailing list