Thanks for correcting me. That makes sense now that you mention it. Maybe I
should read the documentation thoroughly another time :-)
I have tested after making the patch you suggested for the ARTICLE/BODY
problem and it works perfectly. The articles are now caching and everything
is working great. Thanks again for your time and help, I really appreciate
it. Will it be safe to assume these changes will be incorporated in your
main releases or will I need to use my patched versions from here onwards?
Regarding the "other NNTP clients", I was referring to the software that
users on my network are using to download via NNTP namely Newsleecher,
Grabit, Alt.binz etc
Lastly, some users on my network require RADIUS authentication (supported by
my feed provider). For this to work properly, I need to be able to insert a
domain identifier so that the origin server forwards RADIUS packets
correctly. Essentially, all that delegate needs to do is modify the AUTHINFO
command as follows:
AUTHINFO USER username -> AUTHINFO USER username@domain
Since the @domain part is static, it can be inserted by delegate using
strcat(user,"@domain") on each request
I have tried to patch it myself with little success :( Perhaps it could be
added as a parameter i.e. RADIUS-DOMAIN=@domainname - although I would not
mind hard coding it into the source code if needed since this is a special
I don't want to use more of your time but if you could maybe assist me with
some patch code as before, that would be very useful.
On Tue, Aug 5, 2008 at 10:13 AM, Yutaka Sato <firstname.lastname@example.org> wrote:
> In message <_A4042@delegate-en.ML_>
> on 08/05/08(04:33:55)
> you Jeff <email@example.com> wrote:
> |08/04 21:02:02.15  0+0: env
> |08/04 21:02:02.15  0+0: ext DGROOT=/var/delegate/dgtesting
> |08/04 21:02:02.15  0+0: ext ADMIN=
> |08/04 21:02:02.15  0+0: ext OWNER=news/news
> |Please accept my apologies for the extensive post.
> Nothing is bad with a extensive post.
> |It seems for some reason that it is still trying to write to
> |Even though I have specified DGROOT, CACHEDIR and the user account under
> |which delegate should run. Is this intended or a bug?
> |Is there anything else that stands out from the logs?
> You seem specifying DGROOT not in the command-line of DeleGate but in
> a parameter file. DGROOT (and OWNER) is one of parameters which cannot
> be specified in a parameter file, because it is a initial parameter used
> to find files and interpret other parameters.
> > Parameters marked with "+" can NOT be given in "+=parameters" scripts.
> > Those parameters (including DGROOT, CHROOT, LDPATH, and DYLIB) need to be
> > specified in command-line arguments or "implanted" into the executable
> > file of DeleGate with the -Fimp option.
> 9 9 Yutaka Sato <firstname.lastname@example.org> http://delegate.org/y.sato/
> ( ~ ) National Institute of Advanced Industrial Science and Technology
> _< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
> Do the more with the less -- B. Fuller