Re: [DA][Fwd] LDAPS support (and some more stuff)

> I've (tried) to make a short README.BRANCH and a TODO.BRANCH, the readme
> file tries to explain what I've done. The TODO mentions a
> "happens-at-random" bug, I think I have fixed it by adding a "sleep(1);"
> before a "fclose(fd);"

This is hackish dude! =)

Try running under valgrind to discover mem corruption issues.  I also
had an account of someone who told me DA failed with a specific GCC
compiler version and -O3 or -O2... Now I cannot remember what it was.

Or perhaps valgrind grinds DA to an unbearably slow state, which masks
the bug.

AFAICR, DA is not using threads.  I don't think it's even using gtk's
mainloop integration for async fd operations.

(which reminds me, has anyone ported this to gtk2?  gtk1 it is beginning
to look a little dated, and it pulls extra mostly unnecessary and old
deps into distros)

>  - though, I just suspect that somehow fixed it
> (haven't had any freezes since I added that line).
> I would like to force everyone that even thinks about compiling this
> version to read the README.BRANCH, especially the "Misc" section, where
> it mentions something about the config file format-backwards
> compabillity beeing breaked with this branch.

Can the cfg file compat be preserved?
The second best option would be to program a migration algo.

> 
> Any comments or questions are welcome. I belive that this branch is not
> yet "production stable/ready", since it's not been fully tested and
> since it breaks backwards compabillity with the configuration file
> "~/.directory_administrator/profile".

these profile routines are the dumbest dumbest ever routines I have ever
written.  Not to mention that this was what I think my first program in
C was.  Of course I found glib and gtk great and easy to use, but
finally grew up and now I'm sold to pygtk.

> Also, I'd really like to hear your comments on the debug macros (and the
> add of --enable-debug which defines DEBUG so we can do things like
> "#ifdef DEBUG", the DBG_PRINT and DBG_PRINT_DM are only printing debug
> data when DEBUG is defined, thus when configure was run with
> --enable-debug). And I've not done any specific tests with --disable-ldaps.
> 
> oh, I just remembered, I've not added my self to the CREDITS file...

by all means, do!

> 
> Now, you can try to compile it if you trust me. (this is the "test"
> mentioned in the second sentace - haven't we all done the test where the
> first line reads "care fully read all instructions before starting the
> test", and after 5 mintues people start erasing their answers as the
> final line reads "only fill in question number 1 before handing the test
> in" :)
> btw, did I mention that this branch breaks the
> ~/.directory_administrator/profile with a changed format for this file?
> 
> Best Regards
> Fredrik (aka scientica)
> 
> p.s. Mike Jackson, I'm sorry to bother/cc you, I just wonder if this
> e-mail really end up in the diradmin-dev list (could you please e-mail
> me either way and tell me?). TIA
> 
> --
> After all, if you are in school to study computer science, then a
> professor saying:
>  "use this proprietary software to learn computer science" is the
> same as English professor handing you a copy of Shakespeare
> and saying:
>  "use this book to learn Shakespeare without opening the book itself."
>   -- Bradley Kuhn
> 
> 
> 
> 
> 
-- 
                Rudd-O          <[email protected]>
                http://www.amautacorp.com/staff/Rudd-O/