Hello all,
We are running a handful of servers on various 32 bit freebsd releases and
those are running great.
For our new server we decided on the 64bit version of freebsd (8.2), but things
are not going very well.
Bosserver dumps core on all bos requests I tried so far, for the last couple
Hello list,
From the documentation, available at
http://docs.openafs.org/ReleaseNotesWindows/ch03s06.html, one can read:
(...) For example, if the Windows username is jaltman and the default
cell is athena.mit.edu, then Integrated Logon can be successfully used
if the windows password
See appendix A.2.1 for details on specifying per logon domain configuration
including the authentication realm.
Sent from my iPad
On Apr 1, 2011, at 9:27 AM, Hugo Monteiro hugo.monte...@fct.unl.pt wrote:
Hello list,
From the documentation, available at
On 04/01/2011 07:04 PM, Jeffrey Altman wrote:
See appendix A.2.1 for details on specifying per logon domain
configuration including the authentication realm.
Hi Jeffrey,
Actually that's where I started. I was trying to give access to two
different cells using the same krb realm.
Kerberos
On Fri, 1 Apr 2011 08:56:35 -0400
Derrick Brashear sha...@gmail.com wrote:
you're almost certainly better off for FreeBSD using 1.6.0pre4.
It would still be nice to know what's going on here, if possible.
Mark, do you not see anything in BosLog (or BosLog.old, etc) when this
happens? There
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 27.03.2011 01:42, schrieb Russ Allbery:
Dirk Heinrichs dirk.heinri...@altum.de writes:
No. They're both installed as K02* in /etc/rc6.d (default). So I guess
it's up to the init system how to order them.
In the openafs-client init script,
Dirk Heinrichs dirk.heinri...@altum.de writes:
Am 27.03.2011 01:42, schrieb Russ Allbery:
In the openafs-client init script, add openafs-fileserver to the end of
the Should-Start configuration line in the header and add a Should-Stop
line like:
# Should-Stop: openafs-fileserver
Thank you for information. I tried to use memory cache and it was only
a bit faster than using disk cache, the limiting factor being apparently
fileserver consuming available CPU system time on networking. Using
-jumbo helped somewhat, but observing the facts that limited memory
cache means more
