Have any experiece that fidogate have hang while it is try to export and import news from inn to fido ?
I have found out that my fidogate there before have worked fine with my news server inn now in some months has began to hang while it
trying to transport/export and reading fido<-->news works.
Have any experiece that fidogate have hang while it is try to export and
import news from inn to fido ?
As I noted elsewhere, I don't recall having issues like that. I'm
not
currently running Fidonet, though, because I'm testing another program
(MBSE BBS) on the system where I have INN running. Note that I run
v1.7 of INN, not
v2.x, as I think the v2.x versions are overkill...
I have found out that my fidogate there before have worked fine with my
news server inn now in some months has began to hang while it
"it" being Fidogate?
And btw, which version of Fidogate are you running? I had been
running an
interim development version of v4.4.11, but since there hasn't been any
development for quite awhile I've decided to use v4.4.10 plus patches
when/if I put it back online again.
trying to transport/export and reading fido<-->news works.
Sorry, Gert, it's not clear to me where you're seeing the problem...
"transport/export" is failing ?
Also; I understand from something you said elsewhere that you're
using a
new version of INN v2.x? It does make a difference in the compile of
Fidogate, IIRC, which version of INN it's being built to be used with.
(I hadn't figured a way to just make that a configuration item instead
of a compile item, in part because I'm not quite sure how it's used.)
Perhaps something changed enough in the version of INN you're now
running to make a difference to Fidogate?
program (MBSE BBS) on the system where I have INN running. Note that
I run v1.7 of INN, not v2.x, as I think the v2.x versions are
overkill...
hasn't been any development for quite awhile I've decided to use
v4.4.10 plus patches when/if I put it back online again.
trying to transport/export and reading fido<-->news works.
Sorry, Gert, it's not clear to me where you're seeing the
problem... "transport/export" is failing ?
Also; I understand from something you said elsewhere that you're
using a new version of INN v2.x? It does make a difference in the
compile of Fidogate, IIRC, which version of INN it's being built to be used with.
(I hadn't figured a way to just make that a configuration
item instead of a compile item, in part because I'm not quite sure how it's used.) Perhaps something changed enough in the version of INN
you're now running to make a difference to Fidogate?
hasn't been any development for quite awhile I've decided to use
v4.4.10 plus patches when/if I put it back online again.
so fidogate is stable ?
does it support control channel msgs for cancel msgs ?, or other nice things that a user client might do with nntp protocol :)
Also; I understand from something you said elsewhere that you're
using a new version of INN v2.x? It does make a difference in the
compile of Fidogate, IIRC, which version of INN it's being built to be
used with.
ahh, okay, that one is new for me, if inn is upgraded, one need to recompile fidogate, hard when fidogate is still not a ebuild :(
(I hadn't figured a way to just make that a configuration
item instead of a compile item, in part because I'm not quite sure how
it's used.) Perhaps something changed enough in the version of INN
you're now running to make a difference to Fidogate?
it makes sense to me that ./configure in fidogate needs as minimal includes from inn to be compiled correct
in gentoo default portage there is only 2.5.x
in gentoo default portage there is only 2.5.x
Debian as both v1.7 (as package inn) and v2.52 (as package inn2)...
Also; I understand from something you said elsewhere that you're
using a new version of INN v2.x? It does make a difference in the
compile of Fidogate, IIRC, which version of INN it's being built
to be used with.
Also; I understand from something you said elsewhere that you're
using a new version of INN v2.x? It does make a difference in the
compile of Fidogate, IIRC, which version of INN it's being built
to be used with.
You might want to check the DEFAULT_F_NEWSLIBDIR &
DEFAULT_F_NEWSSPOOLDIR
definitions for your Fidogate and compare those to your INN setup...
You might want to check the DEFAULT_F_NEWSLIBDIR & DEFAULT_F_NEWSSPOOLDIR definitions for your Fidogate and compare those to your INN setup...
Nothing shhold be have be changed in my inn.conf file as it is the one there have been used from the first time and it is too where fidogate config.make file have worked fine with before.
You might want to check the DEFAULT_F_NEWSLIBDIR &
DEFAULT_F_NEWSSPOOLDIR
definitions for your Fidogate and compare those to your INN setup...
Nothing shhold be have be changed in my inn.conf file as it is the one there have been used from the first time and it is too where fidogate config.make file have worked fine with before.
You might want to check the DEFAULT_F_NEWSLIBDIR & DEFAULT_F_NEWSSPOOLDIR
definitions for your Fidogate and compare those to your INN setup...
he may even create a ebuild :=)
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,018 |
Nodes: | 17 (0 / 17) |
Uptime: | 49:11:28 |
Calls: | 503,143 |
Calls today: | 6 |
Files: | 228,436 |
D/L today: |
55,705 files (12,239M bytes) |
Messages: | 440,281 |
Posted today: | 3 |