[nos-bbs] ubuntu 9.1 compiles OK now, but... FIXED!!

[jerome schatten]

Excuse me for replying to my own message... 

I just moved my two instances of jnos which are linked together by axip
to the root folder and became root, started both Nos's, and lo and
behold, weirdness and inconsistencies seem to be GONZO!  
Thanks to everyone that helped -- I learned lots.  
Best,
Jerome - VA7VV



On Thu, 2010-11-25 at 21:13 -0800, jerome schatten wrote:
> Thanks Jim... those were my thoughts almost exactly. I can remember
> reading somewhere that sudo works for a specific number of minutes
> without asking again for a password, but I that's a different story. I
> think what your saying is that processes started with sudo ended up
> eating 100% of cpu usage over time and that jnos will do that. I haven't
> noticed that (I've had jnos up for three or four days at a time), but I
> have noticed in earlier kernel versions of 9.1 that udev ends up driving
> the cpu to 100% over time. It depended on what was running -- the ant
> with the flashlight screensaver always did that after a while. 9.04 was
> fine. That all seemed to go away with later kernel updates in 9.1.
> 
> The stuff that's happening around the 'tun' device(s) is really weird,
> so I'm going to see if running from and as root solves that problem.
> 
> Failing that, I do have another box (quite old) with slack 10.0 (no gui)
> on it that I can try the same setup on.
> 
> Thanks for your comments,
> Jerome - VA7VV
> 
> On Thu, 2010-11-25 at 22:58 -0500, Jim Smith wrote:
> > Jerome,
> > 
> >   I had some issues running it with sudo (Ubuntu 9.1 and later). Never
> > figured it out, but it seemed to be time related. Things would work, then it
> > didn't, anywhere from 4 to 28 hours later. It *never* ran past 28 hours or
> > so. I ran it as root and never had that problem. I think it has to do with
> > the way sudo works. I notice that if I'm doing a lot of sudo, it does not
> > ask me for a password on actions subsequent to the first sudo *up until* I
> > go beyond a time limit, then it asks for a password to do sudo actions
> > again.
> > 
> >   My guess is the jnos process at some point doesn't use the magic sudo
> > powers for long enough and the sudo password cache times out which causes
> > the jnos process issues. I have no firm data on this, just a niggling
> > thought. What I *did* have that put me off of Ubuntu was that anywhere from
> > 24 to 48 hours after the process started it would start consuming all CPU on
> > the box. I built a slackware 10.1 box and it has run well on that.
> > 
> > Cheers!
> > 
> > Jim N8AVX
> > 
> > -----Original Message-----
> > From: nos-bbs-bounces at tapr.org [mailto:nos-bbs-bounces at tapr.org] On Behalf
> > Of jerome schatten
> > Sent: Thursday, November 25, 2010 5:04 PM
> > To: TAPR xNOS Mailing List
> > Subject: Re: [nos-bbs] ubuntu 9.1 compiles OK now, but...
> > 
> > Thanks... it compiled fine using 2.0h source. Now one more question:
> > Must I really run from root? Is it not sufficient to start jnos as:
> > 'sudo ./jnos' from the directory I have jnos in? 
> > 
> > The reason I ask is I'm getting some weird inconsistent results getting my
> > axip stuff to work. Sometimes it does, and sometimes it doesn't, and
> > sometimes only half the link works. I thought maybe it's because I'm running
> > jnos out of my home directory, starting it as sudo. ipv4 forwarding is on on
> > the jnos machine.
> > 
> > Best,
> > jerome va7vv
> > 
> > 
> > 
> > 
> > _______________________________________________
> > 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