Re: [leafnode-list] Web administration - leafwa

[Matthias Andree <ma@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>]

Andy Piper <andy.piper@xxxxxxxxxx> writes:

> Sounds useful, yes. Would you look at adding it to both 1.9.x and 2.x
> incarnations? From your description of the queue format, it sounds like
> you now have messages which can exist with a different status than just
> "queued".

Well, yes, we can now have "incomplete" articles in the queue. leafnode
marks them "complete" after they have been fully received, because
formerly, there was a little window in which it might happen that
fetchnews posted an incomplete article (the queue is not locked).

To simulate these, just post an article and then do chmod a-x
/var/spool/news/out.going/1-2-3. To mark it complete, to the same, but
with a+x.

> The other issue currently is that leafwa wants to know and display the
> version of leafnode which is installed. At present it uses the -V switch
> to newsq. This only works in 2.x, so all previous versions are listed as
> "before 2.0" in the screens. Is there another way of finding the
> version?

Yes, the PHP equivalent of "echo QUIT | /usr/local/sbin/leafnode" would
do. If there's a permission problem, connect to the NNTP port and send a
QUIT. The banner contains the version. The output then looks like this:

leafnode-1

200 Leafnode NNTP Daemon, version 1.9.28.cvs running at merlin.emma.line.org (my fqdn: merlin.emma.line.org)
205 Always happy to serve!

leafnode-2

200 Leafnode NNTP daemon, version 2.0.0.alpha20020930a at news.emma.line.org 
205 Always happy to serve!

(no functional changes since 1.9.27, just documentation changes)

> Well, it does that at the moment, that's what I wanted to fix it for :-)
> If the format for newsq output changes again, either leafwa has to move
> forward and abandon the old version; stay with the old version and
> development stops again; or somehow it should cope with multiple formats
> of the output without even knowing what version it is dealing
> with... see the problem? I guess I should make a release. I'm just doing
> some polishing and may put something out in the next couple of days for
> the sake of feedback. Be aware that really my only work so far has been
> a complete tidy of the code - it had clearly grown in a very
> unstructured manner - sorting out the UI, and fixing the newsq function
> for 1.9.27. I principally use it to delete messages from the spool and
> manage newsgroup subscriptions, so that's what I've worked on. No doubt
> functionality should grow, but don't expect a major change from 0.6.1
> yet.

The little things make up the warm feeling of comfort. ;-)

-- 
Matthias Andree

http://sourceforge.net/projects/leafnode/   - leafnode-1 tarballs
http://mandree.home.pages.de/leafnode/beta/ - leafnode-2 tarballs

-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list