Please remember to reply to the mailing list, not the original sender: http://gnudip2.sourceforge.net/#mailinglist
+++++++++ I just realized that I did not respond to the mailing list for this. === I also have to wonder what in hell happened to the header and trailer that is supposed to be added to messages from the list!!!! The header is supposed remind me of the need for this. I just checked the setup of the list, and it is still supposed to be there. I have to be blunt. I have just about had all I can take of SourceForge - grand schemes with no follow through. That they provide free hardware and bandwidth is great. But their crappy software environment is a big problem. I see that the FSF has decided to give up trying to use the SourceForge software for their savanna site: http://savannah.gnu.org/forum/forum.php?forum_id=195 I also can't help noticing that other VA Linux hosted sites such as http://www.geocrawler.com/ and http://www.mail-archive.com/ have had (or are having) massive mail backlog problems. VA Linux should not make promises it is not able to keep. === Moving the mailing list from cheapnet.net may have been a big mistake!! I don't feel like moving it again. === What would be nice is to have a way to address the functionality of the mailing list using software that only requires support for web pages (including Perl CGI) and a shell account (for crond). Then an open source developer could move their support site to another site easily, and just auto redirect from the old one. If the project had its own domain name, it would not even need to redirect!! It would be completely portable to any site that supports virtual hosting, which will certainly be all of them. The problem is how to receive postings sent by E-mail. This requires mail filters and/or privileged system access. Sending mail from web page code does not require special access. So if posts had to be done through a web page, with mail then being sent to the mailing list members, this could probably be done. And the mailing list archive could be built in. === Maybe my next project should be a patch to mailman or majordomo (2) to adapt it to this mode of operation? I already have a front-end on the web page so I can log web site access. This allows me to detect problems and assess its effectiveness. SourceForge does not provide this. Perhaps the project could grow to a complete package that would provide everything a small open source project needs, while allowing the project to avoid becoming dependant on a particular site? === Is anyone else interested? -------- Original Message -------- Subject: Re: [GnuDIP] invalid signature error - BIND Mailing List Date: Sat, 10 Nov 2001 11:58:21 -0700 From: Creighton MacDonnell <[EMAIL PROTECTED]> To: "Julia A. Case" <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> "Julia A. Case" wrote: > > After trying several times and updating bind to the newest release I > still get invalid signature errors when I tro to do an update with > nsupdate... What could be the cause of this? The bind documentation > says it can happen if the clocks are out of sync, but since it's the > same machine I doubt that is the trouble. Without any information, it is pretty hard to speculate. What error messages are you getting for example (both nsupdate output and log messages from named)? === You may also want to consider using the BIND mailing list, since there are many knowledagable BIND people (including the authors) on those lists: http://isc.org/services/public/lists/bind-lists.html http://www.isc.org/ml-archives/ If you test the BIND configuration using nsupdate from the command line, without involving GnuDIP, then the BIND mailing list may be the best place to resolve problems. -- Creighton MacDonnell http://macdonnell.ca/ -- GnuDIP Mailing List http://gnudip2.sourceforge.net/#mailinglist
