similar to: [releng_9 tinderbox] failure on sparc64/sparc64

TB --- 2008-06-03 09:06:24 - tinderbox 2.3 running on freebsd-legacy.sentex.ca TB --- 2008-06-03 09:06:24 - starting RELENG_6 tinderbox run for sparc64/sparc64 TB --- 2008-06-03 09:06:24 - cleaning the object tree TB --- 2008-06-03 09:06:55 - cvsupping the source tree TB --- 2008-06-03 09:06:55 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/sparc64/sparc64/supfile TB ---

TB --- 2008-06-03 08:42:30 - tinderbox 2.3 running on freebsd-legacy.sentex.ca TB --- 2008-06-03 08:42:30 - starting RELENG_6 tinderbox run for i386/i386 TB --- 2008-06-03 08:42:30 - cleaning the object tree TB --- 2008-06-03 08:43:09 - cvsupping the source tree TB --- 2008-06-03 08:43:09 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/i386/i386/supfile TB --- 2008-06-03 08:43:22

TB --- 2012-12-11 03:57:29 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-12-11 03:57:29 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa at freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-12-11 03:57:29 - starting RELENG_9 tinderbox run for i386/i386 TB --- 2012-12-11 03:57:29 - cleaning the

Hi, I'm having lots of difficulties with BCM5719, which is the default network card of HP Proliant DL 360 G8 servers. I can get a few ping replies before I get a couple of these: bge0: watchdog timeout -- resetting bge0: watchdog timeout -- resetting Then everything hangs. Can not log in using ssh.

TB --- 2013-02-26 21:23:55 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-02-26 21:23:55 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa at freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-02-26 21:23:55 - starting RELENG_9 tinderbox run for arm/arm TB --- 2013-02-26 21:23:55 - cleaning the

On 2 September 2016 at 14:51, Rowland Penny via samba <samba at lists.samba.org > wrote: > > > As I said, I know very little about freebsd, but you should be aware > that Samba only supports the last three major versions i.e. at the > moment 4.2.X, 4.3.x and 4.4.x > They are supported in three ways, the oldest version (now 4.2.x) only > gets security fixes, the middle

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

I have a system running rsync in daemon mode, the version information: > rsync --version rsync version 2.6.8 protocol version 29 On another system I have: > authoritative# rsync --version rsync version 3.0.7 protocol version 30 I have the following problem when trying to fetch files from the system running the old daemon: # /usr/local/bin/rsync --protocol=29 -vvvvvvvv

Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- drivers/gpu/drm/nouveau/core/core/handle.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/core/core/handle.c b/drivers/gpu/drm/nouveau/core/core/handle.c index b8d2cbf..264c2b3 100644 --- a/drivers/gpu/drm/nouveau/core/core/handle.c +++

Hi All, I'm trying to integrate Samba 4 DHCPD and Bind 9.9 into a complete solution. I'm using the BIND/Samba 4 DLZ plugin. DHCP by itself works and hands out IP addresses. What I would like to have happen is the following: - PC is joined to the Samba 4 domain (this works) - PC gets an IP via DHCPD - DHCP or the PC registers the IP in BIND Network PC's should resolve cleanly when

Hi, Samba team! I am trying to install samba4 on FreeBSD 9.2 as a domain DC to join an existing samba4 domain controller on FreeBSD 9.2. I followed the instruction of: Samba4/HOWTO/Join a domain as a DC Everything is OK until I run the following command: root at mtm:/var/named/etc/namedb # samba-tool drs showrepl Default-First-Site-Name\MTM DSA Options: 0x00000001 DSA object GUID:

I've made some changes to the 2.9p2 release code to add support for using DNSSEC lookups to check host keys. I've also made the changes to the OPENBSD_2_9 tree. Both patches are available at ftp://ftp.tislabs.com/pub/fmeshd/ as openssh.[portable,openbsd].patch.20010709 I'm really looking for testers at this time. Right now the lookups are done using a getrrsetbyname() function that is

Matthias Busch schrieb am 12.03.2015 16:43: > I am hesitant to use .net (the domain I own) in fear of having dns > issues. i do not control the NS for the internet accesible .net domain > either. At least w.r.t. the Bind backend this fear is not necessary. It is indeed exactly what I do. The AD-DNS is only authoritative to "domain.samdom.com", not to

The rpc service in samba seems to stop during replication -> > [2015/09/30 12:18:41.774189, 0] ../source3/rpc_server/svcctl/srv_svcctl_nt.c:326(_svcctl_OpenServiceW) > > Or may be the Internal Dns that does not connect to the Windows DNS. See below > On Sep 30, 2015, at 4:32 PM, Cesar DiMartino <cesardimartino at gmail.com> wrote: > > Here are the logs from my las

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

Hi When I install bind8 through ports it doesn't create the dir named 'namedb' and the needed files that it's supposed to do according to the handbook. Has anyother experienced this?

zone "local.thisismycompany.com" { type slave; masters { *your DCs go here* }; file "/etc/bind/namedb/bak.local.thisismycompany.com"; forwarders{}; }; If you are setting up bind on the DC like that, you have a problem, you are not using DLZ. Rowland

Hi puppetiers, recently I switched to using Mongrel webserver in effort to get rid of those annoying "end of file reached" errors and increase performance. It did the trick beautifully, but now a lot of my reports are plagued by another error message: --- err: Could not call fileserver.describe: #<Errno::EPERM: Operation not permitted - connect(2)>

(Hi, I tried sending this to ess-bugs, but got it bounced back: "user unknown". Hope this isn't too off-topic for ess-help. Scot) I'm using Xemacs 21.4, ess 5.1.24, on Windows 98 SE, with John Fox's configuration files: (http://socserv.mcmaster.ca/jfox/Books/Companion/ESS/index.html) and am getting the end-of-loop-timeout warning message I've seen reported to

Hi I'm currently testing the replacement of a samba 3 with LDAP backend with a samba 4 ad-dc. For this, I have a fresh install of: - FreeBSD 10.2 - samba 4.3.3 - bind with dlopen-support: IND 9.10.3-P3 <id:bdaecad> built by make with '--localstatedir=/var' '--disable-linux-caps' '--with-dlopen=yes' '--disable-symtable'