Dan Jacobson <[EMAIL PROTECTED]> writes:

> >> perhaps i should also do
> >> 
> >> killall -HUP wwwoffles
> >> 
> >> there too?
> 
> ab> You could except that there are no processes called wwwoffles.  This
> ab> is a historical hangover from version 1 of WWWOFFLE where the child
> ab> processes were a different program.  Now that it forks off a copy of
> ab> the same program they are all called wwwoffled, but wwwoffles is
> ab> retained for the syslog output.
> 
> odd... then this needs to be made truthful and accurate for bug
> hunters to not be looking for wwwoffles.

The description of the wwwoffles / wwwoffled difference is in the
README file.  I would hope that anybody that is going to hunt for bugs
would read some of the documentation.


> Anyway, I have the ability with killall from ip-down to send any certian/all the
> wwwoffle subprocesses a kill -HUP signal ... which I hope they would
> handle as "don't keep trying to read from the gone server, instead
> just backoff and leave the item on the outgoing list [or whatever,
> in case of partial downloads].

It is the wonderful word "whatever" that causes the problem.  In
theory it should be possible to end the program on a signal at any
point.  In practice a decision needs to be made for every block of
code to see where a signal can be tested for.  The signal handler will
set a flag and testing for that flag needs to be done at sensible
places.  The problem is in identifying all of those places and
deciding an appropriate error condition or exit mechanism.


> Anyways, I'm hoping every wwwoffle subprocess could be fitted with
> procedures for what to do incase the line was hungup [or i send that
> signal] at every state.

I will put this request in my TODO file.


> By the way, it would be neat if along with
>    [Outgoing] [Monitored] [Last Time] [Last Outgoing] [http] [ftp] [finger]
>          [Unsorted] [Modification Time] [Access Time] [Date Changed] [Alphabetical]
>                              [Domain Name] [File Type] [Random]
> 
> there could also be a [Screwups]
> which would be, say like the lasttime list, but instead with
> categories
> 
> Pages that failed with error 503 [time out]:
> Pages that failed with error 404 [bla bla]:
> etc.

A sort by status code option?  Interesting, but it would mean that you
need to read the contents of every file to be indexed.  Once you start
doing this you can obviously sort by other things, but there is an
overhead, potentially large with large indexes.


> By the way, "[Date Changed]" makes mysterious bars that ought to have their
> date meaning mentioned inside them: --- 3 days old ----

The meaning of the divisions in these indexes are not documented, but
then if I documented every minute feature I would never write any
code.  The rule is that a blank line is inserted for every hour, a bar
for each day and for 5 or more days the number of days is inserted
between two bars.


> >> darn, with lynx's ^E i could get to the index fast, but now it's not
> >> last on the page
> >> [Delete|Refresh:Options|Monitor|Index|Configure] - WWWOFFLE
> 
> ab> You can always edit the file that contains the message that is added
> ab> to the bottom of the page.
> 
> well, i was thinking that others might like index last too.

Well they can all edit the file as well :-)


> >>>>> "Felix" == Felix Karpfen <[EMAIL PROTECTED]> writes:
> 
> Felix> Is the need to add `-c /var/spool/wwwoffle/wwwoffle.conf' a new
> Felix> requirement needed for WWWOFFLE 2.7?  Or have I just been lucky that the
> Felix> routines worked without this addition?
> 
> this old notation should be swept out of all WWWOFFLE docs and
> programs now that WWWOFFLE has finally gotten with the /etc config
> file home default standard.

No, this is not true.  Only if you install the configuration file in
the place that the compiled executable expects to find it will you not
need the parameter.  Simplifying the description for the sake of
people who never move configuration files only confuses people who
like to live dangerously.  It works for everybody and people who read
the instructions can figure out they don't need the extra option.

(I have however just replaced all references to
/var/spool/wwwoffle/wwwoffle.conf with /etc/wwwoffle.conf to be
consistent.)


-- 
Andrew.
----------------------------------------------------------------------
Andrew M. Bishop                             [EMAIL PROTECTED]
                                      http://www.gedanken.demon.co.uk/

WWWOFFLE users page:
        http://www.gedanken.demon.co.uk/wwwoffle/version-2.6/user.html

Reply via email to