[Fedora-directory-devel] Announcing Fedora Directory Server 1.0.2

[Rich Megginson]

Fedora Directory Server 1.0.2 is released!  This release contains new
features, new platform support, and many bug fixes.

* Extended Password Syntax checking - passwords can be checked to see if
they conform to the following:
** minimum password character length (old feature, but now the default
is 8 characters)
** minimum number of digit characters (0-9)
** minimum number of ASCII alpha characters (a-z, A-Z)
** minimum number of uppercase ASCII alpha characters (A-Z)
** minimum number of lowercase ASCII alpha characters (a-z)
** minimum number of special ASCII characters (!@#$, etc.)
** minimum number of 8-bit characters
** maximum number of times the same char can be immediately repeated
(aaabbb)
** minimum number of character categories that are represented
(categories are lower, upper, digit, special, and 8-bit)
** Screenshot - http://directory.fedora.redhat.com/wiki/Image:Pwdsyntax.png

* Support for Linux x86_64 - RPMs for Fedora Core 4 and Fedora 
Core3/RHEL4 x86_64 are
on the Download page.

* Preliminary support for Fedora Core 5 - including support for Apache
2.2 and native java

* Bug fixes - follow this link
(https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=183369) to see the
bugzilla report

Release Notes: http://directory.fedora.redhat.com/wiki/Release_Notes
Download: http://directory.fedora.redhat.com/wiki/Download
Home Page: http://directory.fedora.redhat.com/wiki/Main_Page

[Fedora-directory-devel] Re: [Fedora-directory-announce] Announcing Fedora Directory Server 1.0.2

[Felipe Alfaro Solana]

> Preliminary support for Fedora Core 5 - including support for Apache
>
> 2.2 and native java

What RPM should I install on FC5T3? I did install
http://directory.fedora.redhat.com/download/fedora-ds-1.0.2-1.FC4.i386.opt.r....
However, during installation, the Admin Server fails to start:

httpd.worker: Syntax error on line 151 of
/opt/fedora-ds/admin-serv/config/httpd.conf: Cannot load
/opt/fedora-ds/bin/admin/lib/libmodrestartd.so into server:
/opt/fedora-ds/bin/admin/lib/libmodrestartd.so: undefined symbol:
apr_filename_of_pathname

What did I do wrong?

[Fedora-directory-devel] Re: [Fedora-directory-announce] Announcing Fedora Directory Server 1.0.2

[Rich Megginson]

Felipe Alfaro Solana wrote:
> > Preliminary support for Fedora Core 5 - including support for Apache
> >
> > 2.2 and native java
>
> What RPM should I install on FC5T3?

There are no RPMs (yet) for FC5.  Instead, you'll have to build it from 
source.  See http://directory.fedora.redhat.com/wiki/Building#One-Step_Build
> I did install
> http://directory.fedora.redhat.com/download/fedora-ds-1.0.2-1.FC4.i386.opt.r....
> However, during installation, the Admin Server fails to start:
>
> httpd.worker: Syntax error on line 151 of
> /opt/fedora-ds/admin-serv/config/httpd.conf: Cannot load
> /opt/fedora-ds/bin/admin/lib/libmodrestartd.so into server:
> /opt/fedora-ds/bin/admin/lib/libmodrestartd.so: undefined symbol:
> apr_filename_of_pathname
>
> What did I do wrong?
>
> --
> Fedora-directory-devel mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-directory-devel

[Fedora-directory-devel] Re: [Fedora-directory-announce] Announcing Fedora Directory Server 1.0.2

[Felipe Alfaro Solana]

> There are no RPMs (yet) for FC5.  Instead, you'll have to build it from
> source.  See http://directory.fedora.redhat.com/wiki/Building#One-%3EStep_Build

Ups! Thanks... I will give it a try.

[Thomas Fitzsimmons]

Hi,

The build instructions on

http://directory.fedora.redhat.com/wiki/Building#One-Step_Build

need to be updated.  Step two should be:

cd dsbuild-fds102/meta/ds

I can confirm that FDS 1.0.2 builds out-of-the-box on my Rawhide
workstation on a completely free stack (no proprietary JDK required for
the Java bits).  This is excellent news!

As a smoke test I tried running startconsole on java-gcj-compat.  It
fails immediately with a GC out-of-memory error.  This is because gij's
support for the -ms and -mx options is limited.  Would it be OK to
remove these options from the launcher scripts for the next release?

When I remove -ms8m -mx64m from startconsole the GUI tool works well on
our free Swing implementation.  I've attached a screenshot.

Could someone add a note about this workaround to the release notes?

Thanks,
Tom

[Rich Megginson]

Thomas Fitzsimmons wrote:
> Hi,
>
> The build instructions on
>
> http://directory.fedora.redhat.com/wiki/Building#One-Step_Build
>
> need to be updated.  Step two should be:
>
> cd dsbuild-fds102/meta/ds
>
> I can confirm that FDS 1.0.2 builds out-of-the-box on my Rawhide
> workstation on a completely free stack (no proprietary JDK required for
> the Java bits).  This is excellent news!

Thanks to you and Lillian for your help.
> As a smoke test I tried running startconsole on java-gcj-compat.  It
> fails immediately with a GC out-of-memory error.  This is because gij's
> support for the -ms and -mx options is limited.  Would it be OK to
> remove these options from the launcher scripts for the next release?

I think we still may need them using other jvms and on other platforms, 
so we'll have to change the script to determine the java version.
> When I remove -ms8m -mx64m from startconsole the GUI tool works well on
> our free Swing implementation.  I've attached a screenshot.
>
> Could someone add a note about this workaround to the release notes?

Done.
> Thanks,
> Tom
>
> --
> Fedora-directory-devel mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-directory-devel

[Thomas Fitzsimmons]

Hi,

On Thu, 2006-03-02 at 18:39 -0700, Richard Megginson wrote:
> Thomas Fitzsimmons wrote:
> > As a smoke test I tried running startconsole on java-gcj-compat.  It
> > fails immediately with a GC out-of-memory error.  This is because gij's
> > support for the -ms and -mx options is limited.

I looked into this a little more: gij fully supports the -mx option but
its -ms option is currently a no-op because it was causing a segfault in
the garbage collector
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20699).  The startconsole
problem seems to be that the selected -mx value is too small for gij.
> > Would it be OK to
> > remove these options from the launcher scripts for the next release?
>
> I think we still may need them using other jvms and on other platforms, 
> so we'll have to change the script to determine the java version.

Increasing -mx to 70m works on my workstation.  After startup top shows
a resident size of 43m; I assume there is a spike in memory consumption
on startup that causes the out-of-memory error but I would have to
profile the console to be sure.

For gij, it may be enough to increase the -mx value in the script to
say, 128m.  But if possible these options should be removed, or only
used on platforms and JVMs that require them.

Tom

[Felipe Alfaro Solana]

> For gij, it may be enough to increase the -mx value in the script to
> say, 128m.  But if possible these options should be removed, or only
> used on platforms and JVMs that require them.

Although the console starts up and seems to work fine, when trying to
open the Directory Server Console, the following exception gets fired:

Exception in thread "http://machine.name:38900/"
java.lang.UnsupportedOperationException: Thread.stop unimplemented
   at java.lang.Thread.stop (libgcj.so.7)
   at java.lang.Thread.stop (libgcj.so.7)
   at com.netscape.management.client.comm.HttpChannel.close (Unknown Source)
   at com.netscape.management.client.comm.CommManager.closeChannel
(Unknown Source)
   at com.netscape.management.client.comm.CommManager.next (Unknown Source)
   at com.netscape.management.client.comm.HttpChannel.run (Unknown Source)
   at java.lang.Thread.run (libgcj.so.7)