From: "Michael P. Soulier" <msoulier@digitaltorque.ca>
Subject: svlogd and blank lines
Date: Sun, 26 Mar 2006 08:15:27 -0500 [thread overview]
Message-ID: <20060326131527.GL12075@tigger.digitaltorque.ca> (raw)
Hello,
Sorry for the resend, but I didn't see the original come through, and I can't
seem to get to the list archives to confirm if it did.
"Firefox can't find the server at skarnet.org."
I've moved an app from logging via multilog to using svlogd. I'm
noticing that in the output, there are no longer any blank lines, used
to break up sections of the logs and keep the more readable.
Is this design intent?
Thanks,
Mike
--
Michael P. Soulier <msoulier@digitaltorque.ca>
"Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the opposite
direction." --Albert Einstein
next reply other threads:[~2006-03-26 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 13:15 Michael P. Soulier [this message]
2006-03-27 11:30 ` Laurent Bercot
-- strict thread matches above, loose matches on Subject: below --
2006-03-24 2:50 Michael P. Soulier
2006-03-26 15:17 ` Gerrit Pape
2006-03-26 15:53 ` Michael P. Soulier
2006-04-06 20:01 ` Alex Efros
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060326131527.GL12075@tigger.digitaltorque.ca \
--to=msoulier@digitaltorque.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).