Andrew and Derrick thank you for replying so quick. I've been fighting with my
AFS/NFS translator to get you some messages when the server is inaccessible,
but so far everything I tried it isn't logging anything besides the reboots and
other various messages that don't seem to apply. In the
Andrew thanks again for any help you can give me. I will find the debuginfo
package and get those installed. I think you are right the machine is freezing
so maybe that is why I'm not seeing anything useful in the messages file. I'm
using 1.5.77 and know from past experiences there were issues
I would like some help with the AFS/NFS Translator. We have an AFS/NFS
translator server running OpenAFS 1.5.77 on SLES 11 no SP. This translator is
an guest in an VMware environment.
When the translator server is rebooted the translator clients can cause the
translator server to be
I don't think the translator code gets built by default, and your
error suggests it's not compiled in. Try removing or commenting out
the line that defines AFS_NONFSTRANS in src/config/param.linux26.h and
rebuilding.
Thanks Marc that did the trick. Now to make sure it works like our production
The changes in the kernel that makes us unable to build the NFS
translator appeared in 2.6.29. So I would guess that SLES 11 (no SP)
would work (2.6.27), but that SLES 11 SP1 (2.6.32), OpenSUSE 11.3
(2.6.34) or anything newer would not.
Marc
I tried with SLES 11 (no SP) and still get the same
To
11/23/2010 04:51 PM Karen Eldredge
karen.eldre...@infoprint.com
Thank you so much. I will give it a try with the kernel level you suggested.
_
This message and any attachments are solely for the intended recipient and may
contain confidential or privileged information. If you are
I've compiled OpenAFS 1.5.77 on OpenSuSE 11.3 and added the these lines in
afs.rc:
/sbin/modprobe sunrpc $MODLOADDIR/libafs.map 21
authtab=`awk '/[ \t]authtab[ \t]/ {print $1}' /proc/kallsyms`
/sbin/insmod $MODLOADDIR/$LIBAFS ${authtab:+authtab_addr=0x$authtab}
$MODLOADDIR/libafs.map
I
We recently just updated the pam-krb5 supplied by Russ Allbery from 3.10 to
3.15 and since the update we are not able to ssh as root. Has anyone seen this
behavior before? Here are the contents of /var/log/messages. It should be
ignoring root, but from this log it seems to be failing at
Sorry I hadn't gotten a chance to reply to your message on this. I
believe you're running into this problem documented in the README:
Not a problem. I know you are extremely busy, and I saw other replies to
openafs.org, so I thought that is the route I should take.
Here are our common PAM
We have a OpenAFS Windows client and the user on that system was not able to
access one directory even though the ACLs showed he has access permission. The
user was able to access this directory from another AFS client, so I believe
that this is an client issue. Since it was just one AFS
We moved both the aklog and aklog_dynamic_auth to /usr/vice/etc, and we use
LDAP as the backend.
Our methods file looks like this:
LDAP:
program = /usr/lib/security/LDAP
program_64 =/usr/lib/security/LDAP64
KRB5:
program = /usr/lib/security/KRB5
program_64 =
Thanks for all your help. With the patch from Carsten and Simon I have
successfully compiled and started AFS.
_
This message and any attachments are solely for the intended recipient and may
contain confidential or
This should be fixed in the openafs code - the right fix would
probably be to add a configure check for the availability of
do_signal, and define out the probing code if it's not available,
similar to what was done for init_mm.
I haven't had luck with changing the SuSE kernel yet, so if you
Could you give me the small modification to the SuSE kernel source code?
_
This message and any attachments are solely for the intended recipient and may
contain confidential or privileged information. If you are not
I compiled OpenAFS 1.4.10 on ppc running OpenSuSE 11.1. Everything seemed to
compile fine, but when I try to start afs I get this message in
/var/log/messages:
kernel: libafs: Unknown symbol do_signal
Any help will be appreciated. Thanks!
What kernel version is that? 2.6.27.21-0.1
How are your feelings about that? Do you think trying the compile with
OpenSuSE 10.3 will work? Instead of making changes to the kernel source.
_
This message and any
17 matches
Mail list logo
