[SSSD] Re: [Freeipa-interest] Announcing SSSD 1.16.0

[Jakub Hrozek]

On Wed, Oct 25, 2017 at 02:06:08PM +0200, Michael Ströder wrote:
> Lukas Slebodnik wrote:
> > On (25/10/17 13:07), Michael Ströder wrote:
> >> Which versions of XML/XSLT/docbook packages are you using?
> > 
> > docbook-style-xsl-1.79.2-5
> > 
> > But it might work on fedora due to following patch
> > https://src.fedoraproject.org/rpms/docbook-style-xsl/c/6391185bf3cb096561d8ff86b60602d697b18245?branch=master
> 
> I will check that.
> 
> > But build would fail based on
> > https://bugzilla.redhat.com/show_bug.cgi?id=1409587
> 
> Hmm, man page build seems to work (see generated result attached).
> 
> But I forgot to mention these two messages in the build output:
> 
> Variable $SGML_CATALOG_FILES not set
> Note: namesp. add : added namespace before processing  SSSD
> Manual pages
> 
> Does that ring any bell?
> (I have to admit I know next to nothing in this field.)

It's been literally years since I was poking at this part of the build
system, but we seem to be exporting the SGML_CATALOG_FILES explicitly in
the man Makefile.am:
 53 export SGML_CATALOG_FILES

And we always substitute this variable for either the value passed with
"--with-xml-catalog-path=PATH" during configure or, if that is unset,
we pass /etc/xml/catalog as a sensible default.

So I'm actually not sure how can the variable be unset..

But IIRC the docbook tools are smart enough to find the catalog on their
own.
___
sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org
To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org

[SSSD] Re: [Freeipa-interest] Announcing SSSD 1.16.0

[Michael Ströder]

Lukas Slebodnik wrote:
> On (25/10/17 13:07), Michael Ströder wrote:
>> Which versions of XML/XSLT/docbook packages are you using?
> 
> docbook-style-xsl-1.79.2-5
> 
> But it might work on fedora due to following patch
> https://src.fedoraproject.org/rpms/docbook-style-xsl/c/6391185bf3cb096561d8ff86b60602d697b18245?branch=master

I will check that.

> But build would fail based on
> https://bugzilla.redhat.com/show_bug.cgi?id=1409587

Hmm, man page build seems to work (see generated result attached).

But I forgot to mention these two messages in the build output:

Variable $SGML_CATALOG_FILES not set
Note: namesp. add : added namespace before processing  SSSD
Manual pages

Does that ring any bell?
(I have to admit I know next to nothing in this field.)

