-stable
>
> I noticed that syslog-ng is spinning out of control with a stock config.
>
> ps shows I have two syslog-ng pids
That is normal, one is the supervisor, the other one does the actual
logging part: http://www.balabit.com/wiki/syslog-ng-faq-supervisor
> the lower numbed p
results in multiple irrecoverable READ ERRORS on the CD?
not just 9.* but with some machines there are problems with CD/DVD drive
switch to loader prompt and type
set hw.ata.atapi_dma=0
worked with 8.*
So, am I the only one on the planet who still installs FreeBSD the old-
fashioned way, i.e
In message
, Adrian Chadd wrote:
>On 12 December 2012 14:04, Ronald F. Guilmette wrote:
>> From where I am sitting, the freebsd web site is still only offering
>> version 9.1-RC3.
>
>The images have to be pushed out to ftp-master and over to the mirrors
>before the release announcement goes ou
On 12 December 2012 14:04, Ronald F. Guilmette wrote:
>
> In message
>
> Mark Saad wrote:
>
>> I am wondering if anyone has seen this. I pulled down the 9.1-RELEASE
>>install media...
>
> That's very interesting. Where did you obtain that?
>
> From where I am sitting, the freebsd web site is s
In message
Mark Saad wrote:
> I am wondering if anyone has seen this. I pulled down the 9.1-RELEASE
>install media...
That's very interesting. Where did you obtain that?
>From where I am sitting, the freebsd web site is still only offering
version 9.1-RC3.
__
looks like i jumped the gun its a bug in syslog-ng
https://bugzilla.balabit.com/show_bug.cgi?id=193
On Wed, Dec 12, 2012 at 11:50 AM, Mark Saad wrote:
> All
> I am wondering if anyone has seen this. I pulled down the 9.1-RELEASE
> install media and did a clean install . After i
All
I am wondering if anyone has seen this. I pulled down the 9.1-RELEASE
install media and did a clean install . After installing some ports from
the packages on
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable
I noticed that syslog-ng is spinning out of control with a stock
On Mon, Sep 3, 2012 at 3:23 AM, Ian Lepore
wrote:
> On Sun, 2012-09-02 at 19:50 -0600, Ian Lepore wrote:
>> On Mon, 2012-09-03 at 00:35 +0100, Attilio Rao wrote:
>> > Hi,
>> > I was trying to use syslog(3) in a port application that uses
>> > threading , havi
Attilio, good day.
Mon, Sep 03, 2012 at 12:35:24AM +0100, Attilio Rao wrote:
> I was trying to use syslog(3) in a port application that uses
> threading , having all of them at the LOG_CRIT level. What I see is
> that when the logging gets massive (1000 entries) I cannot find some
>
On Mon, 3 Sep 2012, Attilio Rao wrote:
I was trying to use syslog(3) in a port application that uses threading ,
having all of them at the LOG_CRIT level. What I see is that when the
logging gets massive (1000 entries) I cannot find some items within the
/var/log/messages (I know because I
On 9/3/2012 4:05 AM, Attilio Rao wrote:
Hi,
I was trying to use syslog(3) in a port application that uses
threading , having all of them at the LOG_CRIT level. What I see is
that when the logging gets massive (1000 entries) I cannot find some
items within the /var/log/messages (I know because I
On Sun, 2012-09-02 at 19:50 -0600, Ian Lepore wrote:
> On Mon, 2012-09-03 at 00:35 +0100, Attilio Rao wrote:
> > Hi,
> > I was trying to use syslog(3) in a port application that uses
> > threading , having all of them at the LOG_CRIT level. What I see is
> > that wh
On Mon, 2012-09-03 at 00:35 +0100, Attilio Rao wrote:
> Hi,
> I was trying to use syslog(3) in a port application that uses
> threading , having all of them at the LOG_CRIT level. What I see is
> that when the logging gets massive (1000 entries) I cannot find some
> items with
On Mon, Sep 3, 2012 at 1:20 AM, Garrett Cooper wrote:
> On Sun, Sep 2, 2012 at 4:35 PM, Attilio Rao wrote:
>> Hi,
>> I was trying to use syslog(3) in a port application that uses
>> threading , having all of them at the LOG_CRIT level. What I see is
>> that when the
On Sun, Sep 2, 2012 at 4:35 PM, Attilio Rao wrote:
> Hi,
> I was trying to use syslog(3) in a port application that uses
> threading , having all of them at the LOG_CRIT level. What I see is
> that when the logging gets massive (1000 entries) I cannot find some
> items with
Hi,
I was trying to use syslog(3) in a port application that uses
threading , having all of them at the LOG_CRIT level. What I see is
that when the logging gets massive (1000 entries) I cannot find some
items within the /var/log/messages (I know because I started stamping
also some sort of message
On 12/02/11 23:45, Zhihao Yuan wrote:
>> In 2008 I implemented the syslog RFCs for NetBSD's syslogd, so if you
> That's an amazing work. Did you compared those documents (they were
> drafts in 08') with the final versions? Any differences?
I followed the IETF process
2011/12/2 Martin Schütte :
> On 12/01/11 10:01, Zhihao Yuan wrote:
>> trivial. How about to implement RFC 5848 in our syslogd?
>
> In 2008 I implemented the syslog RFCs for NetBSD's syslogd, so if you
> are interested please take a look at the syslog code in NetBSD-cur
On 12/01/11 10:01, Zhihao Yuan wrote:
> trivial. How about to implement RFC 5848 in our syslogd?
In 2008 I implemented the syslog RFCs for NetBSD's syslogd, so if you
are interested please take a look at the syslog code in NetBSD-current
and at my report, linked under http://mschuette
> Regardless of his stupid arguments, let's talk about something
> trivial. How about to implement RFC 5848 in our syslogd? It adds the
> encryption to the existing syslog message layer, and increase the
> security in transferring.
> http://tools.ietf.org/html/rfc5848
w about to implement RFC 5848 in our syslogd? It adds the
encryption to the existing syslog message layer, and increase the
security in transferring.
http://tools.ietf.org/html/rfc5848
Albert Mietus made a nice presentation in 2002
http://www.slideshare.net/SoftwareBeterMaken.nl/securing-syslog-on-f
Robert Watson schrieb:
managed if done carefully. I'm not sure if you've looked at Apple's
extended syslog, which among other things, includes a binary log file
format making it more mechanically searched and managed, do take a look
if you haven't.
I read the
I think that complexity can be
> > managed if done carefully. I'm not sure if you've looked at Apple's
> > extended syslog, which among other things, includes a binary log file format
> > making it more mechanically searched and managed, do take a look if you
> > hav
ou've looked at Apple's
> extended syslog, which among other things, includes a binary log file format
> making it more mechanically searched and managed, do take a look if you
> haven't.
... and I'm not just saying this to be ornery, but what about test log file
forma
On Fri, 2 May 2008, Martin Schütte wrote:
I am taking part in this year's Google Summer of Code for NetBSD and want to
implement the upcoming IETF Syslog standards for BSD's syslogd(8). The most
important improvements will be an extended message format, TLS network
transport, a
Edwin Groothuis schrieb:
that would prevent adoption; just like FreeBSD keeps Sendmail instead of
adopting Postfix in its base system.
There are other reasons for this. And the way the mail system is
setup makes it is very simple to replace the default MTA with an
other MTA in the ports collecti
On Sat, May 03, 2008 at 02:39:21PM +0200, Martin Sch?tte wrote:
> I only wonder if that would not be the bigger and more drastic change
> that would prevent adoption; just like FreeBSD keeps Sendmail instead of
> adopting Postfix in its base system.
There are other reasons for this. And the way
Anthony Pankov schrieb:
It is not pleasant to me that most comprehensible unix subsystem -
syslog - will grow to multipurpose monster.
I would like to discuss this point further (so this mail got a bit
longer) because I also thought about it and it basically depends on
where you draw the
Xin LI schrieb:
| and for developing I maintain a Trac at
| http://barney.cs.uni-potsdam.de/trac/syslogd/
That's cool. Is there any commit-mail style stuff that we can subscribe
so we can gradually incorporate your work into FreeBSD?
You could use the RSS feed (Browse Source -> Revision Log) t
On Sat, May 03, 2008 at 12:30:27PM +0400, Anthony Pankov wrote:
> It is not pleasant to me that most comprehensible unix subsystem -
> syslog - will grow to multipurpose monster.
>
> More pleasant to here about careful redesign of syslogd that make
> available various plugins|add
Hello Martin,
It is not pleasant to me that most comprehensible unix subsystem -
syslog - will grow to multipurpose monster.
More pleasant to here about careful redesign of syslogd that make
available various plugins|additional daemons each of which adds
well-defined functionality.
I dislike
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Schütte wrote:
| Hello,
| I am taking part in this year's Google Summer of Code for NetBSD and
| want to implement the upcoming IETF Syslog standards for BSD's
| syslogd(8). The most important improvements will be an extended messag
Hello,
I am taking part in this year's Google Summer of Code for NetBSD and
want to implement the upcoming IETF Syslog standards for BSD's
syslogd(8). The most important improvements will be an extended message
format, TLS network transport, and digital signatures.
I hope these new
Hello.
That's what i found on freebsd.org/projects/:
SYSLOG-SECURE: In August 2001 a standard of syslog was made: RFC3164.
This RFC describes some extensions to add security to syslog. The project
started in 2002 is to adapt RFC3164 to FreeBSD version of syslog, a
On 8/5/06, Luigi Rizzo <[EMAIL PROTECTED]> wrote:
On Sat, Aug 05, 2006 at 12:42:12AM +0100, Joao Barros wrote:
...
> I patched and recompiled the kernel.
> After booting I notice that no messages from ppp are logged by syslog
> (messages|ppp.log)
What is your OS version ?
On Sat, Aug 05, 2006 at 12:42:12AM +0100, Joao Barros wrote:
...
> I patched and recompiled the kernel.
> After booting I notice that no messages from ppp are logged by syslog
> (messages|ppp.log)
What is your OS version ?
i hit a similar problem some time ago, and it seems that
t
In message: <[EMAIL PROTECTED]>
Marc Balmer <[EMAIL PROTECTED]> writes:
: Am 06.10.2004 um 16:48 schrieb Dan Nelson:
:
: > The only unsafe part is openlog(), so set that up before you start any
: > threads and you'll be okay. Once the log fd is opened, the sys
On 2004-10-07 07:20, Marc Balmer <[EMAIL PROTECTED]> wrote:
>
> 1) openlog() must be called before any threads that use syslog() are
> started.
> 2) The first argument to openlog() must not be NULL.
> 3) The "%m" Format String must not be used in syslog() calls.
Can
In the last episode (Oct 07), Marc Balmer said:
> At least on OpenBSD I can use "%m" in the syslog() format string.
> This results in a call to strerror(), which is not thread safe,
> AFAIK. This probably is true for FreeBSD as well, so we have the
> following three cond
Am 06.10.2004 um 16:48 schrieb Dan Nelson:
The only unsafe part is openlog(), so set that up before you start any
threads and you'll be okay. Once the log fd is opened, the syslog()
call looks to be thread-safe. Everything in there is done with local
variables and atomic writes.
At lea
direct me to the right place if this list
is only for discussion of FreeBSD system development...
My question regarding thread-safeness of syslog(): On OpenBSD I used
syslog_r() to do thread safe logging (the software in question is a
sendmail milter, which runs multithreaded). FreeBSD does not
For what it's worth, I've used syslog to the *console* before, in a
multithreaded network daemon. No problems encountered.
On Wed, 6 Oct 2004 16:28:32 +0200, Marc Balmer <[EMAIL PROTECTED]> wrote:
> Hi
>
> I am a long time Unix developer but new with FreeBSD. I worke
In the last episode (Oct 06), Dan Nelson said:
> > My question regarding thread-safeness of syslog(): On OpenBSD I
> > used syslog_r() to do thread safe logging (the software in question
> > is a sendmail milter, which runs multithreaded). FreeBSD does not
> > have the
lease direct me to the right place if this list
> is only for discussion of FreeBSD system development...
>
> My question regarding thread-safeness of syslog(): On OpenBSD I used
> syslog_r() to do thread safe logging (the software in question is a
> sendmail milter, which runs multit
discussion of FreeBSD system development...
My question regarding thread-safeness of syslog(): On OpenBSD I used
syslog_r() to do thread safe logging (the software in question is a
sendmail milter, which runs multithreaded). FreeBSD does not have
these functions, but the cc man page states that
On Sun, Jan 04, 2004 at 02:15:18AM +0700, Eugene Grosbein wrote:
> Hi!
>
> [EMAIL PROTECTED] wrote 8 years ago in src/lib/libc/gen/syslog.c:
>
> p += sprintf(p, "%.15s ", ctime(&now) + 4);
>
> What is '+ 4' for?
quite likely it is to skip the 'day of week' field -- the ctime
manpage says
In the last episode (Jan 04), Eugene Grosbein said:
> [EMAIL PROTECTED] wrote 8 years ago in src/lib/libc/gen/syslog.c:
>
> p += sprintf(p, "%.15s ", ctime(&now) + 4);
>
> What is '+ 4' for?
ctime returns a date in the format:
Thu Nov 24 18:22:48 1986\n\0
The +4 skips the day name.
--
On Sun, Jan 04, 2004 at 02:15:18AM +0700, Eugene Grosbein wrote:
> Hi!
>
> [EMAIL PROTECTED] wrote 8 years ago in src/lib/libc/gen/syslog.c:
>
> p += sprintf(p, "%.15s ", ctime(&now) + 4);
>
> What is '+ 4' for?
ctime() returns:
Thu Nov 24 18:22:48 1986\n\0
So ctime()+4 returns:
Eugene Grosbein wrote:
> [EMAIL PROTECTED] wrote 8 years ago in src/lib/libc/gen/syslog.c:
>
> p += sprintf(p, "%.15s ", ctime(&now) + 4);
>
> What is '+ 4' for?
Oh, I've got it. Please ignore this question, sorry.
Eugene
___
[EMAIL PROTECTED] maili
Hi!
[EMAIL PROTECTED] wrote 8 years ago in src/lib/libc/gen/syslog.c:
p += sprintf(p, "%.15s ", ctime(&now) + 4);
What is '+ 4' for?
http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/gen/syslog.c.diff?r1=1.2&r2=1.3
Eugene Grosbein
P.S. Please CC me, I'm not in list
__
Jeffrey D. Wheelhouse <[EMAIL PROTECTED]> types:
> > -Original Message-
> > From: Peter Wullinger [mailto:[EMAIL PROTECTED]]
> > Subject: Re: Circular log patches for syslog
> >
> > Just to spoil the thread:
> >
> > Shouldn't things
> -Original Message-
> From: Peter Wullinger [mailto:[EMAIL PROTECTED]]
> Subject: Re: Circular log patches for syslog
>
> Just to spoil the thread:
>
> Shouldn't things like this be available as additional package,
> so that the base system supplies only
> -Original Message-
>
> how do you decide the size of the circular log ?
There's a utility included to unwind the log file into time order. It
includes a command line option to create logfiles of user-defined size.
http://software.wwwi.com/syslogd/clog.html
Jeff
To Unsubscribe: se
Jeffrey D. Wheelhouse wrote:
>
> While working on another project, I made some patches to syslogd to support
> circular logfiles:
>
> http://software.wwwi.com/syslogd/
>
> The syslogd patch includes changes to the man page to reflect the new usage.
how do you decide the size of the circular lo
Hi,
While working on another project, I made some patches to syslogd to support
circular logfiles:
http://software.wwwi.com/syslogd/
The syslogd patch includes changes to the man page to reflect the new usage.
I don't know if this is useful to anyone else, but it came in handy for me
on a sma
x27;t be
> portable, but take a look at the man page for fuopen(3).
I presume you meant funopen() :)
Hmm this one looks really nice. I guess what the original poster
wanted would be a call to fwopen(), then parsing the 'output' into
lines and passing those to syslog().. I'll try it
On Sep 1, 3:24pm, Peter Pentchev wrote:
} Subject: Re: Redirect stdout/stderr to syslog [OFF-TOPIC]
} On Fri, Sep 01, 2000 at 02:13:19PM +0200, Alexander Maret wrote:
} > > -Ursprungliche Nachricht-
} > > Von: Peter Pentchev [mailto:[EMAIL PROTECTED]]
} > > Ge
> Hi,
>
> I wonder if it is possible to redirect stdout/stderr to syslog.
>
> Background:
> I'm writing a program which starts (fork=>execvp) and observes
> another program. I would like to redirect all output of the "execvped"
> program to syslog.
&
ut/stderr to logger(1), and you're all set.
> > You may even
> > specify a facility/level to log with.
> >
>
> Thanks for your quick answer but I would prefer to
> do it entirely in C without calling external progs.
> I could think of a solution forking another chil
t; You may even
> > specify a facility/level to log with.
> >
>
> Thanks for your quick answer but I would prefer to
> do it entirely in C without calling external progs.
> I could think of a solution forking another child process
> which does the syslog logging and redirecti
with.
>
Thanks for your quick answer but I would prefer to
do it entirely in C without calling external progs.
I could think of a solution forking another child process
which does the syslog logging and redirecting stdout/stderr
of the execvped program via IPC to this child.
But is there an
f it is possible to redirect stdout/stderr to syslog.
>
> Background:
> I'm writing a program which starts (fork=>execvp) and observes
> another program. I would like to redirect all output of the "execvped"
> program to syslog.
>
> I know this is not reall
Hi,
I wonder if it is possible to redirect stdout/stderr to syslog.
Background:
I'm writing a program which starts (fork=>execvp) and observes
another program. I would like to redirect all output of the "execvped"
program to syslog.
I know this is not really FBSD related
On Wed, Jun 14, 2000 at 11:52:22AM +0200, Neil Blakey-Milner wrote:
> On Tue 2000-06-13 (22:40), Bernd Walter wrote:
> > > I've often thought it would be nice to be able to get syslogd to
> > > make choices based on hostname. I'm sure a patch would be easy
> > > enough to produce, but the trick wo
On Tue 2000-06-13 (22:40), Bernd Walter wrote:
> > I've often thought it would be nice to be able to get syslogd to
> > make choices based on hostname. I'm sure a patch would be easy
> > enough to produce, but the trick would be to produce a good syntax
> > fox syslog.conf. Are there any syslogds
On Tue, Jun 13, 2000 at 05:12:41PM +0100, David Malone wrote:
> On Tue, Jun 13, 2000 at 11:07:27AM -0500, Dan Nelson wrote:
> > In the last episode (Jun 13), Johan Kruger said:
> > >
> > > The man page says " ... and the first word in the message after the
> > > date matches the program, the
On Tue, Jun 13, 2000 at 11:07:27AM -0500, Dan Nelson wrote:
> In the last episode (Jun 13), Johan Kruger said:
> >
> > The man page says " ... and the first word in the message after the
> > date matches the program, the action specified in the action
> > field will be taken ..."
> > No
In the last episode (Jun 13), Johan Kruger said:
>
> The man page says " ... and the first word in the message after the
> date matches the program, the action specified in the action
> field will be taken ..."
> Now the program should the be !4.5.6.1 or one of the ones i previously
> m
*:)
I know they are tagged - but the following does not work:
- Example --
Jun 13 16:41:51 4.5.6.1 root: package=etc 1.2.3.1:/etc/ -> /etc/
Jun 13 16:41:51 4.5.6.1 root: package=etc 1.2.3.1:/etc/ -> /etc/
Jun 13 16:41:51 4.5.6.1 root: Scanning local directory /etc/
Jun
all
> B's logs must have a specific tag ?? Can i start the syslogd on B in
> such a way that all the logs are made with a tag ???
The word immediately after the timestamp in any syslog file is the
hostname of the machine sending the alert. For example, these lines
came from some networ
Morning ... has broken ...
Is it possible to tel machine B to remote log to machine A with
all the logs coming from B specified with a tag.
I want the normal messsages on B to be remotely logged to A (no problem)
but on A all B's logs must have a specific tag ??
Can i start the syslogd on B in su
r/log/all
> syslogd: restarted
> readfds = 0x38
>
> NOTICE THE UNUSED
> Amnesiac do not want to use ockle - i tried specifying the i.p. of ockle
> but to no avail. ockle is in the hosts file on Amnesiac, a dns is present
> and specified in /etc/resolve.conf and it works.
Try
I have 2 machine's : A = Amnesiac B = ockle
I want to remote log to ockle from Amnesiac
Amnesiac : /etc/syslog.conf
*.emerg *
*.crit /var/log/crit
*.err
Hi
I have a system running a stable snap of 3.4 of round about May 31,
I have a program that does quite a bit of logging, and sometime the
following occurs:
The process would just stop (seems to block) - a bt in gdb showed
that it was stuck in open after the following sequence of calls
syslog
On Thu, 11 May 2000, Matthew Dillon wrote:
> I had to fix up /etc/rc.network a little to load the ipsec rules
> at the appropriate point (just after the interface and ipfw setup,
> but before any services (like NFS) are run). I am going to put the
> (relatively simple) patch for
> IPSec isn't well documented, but once I figured out the config
> file it didn't seem too bad. I am guessing that replay prevention
Reading the RFCs might be more helpful than most of the KAME
documentation. There's also a lot of undocumented stuff for which the
sources seem to be the
:
:
:[EMAIL PROTECTED] (Matthew Dillon) writes:
:
:> The question is: What am I forgetting to do? Or is this a bug in our
:> IPSEC implementation?
:
:AFAIK this is more or less how it's supposed to work. IPsec is a
:mess. Security associations are not stateless, ESP provides replay
:p
[EMAIL PROTECTED] (Matthew Dillon) writes:
> The question is: What am I forgetting to do? Or is this a bug in our
> IPSEC implementation?
AFAIK this is more or less how it's supposed to work. IPsec is a
mess. Security associations are not stateless, ESP provides replay
protection us
Anybody an ipsec guru? I've setup an ipsec transport between two
hosts, A and B on an unsecure network, the setkey configuration file is
included below.
It works fine until I reboot one host (A). After it has rebooted
any packets I send from A to B causes B to report 'replay
On Sat, 12 Feb 2000, Andrzej Bialecki wrote:
> I was wondering if there is any way currently to emit a message from
> within kernel, so that syslogd can pick it up later on, but without
> spoiling the standard message buffer. AFAIK, there is no way to do it
> right now.
>
> The reason I'm asking
Hi,
I was wondering if there is any way currently to emit a message from
within kernel, so that syslogd can pick it up later on, but without
spoiling the standard message buffer. AFAIK, there is no way to do it
right now.
The reason I'm asking is that quite a few programs (most notably
ipfw) spi
On Wed, Jul 14, 1999 at 10:56:05PM -0700, Mike Smith wrote:
> > On Tue, 13 Jul 1999, Mike Smith wrote:
> >
> > > 'siobi' is someone trying to open the serial console, for whatever
> > > reason. Without knowing who it was that was stuck there, it's hard to
> > > guess what is going on.
> >
> >
On Wed, Jul 14, 1999 at 10:56:05PM -0700, Mike Smith wrote:
> > On Tue, 13 Jul 1999, Mike Smith wrote:
> >
> > > 'siobi' is someone trying to open the serial console, for whatever
> > > reason. Without knowing who it was that was stuck there, it's hard to
> > > guess what is going on.
> >
> >
r real world load my freebsd box
had 20-40% free cpu and a load average of 1.5. With load as equal as the
switch could make it, the linux box had no free cpu and a load average of
8. :) I also (finally) got the approval to install freebsd on the fourth
box (there are already two linux machine
r real world load my freebsd box
had 20-40% free cpu and a load average of 1.5. With load as equal as the
switch could make it, the linux box had no free cpu and a load average of
8. :) I also (finally) got the approval to install freebsd on the fourth
box (there are already two linux machine
> On Tue, 13 Jul 1999, Mike Smith wrote:
>
> > 'siobi' is someone trying to open the serial console, for whatever
> > reason. Without knowing who it was that was stuck there, it's hard to
> > guess what is going on.
>
> D'uh, sorry. Long day. It was amd that was hung in the siobi
> state.
> On Tue, 13 Jul 1999, Mike Smith wrote:
>
> > 'siobi' is someone trying to open the serial console, for whatever
> > reason. Without knowing who it was that was stuck there, it's hard to
> > guess what is going on.
>
> D'uh, sorry. Long day. It was amd that was hung in the siobi
> state.
On Tue, 13 Jul 1999, Matthew Dillon wrote:
> Comment the whole thing out, kill -HUP the syslogd (or kill and restart
> it), and see if amd still locks up.
Ok, now I think I get it. You want me to enable syslog'ing in amd,
then do what you're talking about here. I will try this fir
On Tue, 13 Jul 1999, Mike Smith wrote:
> 'siobi' is someone trying to open the serial console, for whatever
> reason. Without knowing who it was that was stuck there, it's hard to
> guess what is going on.
D'uh, sorry. Long day. It was amd that was hung in the siobi
state. No way to clea
ed to
:the serial console. Also, just in case it matters I start syslogd with
:-svv flags in rc.conf.
:
:
:> Try messing around
:> with /etc/syslog.conf and see if just plain file logging prevents the
:> lockup -- you could even try turning off all logging (but leaving syslog
:>
> On Tue, 13 Jul 1999, Mike Smith wrote:
>
> > > After pounding on this some more with today's -current (prior to
> > > the MNT_ASYNC flag change) I got a lot more lockups that looked like
> > > this:
> > >
> > > On Mon, 12 Jul 1999, Doug wrote:
> > >
> > > > Ok, got another hang in "
On Tue, 13 Jul 1999, Mike Smith wrote:
> > After pounding on this some more with today's -current (prior to
> > the MNT_ASYNC flag change) I got a lot more lockups that looked like
> > this:
> >
> > On Mon, 12 Jul 1999, Doug wrote:
> >
> > > Ok, got another hang in "siobi" state (this tim
On Tue, 13 Jul 1999, Matthew Dillon wrote:
> :
> : So I started thinking that maybe the problem was actually in
> :syslog (or amd's interface to it). So I disabled the following two options
> :in my amd.conf file:
> :
> :log_file = syslog:local7
> :lo
On Tue, 13 Jul 1999, Matthew Dillon wrote:
> Comment the whole thing out, kill -HUP the syslogd (or kill and restart
> it), and see if amd still locks up.
Ok, now I think I get it. You want me to enable syslog'ing in amd,
then do what you're talking about here. I will try this fi
On Tue, 13 Jul 1999, Mike Smith wrote:
> 'siobi' is someone trying to open the serial console, for whatever
> reason. Without knowing who it was that was stuck there, it's hard to
> guess what is going on.
D'uh, sorry. Long day. It was amd that was hung in the siobi
state. No way to cle
ed to
:the serial console. Also, just in case it matters I start syslogd with
:-svv flags in rc.conf.
:
:
:> Try messing around
:> with /etc/syslog.conf and see if just plain file logging prevents the
:> lockup -- you could even try turning off all logging (but leaving syslog
> On Tue, 13 Jul 1999, Mike Smith wrote:
>
> > > After pounding on this some more with today's -current (prior to
> > > the MNT_ASYNC flag change) I got a lot more lockups that looked like
> > > this:
> > >
> > > On Mon, 12 Jul 1999, Doug wrote:
> > >
> > > > Ok, got another hang in
On Tue, 13 Jul 1999, Mike Smith wrote:
> > After pounding on this some more with today's -current (prior to
> > the MNT_ASYNC flag change) I got a lot more lockups that looked like
> > this:
> >
> > On Mon, 12 Jul 1999, Doug wrote:
> >
> > > Ok, got another hang in "siobi" state (this ti
On Tue, 13 Jul 1999, Matthew Dillon wrote:
> :
> : So I started thinking that maybe the problem was actually in
> :syslog (or amd's interface to it). So I disabled the following two options
> :in my amd.conf file:
> :
> :log_file = syslog:local7
> :lo
> After pounding on this some more with today's -current (prior to
> the MNT_ASYNC flag change) I got a lot more lockups that looked like
> this:
>
> On Mon, 12 Jul 1999, Doug wrote:
>
> > Ok, got another hang in "siobi" state (this time after it
> > successfully completed the script).
1 - 100 of 107 matches
Mail list logo
