dear all,
recently, i added another afs file server into our environment.
somehow, my users have problems after i added the new afs file server.
as long as they they log in from lock screen, they will have the
*permission denied* problem. what i found is before the screen saver
triggered. they
sorry to bother you. now, it is fixed by restoring the previous
kerberos backup. however, i still don't know what is the correct
procedure to add another afs file server with afs key?
thank you all.
best, sam
On Fri, Mar 18, 2011 at 4:41 PM, TIARA System Man
sys...@tiara.sinica.edu.tw wrote:
On 18 Mar 2011, at 10:27, TIARA System Man wrote:
sorry to bother you. now, it is fixed by restoring the previous
kerberos backup. however, i still don't know what is the correct
procedure to add another afs file server with afs key?
You have to have the same afs key on every file and
Hi,
Is it possible to open files read-only when another process has a
write-lock? I found the following information regarding 1.5.20.
http://dl.openafs.org/dl/openafs/1.5.20/winxp/relnotes.htm
Many applications on Windows (e.g. Microsoft Office) require
the use of byte range locks
Hi Thomas,
Mandatory enforcement is the defined behavior for byte-range locks on Windows.
Since you are testing on Windows, you are seeing the Windows behavior. The
same lock would be interpreted as advisory on a Unix client.
Matt
- Thomas Smith theitsm...@gmail.com wrote:
Hi,
Is
Hi everyone,
I had a server doing a cache scan for over an hour yesterday after
upgrading the RAID (mpt2sas) driver on RHEL5.5 64bit. I thought the box
hung, so I ran a hard reset and ended up rebuilding it. I'm trying to
reproduce and measure the cache scan time with the two different
/etc/init.d/openafs-client stop; rm /usr/vice/etc/CacheItems;
/etc/init.d/openafs-client start
?
On Fri, Mar 18, 2011 at 10:05 AM, Edgecombe, Jason jwedg...@uncc.eduwrote:
Hi everyone,
I had a server doing a cache scan for over an hour yesterday after
upgrading the RAID (mpt2sas) driver
On 3/18/2011 9:29 AM, Thomas Smith wrote:
Hi,
Is it possible to open files read-only when another process has a
write-lock? I found the following information regarding 1.5.20.
http://dl.openafs.org/dl/openafs/1.5.20/winxp/relnotes.htm
The release notes for the version of the OpenAFS
On 3/18/2011 9:48 AM, Matt W. Benjamin wrote:
Hi Thomas,
Mandatory enforcement is the defined behavior for byte-range locks on
Windows. Since you are testing on Windows, you are seeing the Windows
behavior. The same lock would be interpreted as advisory on a Unix client.
Matt
While
On Fri, Mar 18, 2011 at 7:55 AM, Jeffrey Altman
jalt...@secure-endpoints.com wrote:
We are all looking forward to the day that the byte-range lock
implementation you have been working on can be merged into the tree.
Is there an estimate as to when this may occur?
On 3/18/2011 12:20 PM, Thomas Smith wrote:
On Fri, Mar 18, 2011 at 7:55 AM, Jeffrey Altman
jalt...@secure-endpoints.com wrote:
We are all looking forward to the day that the byte-range lock
implementation you have been working on can be merged into the tree.
Is there an estimate as to when
Hi,
don't wether this fits here or not, but since I don't have this issue in
non-afs environments I guess it does.
I've got a working Debian/Ubuntu setup with OpenLDAP, MIT Kerberos5 and
OpenAFS. Upon login to one machine, an SSH agent is startet and my key
is added (via keychain). I also get
Never seen this before. Related to dafileserver? I'm getting this in
FileLog after a server crash and restart:
Fri Mar 18 16:00:01 2011 FSYNC_com_VolOff: failed to get heavyweight reference
to volume 536871132 (state=20, flags=0x18)
Fri Mar 18 16:02:00 2011 FSYNC_com_VolOff: failed to get
On Fri, 18 Mar 2011 16:10:36 -0500
Ryan C. Underwood nemesis-li...@icequake.net wrote:
Never seen this before. Related to dafileserver? I'm getting this in
FileLog after a server crash and restart:
Fri Mar 18 16:00:01 2011 FSYNC_com_VolOff: failed to get heavyweight
reference to volume
Hi folks,
My site uses OpenAFS and MIT Kerberos with OpenLDAP for user meta data
(all running on Debian squeeze). Is it possible to prevent users from
logging in more than once, or at least to prevent them from starting
up the same desktop environment on multiple hosts with the same
On Fri, Mar 18, 2011 at 04:28:18PM -0500, Andrew Deason wrote:
Sorry, this is an issue that was fixed on master and we missed the 1.6
pullup. This patch should fix it:
http://git.openafs.org/?p=openafs.git;a=commitdiff_plain;h=4ae82fdc4d67cce9abdf57ce830a5378adc3c442
Yes, that seems to have
hitting bugs is good!
Derrick
On Mar 18, 2011, at 8:33 PM, Ryan C. Underwood nemesis-li...@icequake.net
wrote:
On Fri, Mar 18, 2011 at 04:28:18PM -0500, Andrew Deason wrote:
Sorry, this is an issue that was fixed on master and we missed the 1.6
pullup. This patch should fix it:
Thanks. I got things squared away. I ran mke2fs -j once on my cache
partition to make the scan faster on boot.
On 03/18/2011 10:44 AM, Derrick Brashear wrote:
/etc/init.d/openafs-client stop; rm /usr/vice/etc/CacheItems;
/etc/init.d/openafs-client start
?
On Fri, Mar 18, 2011 at 10:05 AM,
18 matches
Mail list logo
