[OpenAFS] OpenLDAP an Berkleydb

[Schmidt, Mario]

Hi,
as i have seen the new Berkeley DB Database Versions have a feature to share
the databases over machines. My first thought was: Cool we can throw away
slurpd and all LDAP Servers can write to the database: Not only the Master !

My question: Has anybody tried such a configuration ? Is it possible ?

Thank you in advance

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.


> -----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?
> 
> 
> Folks,
> 
> I posted this to openafs-devel and didn't get a responce...maybe that
> was the wrong place for this.  Anyway, I'm seeing a strange 
> problem when
> I use a sysname list and I was wondering if anyone out there 
> can confirm
> this.
> 
> Thanks!
> Jack Neely
> 
> ----- Forwarded message from Jack Neely <slack@quackmaster.net> -----
> 
> 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
> 
> Hi,
> 
> 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 
> between 8.0 and
> our older 7.x binaries in AFS.  So I set the sysname to
> 
>     fs sysname ia32_redhat80 -newsys ia32_redhat8x -newsys 
> i386_linux24
> 
> While someone else was building new binaries they found that 
> they could
> not cd into a directory sysmlink that ended in @sys (like 
> build -> .build/@sys)
> but he could cd into the symlink bin -> .install/@sys/bin.  So I did a
> test case:
> 
> I created:
> 
> [slack@anduril slack]$ ls -R .hide
> .hide:
> i386_linux24  ia32_redhat8x
> 
> .hide/i386_linux24:
> i386_linux24
> 
> .hide/ia32_redhat8x:
> ia32_redhat8x
> 
> And did a:
> 
> [slack@anduril slack]$ ln -s .hide/@sys sysname
> 
> Then I tried:
> 
> [slack@anduril slack]$ ls sysname/
> ia32_redhat8x
> [slack@anduril slack]$ cd sysname/
> [slack@anduril sysname]$ ls
> ls: .: Stale NFS file handle
> 
> I did the same thing after setting the sysname to simply 
> 'ia32_redhat8x'
> and it works as you'd expect.  When I delete the 
> ia32_redhat8x directory
> I get the same stale NFS file handle but the first ls does show
> i386_linux24.
> 
> I've seen this with my RHL8.0 client against an RHL7.3 server running
> 1.2.7 and Transarc AFS 3.6 running on solaris.
> 
> Clues?
> 
> Jack Neely
> 
> -- 
> Jack Neely <slack@quackmaster.net>
> Linux Realm Kit Administration and Development 
> 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
> 
> 
> ----- End forwarded message -----
> 
> -- 
> Jack Neely <slack@quackmaster.net>
> Linux Realm Kit Administration and Development 
> 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
>