Frank Burkhardt wrote:
Hi,
On Fri, Jan 25, 2008 at 11:01:52AM +0100, Anders Magnusson wrote:
Hi,
I have just encountered a non-working behavior of group membership, and I cannot see what I'm
doing wrong.
Environment: Redhat, OpenAFS 1.4.5 on both server and client.
I have an user:
%
Hi,
I have just encountered a non-working behavior of group membership, and
I cannot see what I'm doing wrong.
Environment: Redhat, OpenAFS 1.4.5 on both server and client.
I have an user:
% pts examine afs-backup
Name: afs-backup, id: 99942, owner: system:administrators, creator:
Hi,
On Fri, Jan 25, 2008 at 11:01:52AM +0100, Anders Magnusson wrote:
Hi,
I have just encountered a non-working behavior of group membership, and I
cannot see what I'm
doing wrong.
Environment: Redhat, OpenAFS 1.4.5 on both server and client.
I have an user:
% pts examine
Hi all, if anyone has any ideas about this, please let me know.
* OpenAFS 1.4.4 on Red Hat Enterprise Linux Server release 5
* SSHD without privsep
* User gets in but has no tokens
authrequired pam_env.so
authsufficient/lib/security/pam_afs.so.1 ignore_root
Regardless, there are. I wouldn't try something over 20gb.
We are not quite there yet, ftp.stacken.kth.se Solaris 10 on old
Compaq x86:
# /usr/afs/*/fs getcac
AFS using 14963631 of the cache's available 1600 1K byte blocks.
afsd -stat 62500 -daemons 27 -volumes 250 -afsdb -dcache 62500 -c
2) From the documentation, it looks like the replication mechanism is
single-master / multiple-slaves, i.e. one read-write server, multiple
read-only servers. Is that correct?
Yes
If so, do clients transparently handle
this? Are writes transparently routed to the read-write server while
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25 Jan 2008, at 16:54, Jeff Blaine wrote:
I do have to admit though that I have no idea what keyring
based PAGs means.
AFS typically provides session based PAGs. These allow you to
seperate your AFS credentials into compartments that are
On 25 Jan 2008, at 16:19, Jeff Blaine wrote:
Hi all, if anyone has any ideas about this, please let me know.
* OpenAFS 1.4.4 on Red Hat Enterprise Linux Server release 5
* SSHD without privsep
* User gets in but has no tokens
See my talk from last years best practices workshop - http://
Frank Burkhardt wrote:
Hi,
On Fri, Jan 25, 2008 at 12:39:18PM +0100, Anders Magnusson wrote:
Hi,
I'll continue to spam the list with other odd things that I notice :-)
Environment: Redhat 4.3, OpenAFS 1.4.5 on both server and client.
find does not seems to cross AFS mountpoint
find does not seems to cross AFS mountpoint boundaries.
I suppose you mean GNU find.
-noleaf
Do not optimize by assuming that directories contain 2 fewer
subdirectories than their hard link count. This option is
needed when searching
Hi,
I've looked through the documentation, but couldn't find any specifics on
this, so I'd be grateful if somebody could point me at the page I've
missed.
1) How do OpenAFS clients pick a server to access a volume from if the
volume is replicated on multiple servers?
2) From the
That worked - thanks Simon!
I do have to admit though that I have no idea what keyring
based PAGs means. That's a little lower level than my
knowledge goes. Any chance you have a explanation short
enough that it's reasonable to type out? I'd like to
understand what else I may have affected by
On 25 Jan 2008, at 16:36, Jeff Blaine wrote:
ChallengeResponseAuthentication is set to no
Any other ideas?
What's in your session stack - do you have a call to pam_keyinit.so?
If you're using keyring based PAGs, then pam_keyinit will remove the
key created by AFS to hold your PAG when it
ChallengeResponseAuthentication is set to no
Any other ideas?
Simon Wilkinson wrote:
On 25 Jan 2008, at 16:19, Jeff Blaine wrote:
Hi all, if anyone has any ideas about this, please let me know.
* OpenAFS 1.4.4 on Red Hat Enterprise Linux Server release 5
* SSHD without privsep
* User gets
[EMAIL PROTECTED] wrote:
I see, so replicated volumes are static, rather than constantly catching
up?
Currently, AFS support read-only replication but not read-write replication.
A .readonly volume is paired to a read-write volume. The vos release
command will copy the current contents of
Russ Allbery wrote:
John Tang Boyland [EMAIL PROTECTED] writes:
] It looks like you're not running pam_krb5 in the session stack. pam_krb5
] should be listed in the session stack before pam_afs_session, and that
] will probably fix the problem.
(BTW: This is Sun-provided pam_krb5)
Ah,
16 matches
Mail list logo