Hi,
I installed a test machine using
* Vanilla Linux kernel 2.6.18
* OpenAFS 1.4.2rc2 (it's the latest debian package available)
* Debian GNU/Linux Sid, latest updates
* KDE 3.5.4
Compared to kernel 2.6.17 and OpenAFS 1.4.1 I found some differences:
1. df returns unusual values for
Client OpenAFS 1.4.2 Final Candidate 4 on MacBook (Apple Intel)
works pretty stable under MacOSX 10.4.7,
both at work and at home.
Thank you, guys !
Alberto
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/lis
Carson Gaspar <[EMAIL PROTECTED]> writes:
> Almost certainly - PAM fixes abound in recent openssh versions. Things
> to try:
> - Turn off PrivSep (most likely to fix your problem)
> - Test the newly released 4.4p1
Note that privilege separation is fine provided that the PAG is created in
your se
--On Wednesday, September 27, 2006 2:25 PM -0700 Russ Allbery
<[EMAIL PROTECTED]> wrote:
Mike Dopheide <[EMAIL PROTECTED]> writes:
OpenSSH 3.9p1 or 4.2p1
Building a new version of OpenSSH for 5.8 results in an sshd that ends
up sharing AFS tokens between users.
Sounds like OpenSSH isn't
What is the current best practice to balance volumes across fileservers?
I'm aware of CMU's balance program at
ftp://ftp.andrew.cmu.edu/pub/AFS-Tools/ and Russ Albery's afs-balance at
http://www.eyrie.org/~eagle/software/afs-balance. Are there others?
Is anyone maintaining balance or has anyone
On 9/27/06, Russ Allbery <[EMAIL PROTECTED]> wrote:
Steve Devine <[EMAIL PROTECTED]> writes:
> What methods / utility's are others using to keep machines configuration
> files current?
There are about as many different methods as there are sites. Stanford is
currently in the process of deployin
Sounds like the sshd is not getting a PAG. You say you rebuilt it and it
now fails? Did you change the configure options or sshd_config options,
or did you loose the kafs lib?
I agree with the PAG theory and I think you're onto something with kafs.
That would explain why it's not working on Sol
Mike Dopheide wrote:
I don't believe this to be an OpenAFS issue, but I believe only AFS
users might have seen the symptom.
SunOS 5.8 (only)
OpenAFS 1.2.13 or Transarc
MIT Kerberos 1.3.6 or 1.4.3
OpenSSH 3.9p1 or 4.2p1
Building a new version of OpenSSH for 5.8 results in an sshd that ends
Mike Dopheide <[EMAIL PROTECTED]> writes:
> I don't believe this to be an OpenAFS issue, but I believe only AFS users
> might have seen the symptom.
> SunOS 5.8 (only)
> OpenAFS 1.2.13 or Transarc
> MIT Kerberos 1.3.6 or 1.4.3
> OpenSSH 3.9p1 or 4.2p1
> Building a new version of OpenSSH for 5.8
I don't believe this to be an OpenAFS issue, but I believe only AFS users
might have seen the symptom.
SunOS 5.8 (only)
OpenAFS 1.2.13 or Transarc
MIT Kerberos 1.3.6 or 1.4.3
OpenSSH 3.9p1 or 4.2p1
Building a new version of OpenSSH for 5.8 results in an sshd that ends up
sharing AFS tokens b
Steve Devine <[EMAIL PROTECTED]> writes:
> The package tool formally in the IBM transarc software is deprecated --
> in obsolete status.
> We have tried rebuilding it to run on Linux but so far no joy.
> We found this to be a helpful tool.
> Basically we have traditionally used it to run daily vi
The package tool formally in the IBM transarc software is deprecated --
in obsolete status.
We have tried rebuilding it to run on Linux but so far no joy.
We found this to be a helpful tool.
Basically we have traditionally used it to run daily via crontab and if
we have changed a file it get 'push
On Wed, 27 Sep 2006, Jeffrey Altman wrote:
I actually know exactly what the problem is. The 1.4.x file servers
implement a change to prevent unfriendly clients from repeatedly
requesting FetchStatus operations on the same object. The 1.4.x
Actually, all versions of OpenAFS have that protecti
Thanks.. we will look at deploying 1.5.8 then...
See-ya
Mitch
On Wed, 2006-09-27 at 12:26 -0400, Jeffrey Altman wrote:
> I actually know exactly what the problem is. The 1.4.x file servers
> implement a change to prevent unfriendly clients from repeatedly
> requesting FetchStatus operations on t
I actually know exactly what the problem is. The 1.4.x file servers
implement a change to prevent unfriendly clients from repeatedly
requesting FetchStatus operations on the same object. The 1.4.x
and earlier Windows clients do not implement the InlineBulkStatus
operation. This was first impleme
Mitchell Baker wrote:
> On Wed, 2006-09-27 at 11:07 -0400, Jeffrey Altman wrote:
>> Mitchell:
>>
>> Do you have the same issues with the 1.5.8 Windows client?
>
> Just installed on my test system and no, there is not issue there.
Good.
> Looking for the info on how to get a trace from the window
On Wed, 2006-09-27 at 11:07 -0400, Jeffrey Altman wrote:
> Mitchell:
>
> Do you have the same issues with the 1.5.8 Windows client?
Just installed on my test system and no, there is not issue there.
>
> The error messages you describe are the Windows SMB client timing
> out the connection to th
Mitchell:
Do you have the same issues with the 1.5.8 Windows client?
The error messages you describe are the Windows SMB client timing
out the connection to the AFS Client Service because the AFS client
is taking too long to respond.
1.5.8 implements a new algorithm to attempt to convince the SM
I don't know how seriously you'll take my suggestion for narrowing this problem
down, since I am a Rose-Hulman student, but as a software tester for Microsoft,
Powerway, and other companies, I do have some experience. From what I can tell
from what you sent, you have changed two variables. You h
I'm having an issue which I need some help with. Just finished
migrating all of our file servers from Solaris 8 running openafs 1.2.13
server to RHEL 4 x86_64 running 1.4.1. I have one test server running
1.4.2fc4.
Windows client used is using AFS version 1.3.8700 and same thing with
1.4.0203.
20 matches
Mail list logo
