Displaying 20 results from an estimated 25 matches for "dundas".
Did you mean:
dudas
2003 Apr 16
4
post last sendmail upgrade
I've noticed email corruption post the last upgrade to sendmail
committed to stable. Is anyone else experiencing this?
Mark
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@isc.org
2008 Mar 18
0
Walds Z in a mixed model
...1 -21.92
71 GiI01BS01 outerislands Gil 1 -17.17
72 GiI01BS02 outerislands Gil 1 -18.21
73 GiI01BS05 outerislands Gil 1 -16.54
74 GiI01BS04 outerislands Gil 1 -17.47
75 GiI01BS03 outerislands Gil 1 -19.01
76 DuI03BS01 outerislands Dundas 3 -15.07
77 DuI03BS02 outerislands Dundas 3 -15.42
78 BaI03BS02 outerislands Banks 3 -18.50
2009 Jan 26
2
FreeBSD-7.1STABLE w/BIND-9.4.3-P1 start problem
Hello,
I have been using FreeBSD-7.0STABLE with BIND-9.4.2 ( i guess, forget to check before upgrade) up to 2008-01-26 (yesterday).
But after upgrade FreeBSD-7.0STABLE-->FreeBSD-7.1STABLE everything goes wrong.
1.BIND can't start anymore and giving me following message at /var/log/messages:
.
.
.
Jan 27 12:30:20 ns kernel: ad4: 152587MB <WDC WD1600AAJS-75PSA0 05.06H05> at
2009 Mar 17
3
rndc: connect failed: 127.0.0.1#953: connection refused
My BIND9.6.0 on FreeBSD 6.2 works fine when I manually start with:
root@ns2# named -4 -S 1024 -c /etc/namedb/named.conf
But it won't start on boot and no error messages or log. And it won't start using rndc, it cause error message. Why does the error shows port 953 when I specified for port 53 in the config?
rndc: connect failed: 127.0.0.1#953: connection refused
Below are
2008 Jun 26
1
6to4 suddenly stopped working to 2001: addresses
I've got three installations of FreeBSD using 6to4 in three different
physical locations, attached to three different ISPs. Sometime in the last
few days all of them have stopped talking to IPv6 addesse which are
not also 6to4. I can still talk to 2002: addresses, but not to 2001:
addresses.
This all worked fine a few days ago, and nothing has changed in the config of
any of these machines. I
2013 Jan 15
0
[LLVMdev] IMPORTANT: Change of release tarball. Yes, again.
...or the noise.
Mark
> --=20
> Wei-Ren Chen (=E9=99=B3=E9=9F=8B=E4=BB=BB)
> Computer Systems Lab, Institute of Information Science,
> Academia Sinica, Taiwan (R.O.C.)
> Tel:886-2-2788-3799 #1667
> Homepage: http://people.cs.nctu.edu.tw/~chenwj
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: marka at isc.org
2013 Jan 14
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
...platform before you cut the final release. I understand that
feeling. I don't know how many times I've cut a release to only
find that BIND doesn't build in a particular build environment
despite using build farm and doing release candidates.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: marka at isc.org
2013 Jan 14
0
[LLVMdev] IMPORTANT: Change of release tarball. Yes, again.
...Mathematics and Mechanics, Saint Petersburg State University
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: marka at isc.org
2009 Jan 24
4
BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device not configured, where 199.7.83.42 is RANDOM IP address
Hello, Freebsd-stable.
BIND on my new router (7.1-STABLE, BIND 9.4.3-P1) shows bunch of
errors on every start and doesn't answer on requests for 30-60 seconds
after that. Errors are like this:
Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1567: unexpected error:
Jan 24 12:18:12 gateway named[1455]: internal_send: 193.0.14.129#53:
2013 Jan 14
3
[LLVMdev] IMPORTANT: Change of release tarball. Yes, again.
> I'm confused. Does the release tarball now match RELEASE_32/final or
> not? If not, that's a problem for those of us who count on the
> repository matching the actual release.
>
> At the very least they should match so we can check out the release at
> some point in the future.
They should match now
--
With best regards, Anton Korobeynikov
Faculty of Mathematics and
2013 Jan 17
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
...subset
so there should not be an issue to get the feedback.
And here I think lies a problem for any LLVMRM. It is an old
lesson re-learned yet again, do not try to wear too many hats
and get the community involved in the release.
>
> Mark
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742 INTERNET: marka at isc.org
Thank you for taking time to write this message, reading it helped
restore some sanity in a way that winking smileys didn't seem to.
Paweł
2008 Feb 29
4
7.0 - slow/unstable Internet access via Linux router
Hello,
recently I've installed 7.0 and now I'm observing strange thing with my Internet connection.
Access to some sites may be VERY slow or doesn't work at all with different kinds of timeout
messages or without messages at all (but other sites works fine). For example, firefox may say
"Transferring data from..." message and then "The connection to the server was reset
2013 Jan 15
2
[LLVMdev] IMPORTANT: Change of release tarball. Yes, again.
On Tue, Jan 15, 2013 at 09:25:42AM +1100, Mark Andrews wrote:
>
> While the sizes now match the SHA256 checksum do not match the original
> compressed tarballs.
>
> /usr/ports/devel/llvm # sha256 /usr/ports/distfiles/llvm-3.2.src.tar.gz
> SHA256 (/usr/ports/distfiles/llvm-3.2.src.tar.gz) = 265109c71b4fab8dc12ced314955921695c1ef549719553b0bc1e325110e143e
> root at
2003 Apr 30
1
IPv6 Resolver (or: Slow rendering of Webpages using Konqueror)
Hi,
<new_listmember_intro>
Name: Melvyn Sopacua
Occupation: WebMaster
Age: 32
Location: Netherlands
</new_listmember_intro>
after quite some digging, the user experience mentioned in brackets above,
turned out to be ipv6 resolving problems. They only occur with certain
hosts, one of them being the adserver company my employer uses, 'DoubleClick'.
What is frustrating about
2009 Jan 26
2
FreeBSD-7.1STABLE w/BIND-9.4.3-P1 start problem followup
Installed using pkd_add or ports BIND-9.6.0-P1 working fine.
1.But seems can't run under chroot well:
----------------------------------------------------------
Jan 27 13:54:08 ns named[36447]: starting BIND 9.6.0-P1 -c named.conf -t /var/named -u bind
Jan 27 13:54:08 ns named[36447]: built with '--localstatedir=/var' '--disable-linux-caps'
2006 Apr 05
2
bind() fd 6, family 28, port 123 at boot time
Hi, looking at the messages i see errors with ntp everytime i reboot my
server:
shiva2# tail /var/log/messages
Apr 5 15:32:46 shiva2 kernel: Trying to mount root from ufs:/dev/da0s1a
Apr 5 15:32:46 shiva2 ntpd[385]: ntpd 4.2.0-a Tue Mar 14 04:43:54 UTC
2006 (1)
Apr 5 15:32:46 shiva2 ntpd[385]: bind() fd 6, family 28, port 123, addr
fe80:1::20b:cdff:fe42:3d63, in6_is_addr_multicast=0 flags=0
2013 Oct 01
1
sonewconn: pcb 0xfffffe00c7223498: Listen queue overflow
Hello,
I updated our main server to 9.2-STABLE today and afterwards I noticed a
bunch of these messages, does anyone know what they mean? I was unable
to find anything on this error message. Things appear to be working OK
so far.
Sep 30 22:08:56 illidan kernel: sonewconn: pcb 0xfffffe00c7223498:
Listen queue overflow: 193 already in queue awaiting acceptance
Sep 30 22:12:27 illidan kernel:
2007 Feb 09
1
FreeBSD Security Advisory FreeBSD-SA-07:02.bind
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
=============================================================================
FreeBSD-SA-07:02.bind Security Advisory
The FreeBSD Project
Topic: Multiple Denial of Service vulnerabilities in named(8)
Category: contrib
Module: bind
2008 Jul 16
3
named.conf: query-source address
Hi!
I fully understand and second efforts on educating people
how to configure BIND to be stong to attacks and keep them from using
"query-source address" with "port" option but how about
binding named to particular IP address when host has many of them?
Using "query-source address" without "port" is the only solution
(not speaking of jails here) and safe
2004 Apr 07
5
Changing `security@freebsd.org' alias
Hello Folks,
The official email address for this list is
`freebsd-security@freebsd.org'. Due to convention, there is an email
alias for this list: security@freebsd.org, just as there is for
hackers@ & freebsd-hackers@, arch@ & freebsd-arch@, and so on.
The security@freebsd.org alias has been the source of occassional
problems. Several times in the past, postings have been made to