AW: [OpenAFS] OpenLDAP an Berkleydb

[Schmidt, Mario]

Hi,
im Sorry, false List. Please ignore it.

Mario Schmidt

> -----Urspr=FCngliche Nachricht-----
> Von: Schmidt, Mario [mailto:Mario.Schmidt@Dresdner-Bank.com]
> Gesendet: Mittwoch, 15. Januar 2003 15:28
> An: openafs-info@openafs.org
> Betreff: [OpenAFS] OpenLDAP an Berkleydb
>=20
>=20
> Hi,
> as i have seen the new Berkeley DB Database Versions have a=20
> feature to share
> the databases over machines. My first thought was: Cool we=20
> can throw away
> slurpd and all LDAP Servers can write to the database: Not=20
> only the Master !
>=20
> My question: Has anybody tried such a configuration ? Is it possible =
?
>=20
> Thank you in advance
>=20
> Mario Schmidt
> MiS@, Dresdner Bank ( Externer Mitarbeiter )
> Tel: 069/263-84043
> Email: Mario.Schmidt@dresdner-bank.com
> --
> Es ist nie zu spaet eine glueckliche Kindheit zu haben.
> Its never to late to have a lucky childhood.
>=20
>=20
> > -----Ursprungliche Nachricht-----
> > Von: Jack Neely [mailto:slack@quackmaster.net]
> > Gesendet: Mittwoch, 15. Januar 2003 15:22
> > An: openafs-info@openafs.org
> > Betreff: [OpenAFS] Has anyone seen this problems with sysnames?
> >=20
> >=20
> > Folks,
> >=20
> > I posted this to openafs-devel and didn't get a=20
> responce...maybe that
> > was the wrong place for this.  Anyway, I'm seeing a strange=20
> > problem when
> > I use a sysname list and I was wondering if anyone out there=20
> > can confirm
> > this.
> >=20
> > Thanks!
> > Jack Neely
> >=20
> > ----- Forwarded message from Jack Neely=20
> <slack@quackmaster.net> -----
> >=20
> > From: Jack Neely <slack@quackmaster.net>
> > To: openafs-devel@openafs.org
> > Subject: [OpenAFS-devel] 1.2.8 sysname list bug
> > Date: Mon, 13 Jan 2003 15:28:13 -0500
> >=20
> > Hi,
> >=20
> > Wondering if anyone else has seen this behavior.  I'm working on
> > configuring OpenAFS 1.2.8 (the client) for use with RHL8.0 and I've
> > created a sysname list to deal with binary compatiblity=20
> > between 8.0 and
> > our older 7.x binaries in AFS.  So I set the sysname to
> >=20
> >     fs sysname ia32_redhat80 -newsys ia32_redhat8x -newsys=20
> > i386_linux24
> >=20
> > While someone else was building new binaries they found that=20
> > they could
> > not cd into a directory sysmlink that ended in @sys (like=20
> > build -> .build/@sys)
> > but he could cd into the symlink bin -> .install/@sys/bin. =20
> So I did a
> > test case:
> >=20
> > I created:
> >=20
> > [slack@anduril slack]$ ls -R .hide
> > .hide:
> > i386_linux24  ia32_redhat8x
> >=20
> > .hide/i386_linux24:
> > i386_linux24
> >=20
> > .hide/ia32_redhat8x:
> > ia32_redhat8x
> >=20
> > And did a:
> >=20
> > [slack@anduril slack]$ ln -s .hide/@sys sysname
> >=20
> > Then I tried:
> >=20
> > [slack@anduril slack]$ ls sysname/
> > ia32_redhat8x
> > [slack@anduril slack]$ cd sysname/
> > [slack@anduril sysname]$ ls
> > ls: .: Stale NFS file handle
> >=20
> > I did the same thing after setting the sysname to simply=20
> > 'ia32_redhat8x'
> > and it works as you'd expect.  When I delete the=20
> > ia32_redhat8x directory
> > I get the same stale NFS file handle but the first ls does show
> > i386_linux24.
> >=20
> > I've seen this with my RHL8.0 client against an RHL7.3=20
> server running
> > 1.2.7 and Transarc AFS 3.6 running on solaris.
> >=20
> > Clues?
> >=20
> > Jack Neely
> >=20
> > --=20
> > Jack Neely <slack@quackmaster.net>
> > Linux Realm Kit Administration and Development=20
> > PAMS Computer Operations at NC State University
> > GPG Fingerprint: 1917 5AC1 E828 9337 7AA4  EA6B 213B 765F 3B6A 5B89
> > _______________________________________________
> > OpenAFS-devel mailing list
> > OpenAFS-devel@openafs.org
> > https://lists.openafs.org/mailman/listinfo/openafs-devel
> >=20
> >=20
> > ----- End forwarded message -----
> >=20
> > --=20
> > Jack Neely <slack@quackmaster.net>
> > Linux Realm Kit Administration and Development=20
> > PAMS Computer Operations at NC State University
> > GPG Fingerprint: 1917 5AC1 E828 9337 7AA4  EA6B 213B 765F 3B6A 5B89
> > _______________________________________________
> > OpenAFS-info mailing list
> > OpenAFS-info@openafs.org
> > https://lists.openafs.org/mailman/listinfo/openafs-info
> >=20
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>=20