Wow. Looks like I really need to take a look at 2.0.
To get the list of groups, Leafwa simply runs ls on the
interesting.groups directory, which you should have defined
in settings.inc. Is this set up correctly?
It might be interesting to try setting the $debug variable
in subun.php to 1 and trying again, although that doesn't
add much. I've just noticed that subun.php needs some work
to use the new debugging functions - one more for the task
list...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have 2.0, but I've never set it up for contacting nntp
feeds... but... I'd have to say that this also sounds like a
permissions issue. (Though I suppose it could be related
file name or format too).
Off the cuff, I am wondering if we should have a leaf.wa
subdirectory in /var/spool/news that we copy relevant files
to via sudo - before analyzing them. This actually might be
more safe, especially for the local group options, since it
would let us check if our master still looks the same as
leafnode's file before we drop in edits... I suspect that
leafnode wouldn't grab permissions away from such a
directory since it is not part of leafnode's file set.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=3132
Wow. Looks like I really need to take a look at 2.0.
To get the list of groups, Leafwa simply runs ls on the
interesting.groups directory, which you should have defined
in settings.inc. Is this set up correctly?
It might be interesting to try setting the $debug variable
in subun.php to 1 and trying again, although that doesn't
add much. I've just noticed that subun.php needs some work
to use the new debugging functions - one more for the task
list...
Logged In: YES
user_id=128814
The setting is correct in the settings.inc file. I did a ls
on that group and got the group names back. But, for some
reason, Leafwa does not like it.
Logged In: YES
user_id=3132
OK, I need to upgrade to 2.0 to find out why this is
happening. It works in 1.9.x
Logged In: YES
user_id=697549
I have 2.0, but I've never set it up for contacting nntp
feeds... but... I'd have to say that this also sounds like a
permissions issue. (Though I suppose it could be related
file name or format too).
Off the cuff, I am wondering if we should have a leaf.wa
subdirectory in /var/spool/news that we copy relevant files
to via sudo - before analyzing them. This actually might be
more safe, especially for the local group options, since it
would let us check if our master still looks the same as
leafnode's file before we drop in edits... I suspect that
leafnode wouldn't grab permissions away from such a
directory since it is not part of leafnode's file set.