Hello,
Mark Saad longcount.org> writes:
>
> 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 t
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 installing some
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 , having all of them at the LOG_CRIT level. W
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
> items within t
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 sta
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 s
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 when the logging gets massive (1000
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 within the /var/log/messag
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 logging gets massive (1000 ent
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 within the /var/log/messages
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 ?
FreeBSD ultra5.bsdtec
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 syslog()
: > call looks to b
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 (3) this be solved by changing
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 conditions for thread safe sys
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 least on OpenB
you probably want [EMAIL PROTECTED]
Marc Balmer wrote:
Hi
I am a long time Unix developer but new with FreeBSD. I worked the
last years mostly with OpenBSD. First I am overwhelmed by the number
of mailing lists you guys provide. Second I am not sure if I picked
the right one ;-) So please di
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 worked the last
> years mostly wi
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 these functions, but the cc man
In the last episode (Oct 06), Marc Balmer said:
> I am a long time Unix developer but new with FreeBSD. I worked the
> last years mostly with OpenBSD. First I am overwhelmed by the number
> of mailing lists you guys provide. Second I am not sure if I picked
> the right one ;-) So please direct me
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
On Thu, 8 Jun 2000, Johan Kruger wrote:
> I started syslogd on Amnesiac with : syslogd -d and i get
>
> Logging to CONSOLE /dev/console
> 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 X WALL:
> 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 X FILE: /var/log/crit
> 3 3 3 3 3 3 3 3 3 3 3 3 3 3
28 matches
Mail list logo