Ciao, Michael.
'\" t
.\" Title: sssd
.\"Author: The SSSD upstream - https://pagure.io/SSSD/sssd/
.\" Generator: DocBook XSL Stylesheets v1.79.2 
.\"  Date: 10/25/2017
.\"Manual: SSSD Manual pages
.\"Source: SSSD
.\"  Language: English
.\"
.TH "SSSD" "8" "10/25/2017" "SSSD" "SSSD Manual pages"
.\" -
.\" * Define some portability stuff
.\" -
.\" ~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~
.ie \n(.g .ds Aq \(aq
.el   .ds Aq '
.\" -
.\" * set default formatting
.\" -
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -
.\" * MAIN CONTENT STARTS HERE *
.\" -





.SH "NAME"
sssd \- System Security Services Daemon


.SH "SYNOPSIS"

.HP \w'\fBsssd\fR\ 'u

\fBsssd\fR
 [\fIoptions\fR]




.SH "DESCRIPTION"


.PP
\fBSSSD\fR
provides a set of daemons to manage access to remote directories and 
authentication mechanisms\&. It provides an NSS and PAM interface toward the 
system and a pluggable backend system to connect to multiple different account 
sources as well as D\-Bus interface\&. It is also the basis to provide client 
auditing and policy services for projects like FreeIPA\&. It provides a more 
robust database to store local users as well as extended user data\&.



.SH "OPTIONS"




.PP
\fB\-d\fR,\fB\-\-debug\-level\fR \fILEVEL\fR
.RS 4



SSSD supports two representations for specifying the debug level\&. The 
simplest is to specify a decimal value from 0\-9, which represents enabling 
that level and all lower\-level debug messages\&. The more comprehensive option 
is to specify a hexadecimal bitmask to enable or disable specific levels (such 
as if you wish to suppress a level)\&.
.sp

Please note that each SSSD service logs into its own log file\&. Also 
please note that enabling
\(lqdebug_level\(rq
in the
\(lq[sssd]\(rq
section only enables debugging just for the sssd process itself, not for the 
responder or provider processes\&. The
\(lqdebug_level\(rq
parameter should be added to all sections that you wish to produce debug logs 
from\&.
.sp

In addition to changing the log level in the config file using the
\(lqdebug_level\(rq
parameter, which is persistent, but requires SSSD restart, it is also possible 
to change the debug level on the fly using the
\fBsss_debuglevel\fR(8)
tool\&.
.sp

Currently supported debug levels:
.sp

\fI0\fR,
\fI0x0010\fR: Fatal failures\&. Anything that would prevent SSSD from starting 
up or causes it to cease running\&.
.sp

\fI1\fR,
\fI0x0020\fR: Critical failures\&. An error that doesn\*(Aqt kill SSSD, but one 
that indicates that at least one major feature is not going to work properly\&.
.sp

\fI2\fR,
\fI0x0040\fR: Serious failures\&. An error announcing that a particular request 
or operation has failed\&.
.sp

\fI3\fR,
\fI0x0080\fR: Minor failures\&. These are the errors that would percolate down 
to cause the operation failure of 2\&.
.sp

\fI4\fR,
\fI0x0100\fR: Configuration settings\&.
.sp

\fI5\fR,
\fI0x0200\fR: Function data\&.
.sp

\fI6\fR,
\fI0x0400\fR: Trace messages for operation functions\&.
.sp

\fI7\fR,
\fI0x1000\fR: Trace messages for internal control functions\&.
.sp

\fI8\fR,
\fI0x2000\fR: Contents of function\-internal variables that may be 
interesting\&.
.sp

\fI9\fR,
\fI0x4000\fR: Extremely low\-level tracing information\&.
.sp

To log required bitmask debug levels, simply add their numbers together as 
shown in following 

[SSSD] Re: [Freeipa-interest] Announcing SSSD 1.16.0

[Lukas Slebodnik]

On (25/10/17 13:07), Michael Ströder wrote:
>(limited this to sssd-devel)
>
>Jakub Hrozek wrote:
>> On Mon, Oct 23, 2017 at 09:33:11PM +0200, Michael Ströder wrote:
>>> Jakub Hrozek wrote:
 On Mon, Oct 23, 2017 at 09:19:21PM +0200, Michael Ströder wrote:
>>> BuildRequires:  docbook-xsl-stylesheets
>>> BuildRequires:  libxml2-tools
>>> BuildRequires:  libxslt-tools
>> 
>> Right, you should be able to build the man page from the command line by 
>> calling e.g.:
>> 
>> /usr/bin/xsltproc -o sssd.8  --catalogs
>> --xinclude --nonet --stringparam profile.condition
>> "with_false;with_sudo;with_autofs;with_ssh;with_pac_responder;with_ifp;gpo_default_enforcing;with_secrets;have_systemd;no_enable_files_domain;with_kcm"
>> http://docbook.sourceforge.net/release/xsl/current/manpages/profile-docbook.xsl
>> /home/remote/jhrozek/devel/sssd/src/man/sssd.8.xml
>> 
>> (Sorry for the super-long line, I just copied it from buildroot on my 
>> laptop..)
>> 
>> I'd try if going back to either an older OpenSuse buildroot or an older
>> sssd tarball makes any difference..
>
>This shows that there is something wrong with docbook-xsl-1.79.2 even
>with two openSUSE patch files disabled in my local builds.
>
>Which versions of XML/XSLT/docbook packages are you using?
>

docbook-style-xsl-1.79.2-5

But it might work on fedora due to following patch
https://src.fedoraproject.org/rpms/docbook-style-xsl/c/6391185bf3cb096561d8ff86b60602d697b18245?branch=master

But build would fail based on
https://bugzilla.redhat.com/show_bug.cgi?id=1409587

LS
___
sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org
To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org

[SSSD] Re: [Freeipa-interest] Announcing SSSD 1.16.0

[Michael Ströder]

(limited this to sssd-devel)

Jakub Hrozek wrote:
> On Mon, Oct 23, 2017 at 09:33:11PM +0200, Michael Ströder wrote:
>> Jakub Hrozek wrote:
>>> On Mon, Oct 23, 2017 at 09:19:21PM +0200, Michael Ströder wrote:
>> BuildRequires:  docbook-xsl-stylesheets
>> BuildRequires:  libxml2-tools
>> BuildRequires:  libxslt-tools
> 
> Right, you should be able to build the man page from the command line by 
> calling e.g.:
> 
> /usr/bin/xsltproc -o sssd.8  --catalogs
> --xinclude --nonet --stringparam profile.condition
> "with_false;with_sudo;with_autofs;with_ssh;with_pac_responder;with_ifp;gpo_default_enforcing;with_secrets;have_systemd;no_enable_files_domain;with_kcm"
> http://docbook.sourceforge.net/release/xsl/current/manpages/profile-docbook.xsl
> /home/remote/jhrozek/devel/sssd/src/man/sssd.8.xml
> 
> (Sorry for the super-long line, I just copied it from buildroot on my 
> laptop..)
> 
> I'd try if going back to either an older OpenSuse buildroot or an older
> sssd tarball makes any difference..

This shows that there is something wrong with docbook-xsl-1.79.2 even
with two openSUSE patch files disabled in my local builds.

Which versions of XML/XSLT/docbook packages are you using?

Ciao, Michael.



smime.p7s
Description: S/MIME Cryptographic Signature
___
sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org
To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org

[SSSD] Re: [Freeipa-interest] Announcing SSSD 1.16.0

[Jakub Hrozek]

On Mon, Oct 23, 2017 at 09:33:11PM +0200, Michael Ströder wrote:
> Jakub Hrozek wrote:
> > On Mon, Oct 23, 2017 at 09:19:21PM +0200, Michael Ströder wrote:
> >> Jakub Hrozek wrote:
> >>> On Mon, Oct 23, 2017 at 08:46:08PM +0200, Michael Ströder wrote:
>  Has anything changed with building the man pages?
> 
>  I'm asking because I now get formatting markup in the output of man (see
>  below).
> >>>
> >>> No, not that I'm aware of. You render the man pages locally, right,
> >>> because the tarball only contains the XML sources?
> >>
> >> I'm looking at the man pages generated by the RPM build on openSUSE
> >> build server which IIRC used to work up to sssd release 1.15.2:
> >>
> >> https://build.opensuse.org/package/view_file/home:stroeder:branches:network:ldap/sssd/sssd.spec?expand=1
> > 
> > Nothing changed there for a long time.. If you build the last-known-good
> > (so, 1.15.2) tarball in exactly the same build root, the man pages are
> > rendered fine?
> 
> Ummpf! It seems that the man pages were broken recently even for the
> 1.15.2 builds.
> 
> Any hints which man build tools to check?
> Related build dependencies seem to be:
> 
> BuildRequires:  docbook-xsl-stylesheets
> BuildRequires:  libxml2-tools
> BuildRequires:  libxslt-tools

Right, you should be able to build the man page from the command line by 
calling e.g.:

/usr/bin/xsltproc -o sssd.8  --catalogs
--xinclude --nonet --stringparam profile.condition
"with_false;with_sudo;with_autofs;with_ssh;with_pac_responder;with_ifp;gpo_default_enforcing;with_secrets;have_systemd;no_enable_files_domain;with_kcm"
http://docbook.sourceforge.net/release/xsl/current/manpages/profile-docbook.xsl
/home/remote/jhrozek/devel/sssd/src/man/sssd.8.xml

(Sorry for the super-long line, I just copied it from buildroot on my laptop..)

I'd try if going back to either an older OpenSuse buildroot or an older
sssd tarball makes any difference..
___
sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org
To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org

[SSSD] Re: [Freeipa-interest] Announcing SSSD 1.16.0

[Michael Ströder]

Jakub Hrozek wrote:
> On Mon, Oct 23, 2017 at 09:19:21PM +0200, Michael Ströder wrote:
>> Jakub Hrozek wrote:
>>> On Mon, Oct 23, 2017 at 08:46:08PM +0200, Michael Ströder wrote:
 Has anything changed with building the man pages?

 I'm asking because I now get formatting markup in the output of man (see
 below).
>>>
>>> No, not that I'm aware of. You render the man pages locally, right,
>>> because the tarball only contains the XML sources?
>>
>> I'm looking at the man pages generated by the RPM build on openSUSE
>> build server which IIRC used to work up to sssd release 1.15.2:
>>
>> https://build.opensuse.org/package/view_file/home:stroeder:branches:network:ldap/sssd/sssd.spec?expand=1
> 
> Nothing changed there for a long time.. If you build the last-known-good
> (so, 1.15.2) tarball in exactly the same build root, the man pages are
> rendered fine?

Ummpf! It seems that the man pages were broken recently even for the
1.15.2 builds.

Any hints which man build tools to check?
Related build dependencies seem to be:

BuildRequires:  docbook-xsl-stylesheets
BuildRequires:  libxml2-tools
BuildRequires:  libxslt-tools

Ciao, Michael.



smime.p7s
Description: S/MIME Cryptographic Signature
___
sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org
To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org

[SSSD] Re: [Freeipa-interest] Announcing SSSD 1.16.0

[Jakub Hrozek]

On Mon, Oct 23, 2017 at 09:19:21PM +0200, Michael Ströder wrote:
> Jakub Hrozek wrote:
> > On Mon, Oct 23, 2017 at 08:46:08PM +0200, Michael Ströder wrote:
> >> Has anything changed with building the man pages?
> >>
> >> I'm asking because I now get formatting markup in the output of man (see
> >> below).
> > 
> > No, not that I'm aware of. You render the man pages locally, right,
> > because the tarball only contains the XML sources?
> 
> I'm looking at the man pages generated by the RPM build on openSUSE
> build server which IIRC used to work up to sssd release 1.15.2:
> 
> https://build.opensuse.org/package/view_file/home:stroeder:branches:network:ldap/sssd/sssd.spec?expand=1
> 
> Ciao, Michael.

Nothing changed there for a long time.. If you build the last-known-good
(so, 1.15.2) tarball in exactly the same build root, the man pages are
rendered fine?
___
sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org
To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org

[SSSD] Re: [Freeipa-interest] Announcing SSSD 1.16.0

[Jakub Hrozek]

On Mon, Oct 23, 2017 at 08:46:08PM +0200, Michael Ströder wrote:
> HI!
> 
> Has anything changed with building the man pages?
> 
> I'm asking because I now get formatting markup in the output of man (see
> below).

No, not that I'm aware of. You render the man pages locally, right,
because the tarball only contains the XML sources?

> 
> Ciao, Michael.
> 
> SSSD-LDAP(5)
>   File Formats and Conventions
>SSSD-LDAP(5)
> 
> .SH "NAME" sssd-ldap - SSSD LDAP provider
> 
> .SH "DESCRIPTION"
> 
> .PP This manual page describes the configuration of LDAP domains
> for sssd(8). Refer to the “FILE FORMAT” section of the sssd.conf(5)
> manual page for detailed syntax information.
> 
> .PP You can configure SSSD to use more than one LDAP domain.
> 

___
sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org
To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org