From: Bruce Hill <daddy@happypenguincomputers.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] syslog-ng segfaults
Date: Thu, 18 Jul 2013 17:49:22 -0500 [thread overview]
Message-ID: <20130718224922.GR3387@server> (raw)
In-Reply-To: <1374187274.26910.2.camel@scurvy.electronsweatshop.com>
On Thu, Jul 18, 2013 at 06:41:14PM -0400, Randy Barlow wrote:
> I saw that there were a couple of syslog-ng threads recently, but
> neither of them mentioned any segfaulting which I am currently
> experiencing. My log file (dmesg and /var/log/messages) is full of lines
> like this:
>
> syslog-ng[32015]: segfault at 44d8 ip 00007f4f3fa23c83 sp
> 00007fffb233b940 error 4 in libsyslog-ng.so.0.0.0 (deleted)[7f4f3f9eb000
> +67000]
>
> Has anybody else seen anything like that?
Try changing the version at the top of the config file to the present version.
--
Happy Penguin Computers >')
126 Fenco Drive ( \
Tupelo, MS 38801 ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
next prev parent reply other threads:[~2013-07-18 22:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 22:41 [gentoo-user] syslog-ng segfaults Randy Barlow
2013-07-18 22:49 ` Randy Barlow
2013-07-18 22:49 ` Bruce Hill [this message]
2013-07-18 22:55 ` Randy Barlow
2013-07-18 22:50 ` Bruce Hill
2013-07-18 22:58 ` Randy Barlow
2013-07-19 0:53 ` [gentoo-user] [Solved] " Randy Barlow
2013-07-19 4:46 ` Dan Johansson
2013-07-19 15:59 ` Randy Barlow
2013-07-19 18:12 ` Alexey Mishustin
2013-07-19 5:50 ` [gentoo-user] " Алексей Мишустин
2013-07-19 8:48 ` Adam Carter
2013-07-19 9:06 ` Alexey Mishustin
2013-07-19 21:03 ` Randy Barlow
2013-07-20 12:27 ` kwkhui
2013-07-20 21:54 ` Neil Bothwick
2013-07-22 21:25 ` Randy Barlow
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=20130718224922.GR3387@server \
--to=daddy@happypenguincomputers.com \
--cc=gentoo-user@lists.gentoo.org \
/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