[sword-devel] Monitoring the sources for our modules?
d.haslam at ukonline.co.uk
Mon Sep 7 00:01:04 MST 2009
I am impressed, even though the line is somewhat obscure to the uninitiated.
I suppose it would be "icing on the cake" to have the output sorted? ;>}
We should do the same for those in the beta repo.
The checking for broken links using Xenu's LinkSleuth would be a very useful
For that, we'd need to pipe the script output to a standalone web-page
somewhere on crosswire.org,
but one with no links back to anything else on our server.
Running LinkSleuth on the whole of our server is a fruitless task! I once
Jonathan Marsden wrote:
> David Haslam wrote:
>> http://home.snafu.de/tilman/xenulink.html Xenu's Linksleuth , but first
>> someone would have to generate a single page containing a table listing
>> every module in one column, and the "supplier" URL (from the conf files)
> Here's an improved version. Not exactly readable, but appears to work.
> Still a (long) oneliner :)
> wget -O- -q ftp://ftp.crosswire.org/pub/sword/raw/mods.d.tar.gz |tar
> zxOf - |egrep "^\[|TextSource=.*http" |sed -e 's/^.*http/http/' -e
> 's/,.*$//' |tr '\n' ' ' |sed -e 's/\(http[^ ]\+ \)/\1\n/g' |sed -e
> 's/^.*\(\[.*\]\)/\1/' |head --lines=-1
View this message in context: http://www.nabble.com/Monitoring-the-sources-for-our-modules--tp25318901p25325860.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
More information about the sword-devel