Any clues?
linux v 4.1.15-8
afs v 1.6.17
heimdal 1.6.99 (master)
carps
gcc -O -I/data/openafs-1.6.17/src/config -I/data/openafs-1.6.17/include -I.
-I. -D_LARGEFILE64_SOURCE -o ptserver ptserver.o ptutils.o ptprocs.o
ptint.ss.o ptint.xdr.o utils.o map.o /data/openafs-1.6.17/lib/libubik.a
/
Am 14.03.2016 um 14:24 schrieb Chas Williams:
> Then you should have permission to read root.cell. Did you add admin
> to the system:administrators group? Do the pts commands work?
>
> While poking around I found this gentoo document which seems to
> cover what you want:
>
> https://wiki.gentoo
On 5/3/2016 11:02 AM, Steve Gaarder wrote:
> Yes, of course we do that. My question is whether there is also a way
> to say that some volumes cannot be accessed from outside our network
> regardless of credentials. Would it work to put all those volumes on a
> server with a firewall that blocks a
We have a bunch of old linux-from-scratch systems which we're rolling out
the door and aren't going to be getting AFS upgrades. RHEL5 is the
next-oldest, about 15% of dropping fast and we're currently discussing what
to do w/r/t afs on them. Everything else with AFS is pretty recent.
The conversio
hi，
ktpass -princ afs/pc@pc.com -mapuser
t...@pc.com -mapOp add -out afs.keytab +rndPass
-crypto DES-CBC-CRC +DesOnly -ptype KRB5_NT_PRINCIPAL
+DumpSalt
i use the ktpass command to create afs.keytab on windows ad and then copy the
afs.keytab file to the openafs server,after that
hi,
sorry,i need to add something .
i have three servers.
ad +kerberos win2008
nis server openafs server linux redhat 6.7
nis slave openafs client linux redhat 6.7
i can use the ad accounts to login the linux server and can get tokens.but the
pam configuration with pam_krb5 seems not wor
hi,
i modified the /etc/pam.d/system-auth file ,but it did not work,how can i debug
this error?Are there any other files that need to be modified?
root@test-afs002 cai]# vi /etc/pam.d/system-auth
#%PAM-1.0
# This file is auto-generated.
# User changes will be destroyed the next time authconfig is
Yes, of course we do that. My question is whether there is also a way to
say that some volumes cannot be accessed from outside our network
regardless of credentials. Would it work to put all those volumes on a
server with a firewall that blocks access?
Steve Gaarder
System Administrator, Dep
