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

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-04-08 08:26:29 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-04-08 08:26:29 - FreeBSD freebsd-stable.sentex.ca 8.2-STABLE FreeBSD 8.2-STABLE #4: Wed Sep 28 13:48:49 UTC 2011 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-04-08 08:26:29 - starting RELENG_9 tinderbox run for sparc64/sparc64 TB --- 2012-04-08 08:26:29 - cleaning the

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

Okay, I started over from scratch with my samba server rebuild, but I am still getting some weird issues. Here are my config files of importance: --------------/etc/samba/smb.conf-------------------- # Samba Configuration File [global] workgroup = WAYNE realm = WAYNE.LOCAL server string = Samba Server security = ADS password server =

Hi, I've a problem, with a cpu load (>66% while running a separate virusscanner with another 30%) of one of my smbd processes. It only happens occasionally (approx. 2 times in the last 4 weeks). The backtrace is attached. It seems to me, that smbd is looking for colorlaser5quota. This printer isn't attached anymore to the server and neither cups nor samba configuration files include a

Hello, I'm having trouble when I try do get a group SID from my domain, the user lookup and authentication is working fine. Actually what I'm trying to do is to authenticate squid against MS AD using winbind. I need to restrict access by group, so I'm using wbinfo_group.pl to do it. The machine has been built to be a proxy server only. I'm using Suse Linux 9.3 Professional

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-07:07.bind Security Advisory The FreeBSD Project Topic: Predictable query ids in named(8) Category: contrib Module: bind Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-07:07.bind Security Advisory The FreeBSD Project Topic: Predictable query ids in named(8) Category: contrib Module: bind Announced:

Hi All I am using the samba 3.0.14a RPMs installed on SuSE 9.2. I have a PDC running on one machine, using tdbsam as a backend - this has been running fine for months. I am not trying to set up a standalone server in another office, which should authenticate with the PDC using winbind, as per the "The 500-User office" chapter of samba by example :

The configuration I'm trying to use is a SAMBA PDC with a SAMBA Member Server, using tdbsam. Binaries for SuSE 9.3 from the samba web page, version 3.0.14a-4.1.i586.rpm. This is SuSE 9.3 Pro with patches and kernel up-to-date thru 20050708. I need to use Samba 3.0.14a because in production the Samba PDC will have to work with several Samba member servers and 3 Windows 2003 member servers.

http://bugzilla.mindrot.org/show_bug.cgi?id=613 Summary: sshd hanging Product: Portable OpenSSH Version: 3.6.1p2 Platform: ix86 OS/Version: Linux Status: NEW Severity: critical Priority: P2 Component: PAM support AssignedTo: openssh-bugs at mindrot.org ReportedBy: airwin at inf.bme.hu On

> On Tue, Jun 10, 2008 at 4:50 PM, Robert Grapes > <robert_grapes at hotmail.com> wrote: > > llvm[3]: Compiling SelectionDAGISel.cpp for Release build > > > > /var/folders/Xq/XqzGACxLHWq4Af0cQbEMdE+++TI/-Tmp-//cc6xGQcn.s:unknown:immediate > > value (-288) too large > > > > Any help would be really appreciated, > > That looks like an internal