search for: dalvis

...'/etc/named.conf' Nov 25 14:16:03 unitedinfotechs named[2201]: using default UDP/IPv4 port range: [1024, 65535] Nov 25 14:16:03 unitedinfotechs named[2201]: using default UDP/IPv6 port range: [1024, 65535] I shall highly appreciate any hint. -- Best Regards Tariq Ismail Dalvi http://www.dalvis.net tariq at dalvis.net

...the update completed my system can receive emails but cannot send and cannot browse get error domain not found, besides ftping is working fine web servers are working fine how can i fix this or roll back to my previous configuration of system. Thank you Best Regards Tariq Ismail Dalvi http://www.dalvis.in tariqdalvis at gmail.com tariq at dalvis.net

Hello guys I am having problem of pop3 with my mail server I am using postfix-2.3.3 and Dovecot v1.0.7 when i telnet localhost or xyz.net i get following output [root at dalvis ~]# telnet mail.xyz.net 110 Trying 192.168.12.14... Connected to mail.xyz.net (192.168.12.14). Escape character is '^]'. +OK Dovecot ready. user johne at xyz.net +OK pass 768tidzx -ERR Authentication failed. Connection closed by foreign host. and my maillog shows Jun 21 19:25:20 localhost...

Hello to all, I am having a web server mail server Mysql and name server on single machine my os is CentOs 5.2 and desktop gnome everything was working fine now couple of days back I was using text editor, Fire Fox and GIMP at a time and my mouse started to act funny as well as very slow even my keyboard curser moves very slow I feel it is some sort of memory problem but I have noticed the

CentOS 4.8, BIND 9.2.4 Hi All: I have a rather annoying problem with rndc which I have not been able to resolve despite much searching and many attempts to correct. When making changes to our DNS entries I have tried to use the following procedures: 1. Flush the cache buffers: rndc flush 2. Stop named: rndc stop 3. Delete the journal files: rm *.jnl 4. Edit the forward and/or

Hi, I am trying to run samba with bind_dlz (bind-9.9.1 - P1) on a multi-homed network. I have configured the setup as per Samba4 Howto. But when I try to do "samba_dnsupdate --all-names" it fails with error: dns_tkey_negotiategss: TKEY is unacceptable The kerberos ticket being used by samba_dnsupdate shows follwoing principals: klist -c /tmp/tmp6cxfgY Ticket cache: FILE:/tmp/tmp6cxfgY

flight 17325 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17325/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl 9 guest-start fail REGR. vs. 12557 test-amd64-i386-xl-credit2 15 guest-stop fail REGR. vs. 12557 test-amd64-i386-xl 15 guest-stop

flight 17454 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17454/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as allowable (not blocking): test-amd64-i386-qemut-rhel6hvm-amd 7 redhat-install fail

flight 17612 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17612/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as allowable (not blocking): test-amd64-i386-rhel6hvm-intel 9 guest-start.2 fail

flight 17901 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17901/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-qemuu-rhel6hvm-intel 4 xen-install fail REGR. vs. 12557 test-amd64-i386-pv 4 xen-install fail REGR. vs. 12557 test-amd64-amd64-pv 4

flight 17916 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17916/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-pv 4 xen-install fail REGR. vs. 12557 test-amd64-amd64-xl 4 xen-install fail REGR. vs. 12557 test-amd64-amd64-xl-win7-amd64 4

flight 18150 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18150/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12557 test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as

flight 18181 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18181/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12557 test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as

flight 18805 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18805/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12557 test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as

flight 18844 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18844/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386 4 xen-build fail REGR. vs. 12557 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-pcipt-intel 9 guest-start fail

I think the 6month period comes from the "tombstoneLifetime" attribute present under this DN. The default is 180 days. dn: CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration, BASEDN Can this value be reduced and wait for samba to purge the old deleted objects? Modifying this value has other implications as per AD docs but I wonder if it can be changed for a simple directory