[Commotion-dev] Fwd: Re: Node Crashing / Nodogsplash

[Dan Staples]

Just wanted to check with the other OpenWRT-knowledgeable folks about
this...there's no way to fix a filled filesystem issue without
reflashing, right? I was under the impression that squashFS is append-only.

Dan


-------- Original Message --------
Subject: 	Re: Node Crashing / Nodogsplash
Date: 	Sun, 10 Nov 2013 10:26:09 +0300
From: 	Daniel Hastings <dhastings at abaarsotech.org>
To: 	Dan Staples <danstaples at opentechinstitute.org>



Hey Dan,

Trying to disable no dog splashI typed this: /etc/init.d/nodogsplash disable

and got this:

rm: can't remove '/etc/rc.d/S65nodogsplash': No space left on device
rm: can't remove '/etc/rc.d/K65nodogsplash': No space left on device

Thanks

Dan



On Fri, Nov 8, 2013 at 6:42 PM, Dan Staples
<danstaples at opentechinstitute.org
<mailto:danstaples at opentechinstitute.org>> wrote:

    Thanks Dan, I'll add a feature request to add a mechanism for simply
    turning off the captive portal.

    On Thu 07 Nov 2013 10:20:51 AM EST, Dan Hastings wrote:
    > Got it. I didn't use that before.  I just figured just hitting
    > "Immediately Authenticate" under captive portal would completely
    disable
    > it. I guess I was wrong about that. Is there a way in the web
    interface
    > to do this or do you think that may be possible to include in the
    future?
    >
    > I'll run that tomorrow morning and do a test tomorrow with a group of
    > students to see if it makes a difference.  We had the same issue today
    > again. Same number of students same behavior.  It seems that it only
    > happens with my first class and then it doesn't reoccur with the
    classes
    > after.  I hope this helps you are able to get to the bottom of the
    > issue.  Thanks for the help.
    > On 11/7/13 3:40 PM, Dan Staples wrote:
    >> Hmmm, to disable NDS I'd recommend running "/etc/init.d/nodogsplash
    >> disable". Is that what you tried before?
    >>
    >> Also keep in mind that the memory usage reported by top can be wildly
    >> inaccurate for nodogsplash...sometimes it reports > 200% memory usage
    >> just by nodogsplash alone, yet there will be plenty of free memory.
    >>
    >> Several of us have been working yesterday and today on
    reproducing the
    >> crashes you're seeing and getting to the bottom of what's causing it.
    >> We'll let you know what we find.
    >>
    >> Thanks, and let me know if you see anything else!
    >>
    >> Dan
    >>
    >> On 11/07/2013 06:32 AM, Daniel Hastings wrote:
    >>> Hey Dan,
    >>>
    >>> I tried sending this to the list yesterday but it didn't go
    through. I
    >>> also attached a screenshot of top running as the node crashed. I
    think
    >>> the problem may be no dog splash not being completely disabled.
    >>>
    >>> Dan
    >>>
    >
    >

    --
    Dan Staples

    Open Technology Institute
    https://commotionwireless.net
    OpenPGP key: http://disman.tl/pgp.asc
    Fingerprint: 2480 095D 4B16 436F 35AB 7305 F670 74ED BD86 43A9




-- 
*Dan Hastings*
/Abaarso School Computer Science Department/
dhastings at abaarsotech.org <mailto:dhastings at abaarsotech.org>