䤠瑲楥搠瑯湳瑡汬灥湦猠潮⁆敤潲愠䍯牥‴⁷楴栠瑨攠灲潶楤敤⁒偍猬畴੩琠獥浭敳浰潳獩扬攠慳潮朠慳⁴桥灥湡晳敲湥氠景爠瑨攠捵牲敮琠晣㐠੫敲湥氠癥牳楯渠⠲⸶⸱㐭ㄮㄶ㌷彆䌴⤠楳潴癡楬慢汥⸊䉹⁴桥⁷慹Ⱐ䤠汯潫敤潲⁹畭数潳楴潲礠桡癩湧灥湡晳Ⱐ睩瑨潵琠獵捣敳献
䥳⁴桥牥湥㼠䥦潴Ⱐ楴⁷潵汤攠湩捥⁴漠楮獴慬氠潮攠慴灥湡晳牧⸊⡉浡杩湥⁴桡琠楴❳潴⁴潯畣栠睯牫Ⱐ潮捥⁴桥灭猠慲攠慬牥慤礠瑨敲攩ਊ捨敥牳Ⰺⴭ
偩敲牥⁆牥湫楥氠†††攭浡楬㨠灩敲牥牥湫楥汀慰挮畮楶⵰慲楳㜮晲ੁ獴牯偡牴楣畬攠整⁃潳浯汯杩攠†䍯汬攠摥⁆牡湣
Hi,
Carmi Weinzweig [EMAIL PROTECTED] writes:
Derek -
I installed the SRPM, and built it, but even though it shows:
+ : @
+ : @@@
+ : @@@ kernel version: 2.6.11-1.1369_FC4
+ : @@@ base kernel version:2.6.11-1.1369_FC4
+ :
[EMAIL PROTECTED] writes:
I tried to install openfs on Fedora Core 4 with the provided RPMs, but
it semmes impossible as long as the openafs-kernel for the current fc4
kernel version (2.6.14-1.1637_FC4) is not available.
I don't rebuild the kernel modules every time a new kernel is
released.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Douglas E. Engert wrote:
Anything to do with the username being more then 8 characters?
Do other uses on the same machine have the problem?
Its a notebook and just for one user.
I tested it right now with another userID.
First with user admin, the
Lars Schimmer wrote:
aklog: unable to obtain tokens for cell cgv.tugraz.at (status: 11862788).
This is a pioctl() error. Do any of the other commands that invoke
pioctl() operations work?
tokens
fs getserverpref
fs checkserver
...
smime.p7s
Description: S/MIME Cryptographic
That looks like either an old aklog or no cache manager running.
11862788 (ktc).4 = a pioctl failed
What's ktrace tell you? (No, we don't need thewhole output, just the
failure)
Derrick
On Thu, 1 Dec 2005, Lars Schimmer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
One of
Its a notebook and just for one user.
I tested it right now with another userID.
First with user admin, the same error.
aklog -d told me he tries to get a token for ID 1, but then there was
the same error.
As my user, schimmer, I got the same error, to.
aklog: unable to obtain tokens for cell
On Thu, 1 Dec 2005, Ken Hornstein wrote:
Ewww. Is it possible that somehow you're running the wrong aklog?
(I sure wish translate_et was shipped by default).
/Library/OpenAFS/Tools/bin/translate_et 11862788
11862788 (ktc).4 = a pioctl failed
*cough*
Derrick
The OpenAFS Gatekeepers announce the availability of OpenAFS version
1.4.1 Release Candidate 2. Source files and available binaries can be
accessed via the web at:
http://www.openafs.org/dl/openafs/candidate/1.4.1-rc1/
^^^
Shouldn't
A user of our AFS cell uses both UNIX/Linux and Windows clients (1.3.71)
On UNIX/Linux sistems he has created a large amount of files having a colon
character : in the file name.
He can read these files from the AFS Windows client but he is unable to create
new files with colons in the file
On Thu, 1 Dec 2005, Ken Hornstein wrote:
Ewww. Is it possible that somehow you're running the wrong aklog?
(I sure wish translate_et was shipped by default).
/Library/OpenAFS/Tools/bin/translate_et 11862788
Well, what do you know. I didn't even know that path existed. Is that
written down
On Thu, 1 Dec 2005, Ken Hornstein wrote:
The OpenAFS Gatekeepers announce the availability of OpenAFS version
1.4.1 Release Candidate 2. Source files and available binaries can be
accessed via the web at:
http://www.openafs.org/dl/openafs/candidate/1.4.1-rc1/
On Thu, 1 Dec 2005, Giovanni Bracco wrote:
A user of our AFS cell uses both UNIX/Linux and Windows clients (1.3.71)
Then they are a great fool. Please please please upgrade the Windows
client.
He can read these files from the AFS Windows client but he is unable to create
new files with
On Thu, 1 Dec 2005, Ken Hornstein wrote:
On Thu, 1 Dec 2005, Ken Hornstein wrote:
Ewww. Is it possible that somehow you're running the wrong aklog?
(I sure wish translate_et was shipped by default).
/Library/OpenAFS/Tools/bin/translate_et 11862788
Well, what do you know. I didn't even
There is no solution. : is an illegal character on Windows for a
file name. Although the file system obviously supports it, the Win32
APIs will not allow a file with such a name to be created.
Jeffrey Altman
Giovanni Bracco wrote:
A user of our AFS cell uses both UNIX/Linux and Windows
since file locking is 'just around the corner' for openafs (at least
I'm hopeful) the question I have now is will (is) there be a way to
ask the server who has a particular file open. the afs server has to
keep track of which client has a file open in order to force the cache
manager to do its
fyi ...
---BeginMessage---
-BEGIN PGP SIGNED MESSAGE-
The MIT Kerberos Development Team is proud to announce a public beta
of the next major revision of our Kerberos for Windows product,
Version 3.0.
Version 3.0 provides several often requested new features:
* thread-safe Kerberos 5
Hi,
On Thu, Dec 01, 2005 at 10:20:22AM -0500, Derrick J Brashear wrote:
That looks like either an old aklog or no cache manager running.
11862788 (ktc).4 = a pioctl failed
What's ktrace tell you? (No, we don't need thewhole output, just the
failure)
I've got the same problem so I post
I've got the same problem so I post my ktrace-dump:
616 aklogCALL poll(0x14,0,0x800c5603)
616 aklogRET poll -1 errno 22 Invalid argument
616 aklogCALL write(0x2,0x32550,0x5e)
616 aklogGIO fd 2 wrote 94 bytes
aklog: unable to obtain tokens for cell
I grabbed the 1.4.1-rc2 src.tar and doc.tar files.
I installed the 1.4.0 src.rpm, replaced the src.tar and doc.tar files in
/usr/src/redhad/SOURCE with the 1.4.1-rc2 files, updated the
SPEC/openafs.spec file to call them and compiled.
The compile went fine, however I'm getting the following
file locking is not just around the corner... It has always been
there, and has always worked fine... If you're meaning byte range
partial file locking, then yes, that is in the current release
candidate for windows only, and is purely client side.
At best, you could determine who has callbacks
Hi all,
I'm running into some strange behaviour, and I'm hoping
someone may have already come up with a solution.
We are running a bunch of 32 bit Centos 3.5 and 3.6 machines,
and using pam_krb5afs.so with the tokens option in the PAM
system-auth file for authentication and
Dj Merrill [EMAIL PROTECTED] writes:
We are running a bunch of 32 bit Centos 3.5 and 3.6 machines,
and using pam_krb5afs.so with the tokens option in the PAM
system-auth file for authentication and getting AFS tokens upon login.
It seems to be working fine with 32 bit Intel and AMD
Hi,
On Thu, Dec 01, 2005 at 12:38:35PM -0500, Ken Hornstein wrote:
I've got the same problem so I post my ktrace-dump:
616 aklogCALL poll(0x14,0,0x800c5603)
616 aklogRET poll -1 errno 22 Invalid argument
616 aklogCALL write(0x2,0x32550,0x5e)
616 aklogGIO
Wondering if it would be possible to build 1.4.1 Release Candidate 2
without support on the server side for Windows byte range locking?
Why would you want to do this?
It appears that various non Windows locking related issues are getting
addressed within 1.4.1 such as:
- A bug in callback
Would it be worth considering having byte range lock support in the
code, but enabled with a flag or option of some sort so that code could
be staged in without fully implementing it?
i.e. similar to fs setcrypt?
I don't know if the impact described below is legitimate or not, but
having it in
This particular problem was caused by using the wrong compiler and has
been resolved.
However, the aklog segfault reported under 1.4.0 is still here:
The last few lines of an strace aklog show:
read(3, ee.washington.edu\t#Nikola\n128.2..., 4096) = 4096
read(3, ysics, university Mainz,
- A bug in callback handling for readonly volumes in the Unix clients
has been fixed.
which wasn't a bug in 1.4.0
- MacOS 10.3 support has been updated.
also not a bug in 1.4.0
- Several MacOS 10.4 issues have been addressed.
10.4 wasn't going to be in 1.4.0
But it is not
On Thu, 1 Dec 2005, Lee Damon wrote:
This particular problem was caused by using the wrong compiler and has been
resolved.
However, the aklog segfault reported under 1.4.0 is still here:
The last few lines of an strace aklog show:
+++ killed by SIGSEGV +++
Process 3539 detached
How about
Should be in ticket #23845 if I did it right.
nomad
Derrick J Brashear wrote:
On Thu, 1 Dec 2005, Lee Damon wrote:
This particular problem was caused by using the wrong compiler and has
been resolved.
However, the aklog segfault reported under 1.4.0 is still here:
The last few lines of an
On Thu, 1 Dec 2005, Neulinger, Nathan wrote:
Would it be worth considering having byte range lock support in the
code, but enabled with a flag or option of some sort so that code could
be staged in without fully implementing it?
i.e. similar to fs setcrypt?
That would be a suitable.
I
Terry McCoy wrote:
On Thu, 1 Dec 2005, Neulinger, Nathan wrote:
Would it be worth considering having byte range lock support in the
code, but enabled with a flag or option of some sort so that code could
be staged in without fully implementing it?
i.e. similar to fs setcrypt?
That would be
Quoting Sergio Gelato [EMAIL PROTECTED]:
* Turbo Fredriksson [2004-10-29 18:44:51 +0200]:
I'm about to upgrade my production machine, and unfortunately
I can't test the upgrade before I do...
I just don't have the resources (time and money for new test
machines)
If you don't even have
Me
tedc
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
PS 1.4 stable, your e-mail is not clear.
tedc
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
35 matches
Mail list logo
