well done
- "Andrew Deason" wrote:
> On Tue, 12 Jan 2010 23:19:09 +
> Simon Wilkinson wrote:
>
> >
> > On 12 Jan 2010, at 23:12, Gary Gatling wrote:
> >
> > > Thanks a lot for all the replys. Its sounds like we don't need to
> > > be restarting afs every week since we are using a mod
On Tue, 12 Jan 2010 23:19:09 +
Simon Wilkinson wrote:
>
> On 12 Jan 2010, at 23:12, Gary Gatling wrote:
>
> > Thanks a lot for all the replys. Its sounds like we don't need to
> > be restarting afs every week since we are using a modern (1.4.11)
> > release of afs.
>
> I suspect that we
On 12 Jan 2010, at 23:12, Gary Gatling wrote:
Thanks a lot for all the replys. Its sounds like we don't need to be
restarting afs every week since we are using a modern (1.4.11)
release of afs.
I suspect that we should probably change the default bos
configuration, and the installation i
Thanks a lot for all the replys. Its sounds like we don't need to be
restarting afs every week since we are using a modern (1.4.11) release of
afs.
Cheers,
Gary Gatling | ITECS Systems
ITECS, BOX 7901 | Operations and Systems Analyst
NCSU, Raleigh, NC | Email: gsgat...@eos.ncsu.edu
27
Hi,
Interested folks are welcome to try rxk5 in its current form. Feel free to
email me or Marcus if this would be helpful to you.
Regards,
Matt
- "Russ Allbery" wrote:
> Jack Neely writes:
>
> > I'm researching upgrading our aging (1.2) Kerberos 5 infrastructure
> to
> > 1.6. I'm at
Jack Neely writes:
> I'm researching upgrading our aging (1.2) Kerberos 5 infrastructure to
> 1.6. I'm attempting to figure out how the upgrade and new encryption
> types would affect our AFS deployment. Russ's email from 2007 was
> helpful in this:
> http://www.openafs.org/pipermail/opena
Folks,
I'm researching upgrading our aging (1.2) Kerberos 5 infrastructure to
1.6. I'm attempting to figure out how the upgrade and new encryption
types would affect our AFS deployment. Russ's email from 2007 was
helpful in this:
http://www.openafs.org/pipermail/openafs-info/2007-March/0255
Hi all,
we have noticed file corruption in certain circumstances when using the
OpenAFS for Windows client in combination with antivirus products and
non-default network MTU settings.
Isolating exactly what factors _must_ be present has been a challenge, but
with tremendous help from Jeff A
On 1/12/2010 8:50 AM, Holger Rauch wrote:
> Hi,
>
> I downloaded version 1.5.68 for Win and tried to install it on a Win
> XP Professional SP3 system (32bit).
>
> The install of the required KfW 3.2.2 went smoothly and I can also use
> it for passwordless SSH logins via a PuTTY with GSSAPI suppor
On 1/12/2010 7:44 AM, Lars Schimmer wrote:
> Hi!
>
> Is anyone running Windows 7 64bit with OpenAFS 1.5.68 in a AD
> environment and has discovered malfunction of OpenAFS after
> reconfiguring the network interfaces?
>
> E.g. if I login as a domain user to win7, all works fine til I plugin a
> bl
"Karl Tißner" writes:
>> > Since it is not possible to create an user with AFS UID "0", all files
>> > created by root are not owned by root (Debian Linux, root has UID 0):
>> >
>> > # pts createuser -name testtest -id 0
>> > 0 isn't a valid user id; aborting
>> >
>> > What is the standard way
On Tue, 12 Jan 2010 08:50:32 +0100
"Karl Tißner" wrote:
> > > Since it is not possible to create an user with AFS UID "0", all
> > > files created by root are not owned by root (Debian Linux, root
> > > has UID 0):
> > >
> > > # pts createuser -name testtest -id 0
> > > 0 isn't a valid user id;
Hi,
I downloaded version 1.5.68 for Win and tried to install it on a Win
XP Professional SP3 system (32bit).
The install of the required KfW 3.2.2 went smoothly and I can also use
it for passwordless SSH logins via a PuTTY with GSSAPI support.
However, as soon as I checked the three recommended
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
Is anyone running Windows 7 64bit with OpenAFS 1.5.68 in a AD
environment and has discovered malfunction of OpenAFS after
reconfiguring the network interfaces?
E.g. if I login as a domain user to win7, all works fine til I plugin a
bluetooth stic
14 matches
Mail list logo