Author: Davina Treiber <Treiber AT HOTPOP DOT COM>
Date: Mon, 14 Jul 2003 08:04:50 +0100
I don't think this is a generally held opinion. Most people regard 6.1.3 as the most stable and least buggy release of NetWorker yet, and definitely better than 6.1.1. Many bugs from 6.1.1 are now f
Author: Yura Pismerov <ypismerov AT TUCOWS DOT COM>
Date: Mon, 14 Jul 2003 08:26:13 -0400
I'm curious if the behavior is different if the nscd is down. It would be great if somebody who experiencing this problem could test it. -- Yuri Pismerov, Sr. System Administrator, TUCOWS.COM INC. (4
Author: George Sinclair <George.Sinclair AT NOAA DOT GOV>
Date: Mon, 14 Jul 2003 10:26:27 -0400
Well, I guess I stand corrected. Didn't mean to raise any red flags, but it seemed like for a while there that everyone and there brother was complaining about 7 or 6.1.3 or some such thing and havin
Author: Kent Holloway <Kent.Holloway AT ONVOY DOT COM>
Date: Mon, 14 Jul 2003 13:46:11 -0500
I don't run nscd on our Solaris 8 Networker server and we continue to see the problem. -- Note: To sign off this list, send a "signoff networker" command via email to listserv AT listmail.temple DOT
Author: "Mark Bradshaw (BTOpenWorld)" <notthehoople AT BTOPENWORLD DOT COM>
Date: Tue, 15 Jul 2003 21:12:14 +0100
I've seen this problem on a Solaris 8 server which had a slightly broken DNS setup which didn't look, at first glance, to be broken at all! Basically what the problem was was that there were multiple
Author: Yura Pismerov <ypismerov AT TUCOWS DOT COM>
Date: Wed, 16 Jul 2003 13:53:55 -0400
As I already mentioned (and Davina explained) nslookup results has nothing (well, almost nothing) to do with what other application gets for DNS lookups. The thing is, nslookup queries DNS servers di