<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Dan,<div>Great news on your shell scripting skills..... as I haven't done any. Yes, the mutual exclusivity of wwwoffle and squid would be one part. Below are some earlier comments from Martin that help define the opportunity/plan better.</div><div><br></div><div>From Martin's first thoughts on automating wwwoffle....</div><div><blockquote type="cite"><div></div></blockquote><blockquote type="cite"><blockquote type="cite"><div><br>- Can we remove the need to set proxy on every XO by either...<br> - using a transparent proxy, same as we do with SQUID (maybe make a<br>TURN_ON_WWWOFFLE script)?<br> - serving a proxy autoconfig file via dhcp/apache?<br><br>- Is it viable to automate the "go online / go offline" with a<br>cronjob that pings a public host ( ping -c1 google) every 5 minutes?<br>Or...<br><br>- If there's a daemon managing the connetion (case of pppd), use the<br>"down" and "up" hooks? This would only work if the daemon catches the<br>"link is lost" situation reliably.</div></blockquote></blockquote><div><br></div>A follow up note from Martin with some additional detail/thoughts....</div><div><br></div><div><blockquote type="cite"></blockquote></div><blockquote type="cite"><div><blockquote type="cite">how are things going with that wwwoffle script? I am catching up a bit<br></blockquote><blockquote type="cite">on my XS stuff and was wondering if life would be easier for you (and<br></blockquote><blockquote type="cite">me) following the strategy we've outlined for services in 0.7.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">- a separate init script: /etc/init.d/xs-wwwoffle -- based on what's<br></blockquote><blockquote type="cite">in the rpm or what upstream ships<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">- a separate config dir /etc/xs-wwwoffle<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">- a TURN_WWWOFFLE_ON script (copy the squid approach, we'll come up<br></blockquote><blockquote type="cite">with something better for 0.7)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">- if we need to 'sed' anything into the config files, it can be done<br></blockquote><blockquote type="cite">in the init script, so a change of FQDN gets taken up in the next<br></blockquote><blockquote type="cite">service (or server) restart<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">If you give me the scripts and config files (tested ;-) ), I will add<br></blockquote><blockquote type="cite">them to xs-config so users of 0.6 can benefit from your work.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I will polish up the wwwoffle rpm with the latest upstream version so<br></blockquote><blockquote type="cite">we ship that one.<br></blockquote></div></blockquote><div><br></div><div><div>On Jan 25, 2011, at 5:37 PM, Dan Zubey wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div text="#000000" bgcolor="#ffffff">
Hi Andy<br>
<br>
Well shell scripting is one of my strong points. I can put something
together quickly here.<br>
<br>
I assume the script should make squid and wwwoffle mutually
exclusive...so that when wwwoffle is enabled, squid gets disabled,
and vice versa?<br>
<br>
<br>
<br>
On 01/22/2011 04:44 PM, Andra DuPont wrote:
<blockquote cite="mid:5C0A9B7A-F46A-45E1-AA20-16F45CAE3799@gmail.com" type="cite">
<div><br>
<div>
<div>On Jan 22, 2011, at 4:51 PM, Martin Langhoff wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div>On Sat, Jan 22, 2011 at 4:44 PM, Anna <<a moz-do-not-send="true" href="mailto:aschoolf@gmail.com">aschoolf@gmail.com</a>>
wrote:<br>
<blockquote type="cite">Wasn't me! I tried to get it to
work the other day on my test server<br>
</blockquote>
<br>
Ah true, it was Andra! I'm all mixed up...<br>
<br>
<br>
</div>
</blockquote>
<div>Yes... it was me. I input the "<a moz-do-not-send="true" href="http://wiki.laptop.org/go/XS_Techniques_and_Configuration#WWWOFFLE_for_unreliable_or_intermittent_internet_connections">WWWOFFLE
for unreliable or intermittent internet connections</a>"
section of the "<a moz-do-not-send="true" href="http://wiki.laptop.org/go/XS_Techniques_and_Configuration">XS
Techniques and Configuration</a>". I am running wwwoffle
on an XS in Kenya, and it is helping out a lot. In fact, we
have loaded up a ton of educational site pages to the XS
while on high speed connection, and all this material is
available to the students even when the XS is offline, which
is most of the time. We have created courses in Moodle where
the topics are groupings of educational categories, and each
educational site is add to the topic as a "link to a
website" resource.</div>
<div><br>
</div>
<div>As you can tell from the method I used, it is a manual
process, and Martin has asked me to work on making it a
little more integral to the build, so that a script can take
care of switching between Squid and wwwoffle for instance.</div>
<div><br>
</div>
<div>I have not had the time to develop this yet, and will be
going back to Kenya soon. I hope to carve out some time
soon, but if you want to jump in, that would be great.</div>
<div><br>
</div>
<div>Andy (Andra is my legal/formal name).</div>
<blockquote type="cite">
<div><br>
<br>
m<br>
-- <br>
<a moz-do-not-send="true" href="mailto:martin.langhoff@gmail.com">martin.langhoff@gmail.com</a><br>
<a moz-do-not-send="true" href="mailto:martin@laptop.org">martin@laptop.org</a>
-- School Server Architect<br>
- ask interesting questions<br>
- don't get distracted with shiny stuff - working code
first<br>
- <a moz-do-not-send="true" href="http://wiki.laptop.org/go/User:Martinlanghoff">http://wiki.laptop.org/go/User:Martinlanghoff</a><br>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</blockquote></div><br></body></html>