It seems to be time to try kicking this beast again. I removed the old install, started from scratch, and seem to have ended up in the same place. I don't believe it actually has any y2k date issues, logging at least shows a 4 digit year space, and it shows the right year not some wacked 19 prefix on the 20x year.

It goes through the motions, gives no errors, but doesn't process anything. Despite with the docs say, its like its looking in the wrong place for the files in transit. It could conceivably be an addressing problem bbs sits at 66:666/666 and is exporting to 66:666/667 so it should pick up packets to
that destination and mangle them into uucp packets.

Perhaps I shoould just archive the installation and see if I can get a fresh set of eyes to look it over, maybe I've got something backwards...

Spec


--- SuperBBS v1.17-3 (Eval)
* Origin: A camel is a horse, designed by a committee! (21:3/101)

It seems to be time to try kicking this beast again. I removed the old install,
started from scratch, and seem to have ended up in the same place. I don't believe it actually has any y2k date issues, logging at least shows a 4 digit year space, and it shows the right year not some wacked 19 prefix on the 20x year.

It goes through the motions, gives no errors, but doesn't process anything. Despite with the docs say, its like its looking in the wrong place for the files in transit. It could conceivably be an addressing problem bbs sits at 66:666/666 and is exporting to 66:666/667 so it should pick up packets to that destination and mangle them into uucp packets.

Perhaps I shoould just archive the installation and see if I can get a fresh set of eyes to look it over, maybe I've got something backwards...

Spec


--- SuperBBS v1.17-3 (Eval)
* Origin: A camel is a horse, designed by a committee! (21:3/101)

It seems to be time to try kicking this beast again. I removed the old install,
started from scratch, and seem to have ended up in the same place. I don't believe it actually has any y2k date issues, logging at least shows a 4 digit year space, and it shows the right year not some wacked 19 prefix on the 20x year.

It goes through the motions, gives no errors, but doesn't process anything. Despite with the docs say, its like its looking in the wrong place for the files in transit. It could conceivably be an addressing problem bbs sits at 66:666/666 and is exporting to 66:666/667 so it should pick up packets to that destination and mangle them into uucp packets.

Perhaps I shoould just archive the installation and see if I can get a fresh set of eyes to look it over, maybe I've got something backwards...

Spec


--- SuperBBS v1.17-3 (Eval)
* Origin: A camel is a horse, designed by a committee! (21:3/101)