Package Details: openafs 1.8.7-1

Git Clone URL: (read-only, click to copy)
Package Base: openafs
Description: Open source implementation of the AFS distributed file system
Upstream URL:
Licenses: custom:"IBM Public License Version 1.0"
Conflicts: openafs-features
Submitter: None
Maintainer: Bevan
Last Packager: Bevan
Votes: 61
Popularity: 0.007974
First Submitted: 2006-02-01 17:18
Last Updated: 2021-01-15 08:34

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

darkxsun commented on 2020-04-06 22:22

@dmaxter Not needed. See

Note: Packages in the AUR assume that the base-devel group is installed, i.e. they do not list the group's members as build dependencies explicitly.

dmaxter commented on 2020-04-06 21:31

Missing dependencies: automake and autoconf

drslmr commented on 2017-11-24 14:02

Hi, I had some issue concerning ypbind together with logging into my afs account where I have my home directory under afs. See
In the above communication there was one workaround suggested to give the appropriate privileges to the login process, which works for me. But the better option would be to use nscd or sssd instead of yp.
Does anyone have any experience using nscd or sssd with logging into an afs account?

drslmr commented on 2017-11-06 13:06

Unfortunately I could not find out what exactly caused my recent issue. But from a former snapshot of my installation that did not have the issue it was possible to upgrade to today's state. And now the issue is gone.

drslmr commented on 2017-11-04 09:50

Bevan, thanks a lot for your effort. I'm sorry for taking your time.
On a different machine I did update openafs and linux to 4.13.11-1-ARCH and I can not reproduce the problem. Too, on my ill machine I can still use an older snapshot of an complete arch installation without the reported issue. So I guess something went wrong during upgrading. I remember that at some point during post installation hook my disk ran out of space. I think it was due to openafs-modules-dkms. I removed parts of /var/vache and tried to reinstall every package again. But still something is wrong. It's my problem.

Thanks again.

Bevan commented on 2017-11-03 14:05

drslmr: This sounds more like an issue with your AFS cell to me. If it's not, I guess it would be an upstream bug as I don't think we touch any code that's relevant for that.

Can you try to debug this with your cell provider? I did a small test in a local test cell and it worked as expected with kernel 4.13.10-1-ARCH and the current openafs packages:

1. Created a user for an IP range:
2. Created a group containing this user named localnet
3. Set ACLs for a folder to only allow access by group localnet
4. Within this directory I created another folder only accessible for my authenticated user

Without a token I could access the folder from step 3 from my local network and after obtaining a token I could also enter the folder from step 4.

One thing that does not work is giving the IP-based user (i.e. permissions via ACLs. This is on purpose and documented in

drslmr commented on 2017-11-03 09:59

Since last linux and openafs upgrade I can't access my directories anymore.
In the directory tree I can see directories only down to a certain level.
As soon as there is an additional IP based access right required I don't
see the directories anymore. This IP based access right seams to require that
the hosts IP address belongs to a certain set of IP sub-nets. I have no clue how that works. But it seams to not work anymore now.

kgizdov commented on 2017-10-24 21:00

latest version compiles for me fine.

totsilence commented on 2017-10-24 10:32

I prepared a patch and submitted it here as an OpenAFS bug:

I guess they will move the patch to gerrit if they agree with it. The patch solves the linking issue for me.

Bevan commented on 2017-10-23 17:23

Good catch! So it is caused by the latest ncurses update:

Searching the web for "ncurses with-termlib=tinfo" shows that this is/was an issue for other software packages as well. I guess the configure logic needs to be extended for again.

I won't have time to look into this today. If you come up with a patch we can directly send it upstream for review.