search for: riverwillow

Displaying 9 results from an estimated 9 matches for "riverwillow".

2013 Sep 27
1
9.2-RC4 amd64 panic: vm_page_unwire
..._syscall+0x3bf #15 0xffffffff8069a817 at Xfast_syscall+0xf7 Uptime: 6d7h46m14s Is this a known problem? Should I file a PR? What additional information should I provide? I have made the core.txt.[0-2] files available in the following directory. The directory is not browsable. http://www.riverwillow.net.au/~john/92rc4/ -- John Marshall -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20130927/b2540c66/attac...
2013 Mar 13
1
[patch] Incorrect umask in FreeBSD
...e OpenBSD's, our setusercontext() will intentionally ignore the user's own umask setting (from ~/.login.conf) unless running with the user's UID. Therefore, we need to call it again with LOGIN_SETUMASK after changing UID. PR: bin/176740 Submitted by: John Marshall <john.marshall at riverwillow.com.au> MFC after: 1 week Index: session.c =================================================================== --- session.c (revision 248230) +++ session.c (revision 248231) @@ -1533,6 +1533,12 @@ perror("unable to set user context (setuser)"); exit(1); } + + /* + * Fr...
2013 Oct 28
1
Stale NTP in FreeBSD
Apologies if this is the wrong mailing list but no list in particular seems appropriate. I was disappointed to discover in the 9.2-RC's that ntpd was still 4.2.4p8. I notice that that same (legacy) ntpd version is in stable/10 and, presumably, likely to end up in the new 10.0 release; so I thought I should speak up in the hope that it is not yet too late for the current ntpd stable release
2009 Aug 28
1
GSSAPI Authentication Broke with Dovecot 1.1.16 -> 1.2.4 Upgrade
This morning I upgraded a dovecot installation from 1.1.16 to 1.2.4 on a FreeBSD 7.2 server, and then spent 3 hours trying to figure out why GSSAPI authentication had broken. It turned out to be a recent change in Dovecot's mech-gssapi.c to do with checking for NULs in usernames: everything worked fine when I disabled that test. <http://hg.dovecot.org/dovecot-1.2/rev/5d53b1d66d1b> This
2012 Aug 23
11
FreeBSD 9.1-RC1 Available...
The first release candidate of the 9.1-RELEASE release cycle is now available on the FTP servers for amd64, i386, and powerpc64. The MD5/SHA256 checksums are at the bottom of this message. The ISO images and, for architectures that support it, the memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/9.1/ (or any of the FreeBSD mirror sites). Current
2008 Jul 09
1
Correct remedy for winbindd sulking on 3.0.30?
Greetings, I have recently upgraded from 3.0.28a to 3.0.30 on a couple of FreeBSD 7.0 servers: one in a Windows 2000 Active Directory environment, and the other in a Windows 2003 Active Directory environment, as member servers. Everything works for a while and then winbindd goes into sulking mode. Re-starting fixes everythng for a little while. I'm guessing I've hit the winbindd bug
2009 Sep 21
2
How to generate additional debug messages for sshd gssapi failures?
I'm trying to troubleshoot gssapi_with_mic authentication with OpenSSH 5.2p1 on FreeBSD 8.0. If I run sshd with maximum debug "sshd -ddd" the most detail I get is: GSSAPI MIC check failed That comes from line 282 in auth2-gss.c 279 if (!GSS_ERROR(PRIVSEP(ssh_gssapi_checkmic(gssctxt, &gssbuf, &mic)))) 280 authenticated =
2009 Jul 17
1
GSSAPI Kerberos Differences between 5.1p1 and 5.2p1?
Hello, I'm trying to find clues on what may have changed for GSSAPI (Kerberos) authentication between OpenSSH 5.1p1 and 5.2p1. We have been using GSSAPI authentication for ssh for about 18 months with no problem with the OpenSSH build that is bundled with the FreeBSD operating system. All of those machines have OpenSSH 5.1p1. Last week I upgraded one of the servers to FreeBSD 8.0-BETA1
2009 Jun 19
2
Managesieve fails to retrieve scripts > 8kB on Dovecot 1.1.16
After some help with debugging tips on #dovecot, I have established that a sieve script on Dovecot 1.1.16 has to be less than 8kB in order to be retrieved by a managesieve client. I have been using managesieve for about 6 months over as many 1.1.n versions of dovecot as have been around during that time and hit this problem when I upgraded to Dovecot 1.1.16. I have gone back to Dovecot 1.1.15