perfparse-users

[Perfparse-users] Re: perfparse documentation

[Ben C. <Ben...@ro...>]

Yves,

This is a problem with the docbook conversion to HTML.  It seems to
produce fixed width pages which are a bit wide.  I've tried to find a
solution without any luck.  It may be an idea to find/write a parser
with removes all the unwanted HTML.  Leaving just the text and the <p>
taggs.  Or something similar...

Any users who know docbook better than my self, can they please have a
hack at producing good HTML?

PS, we gave birth on Friday to a beautiful 7.6 pound baby (~4.5Kg), who
we have called Adam.  Right now it's baby poo and crying all night,
perfparse will wait a short while!

Ben

Yves wrote:
>>Hello,
>>
>>Is the 'perfparse installation guide' available in a format that doesn't
>>require my browser window to be 2000 pixels wide to read it all?
> 
> 
> Are you using the doc from the docs/ directory ? Did you generate it yourself ? maybe
> consider generating the the pdf form ?
> 
> Yves
> 
> 
> 

Re: [Perfparse-users] Re: perfparse documentation

[Yves <yme...@pe...>]

> Yves,
>
> This is a problem with the docbook conversion to HTML.  It seems to
> produce fixed width pages which are a bit wide.  I've tried to find a
> solution without any luck.  It may be an idea to find/write a parser
> with removes all the unwanted HTML.  Leaving just the text and the <p>
> taggs.  Or something similar...

I'm using docbook-xsl-1.66.1 stylesheet for transformation from docbook t=
o xml. It
transforms <para> tag into <P> tag.
It seems that paragraphs are inside <DIV CLASS=3D"CHAPTER"> tags. If ther=
e is a problem,
it is with the <DIV> tag.
What browser are you using ? I'm trying with IE-5.50 and firefox-1.02 and=
 I have no
problem.

> Any users who know docbook better than my self, can they please have a
> hack at producing good HTML?

I don't think it's a problem with docbook, but with CSS stylesheets. Mayb=
e my default
CSS stylesheet are correct for me, which is not the case for everybody ? =
But before
hacking docbook-xsl, find out if you can produce a CSS stylesheet for the=
 install guide.
If you really want to hack docbook-xsl, first have a look on the docbook-=
xsl guide :
http://www.sagehill.net/docbookxsl/. And then tell the maintainers about =
it :
http://docbook.sourceforge.net/projects/xsl/




> PS, we gave birth on Friday to a beautiful 7.6 pound baby (~4.5Kg), who
> we have called Adam.  Right now it's baby poo and crying all night,
> perfparse will wait a short while!

Congratulations Ben !!! :)
And welcome to Adam :)

Yves



--=20
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- Perfparse   - http://www.perfparse.org/                          -

Re: [Perfparse-users] Re: perfparse documentation

[Steve G. <st...@ls...>]

On Tue, Mar 29, 2005 at 03:45:21PM +0200, Yves wrote:
> It seems that paragraphs are inside <DIV CLASS="CHAPTER"> tags. If there is a problem,
> it is with the <DIV> tag.
> [and]
> I don't think it's a problem with docbook, but with CSS stylesheets. 

No, it's because the example nagios 'define command {...}' stanza's
are wrapped in '<PRE>' tags, and thus don't wrap automatically (which
is good), but also don't have embedded line breaks, which is bad. The
docbook tag <programlisting> is what generates this.

Anyway, the longest line in the HTML doc sets the overall width, so the
wrapping for the whole doc is screwed up.

Steve

-- 
"Outlook not so good." That magic 8-ball knows everything! I'll ask
about Exchange Server next.
                           -- (Stolen from the net)

Re: [Perfparse-users] Re: perfparse documentation

[Yves M. <yme...@li...>]

Steve, do you have any idea how we can change this behaviour without brea=
king the
standards (docbook and the xsl stylesheet from docbook-xsl) ?
Thanks for your explanation anyways.

Yves

> On Tue, Mar 29, 2005 at 03:45:21PM +0200, Yves wrote:
>> It seems that paragraphs are inside <DIV CLASS=3D"CHAPTER"> tags. If t=
here is a problem,
>> it is with the <DIV> tag.
>> [and]
>> I don't think it's a problem with docbook, but with CSS stylesheets.
>
> No, it's because the example nagios 'define command {...}' stanza's
> are wrapped in '<PRE>' tags, and thus don't wrap automatically (which
> is good), but also don't have embedded line breaks, which is bad. The
> docbook tag <programlisting> is what generates this.
>
> Anyway, the longest line in the HTML doc sets the overall width, so the
> wrapping for the whole doc is screwed up.
>
> Steve
>
> --
> "Outlook not so good." That magic 8-ball knows everything! I'll ask
> about Exchange Server next.
>                            -- (Stolen from the net)
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users=
.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
> _______________________________________________
> Perfparse-users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-users
>


--=20
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- Perfparse   - http://www.perfparse.org/                          -

Re: [Perfparse-users] Re: perfparse documentation

[Steve G. <st...@ls...>]

On Tue, Mar 29, 2005 at 05:43:00PM +0200, Yves Mettier wrote:
> Steve, do you have any idea how we can change this behaviour
> without breaking the standards (docbook and the xsl stylesheet from
> docbook-xsl) ? Thanks for your explanation anyways.

Just put line breaks in the docbook code, e.g.

define command{
        command_name    process-service-perfdata
        command_line    /usr/bin/printf "%b" 
                "$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$OUTPUT$\t$SERVICESTATE$\t$PERFDATA$\n" 
                | $USER2$/bin/perfparse-log2mysql -c $USER2$/etc/perfparse.cfg
        }


and then note that the line has been broken for presentation, but
that it actually needs to be all on one line. Or, if nagios supports
the the trailing '\' convention, show it that way, like you do in the
../configure examples earlier:

define command{
        command_name    process-service-perfdata
        command_line    /usr/bin/printf "%b"  \
                "$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$OUTPUT$\t$SERVICESTATE$\t$PERFDATA$\n" \
                | $USER2$/bin/perfparse-log2mysql -c $USER2$/etc/perfparse.cfg 
        }

(I took a quick look at the nagios docs, but they don't seem to say, and
I don't have time right now to experiment.)

Basically, anything inside <programlisting> is presented "as-is", so you
need to get the width of the listing down.

Steve

-- 
"Outlook not so good." That magic 8-ball knows everything! I'll ask
about Exchange Server next.
                           -- (Stolen from the net)