* Pierre Habouzit:
> On Mon, Aug 06, 2007 at 08:15:58AM +1000, Hamish Moffatt wrote:
>> On Sun, Aug 05, 2007 at 10:25:34PM +0200, SZALAY Attila wrote:
>> > And I think that the real question is that there is place in Debian for
>> > a multithread/process system logging daemon (against the singleth
* Hamish Moffatt:
> Also does rsyslog guarantee that messages are logged in the order they
> are sent?
The kernel does not guarantee that SOCK_DGRAM sockets preserve order,
even if the packets are sent from a single process/host.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
On Mon, Aug 06, 2007 at 10:22:22PM +0200, SZALAY Attila wrote:
> At first if you poll for an fd in more than one thread you can balance
> the load. (When a thread handle a message another thread can read. Just
> like in spamassassin :)
There's a risk of reordering the messages if subsequent messag
On Sat, Aug 04, 2007 at 02:18:29PM +1000, Hamish Moffatt wrote:
> On Sat, Aug 04, 2007 at 12:12:50AM +0200, Michael Biebl wrote:
> > * Package name: rsyslog
> > Version : 1.18.0
> > Upstream Author : Rainer Gerhards <[EMAIL PROTECTED]>
> > * URL : http://www.rsyslog.com
Hi All!
On Mon, 2007-08-06 at 00:19 +0200, Pierre Habouzit wrote:
>
> please don't CC me, I read the list, and my M-F-T specifically ask you
> not to do so[0].
Ok.
> You didn't answered, why is there any kind of gain to use another CPU
> where 1/100 of one is enough ?
Maybe that is not eno
Hi All!
I have no connection with rsyslog. I don't know anything about this
program.
On Mon, 2007-08-06 at 08:15 +1000, Hamish Moffatt wrote:
>
> Since messages arrive on a single socket (usually connection-less)
> ultimately the messages enter through one process/thread. And they get
> writt
Le dimanche 05 août 2007 à 23:49 +0200, SZALAY Attila a écrit :
> Yes, you are right in a Desktop. You are right in a server too. But if
> you want to collect log messages from some hundred machine is an other
> question. And it's more easy to put another CPU into the machine than
> double the cloc
On Mon, Aug 06, 2007 at 10:39:36AM +0200, Stig Sandbeck Mathisen wrote:
> You have multiple ways for logs to enter:
>
> 514/udp - the good old standard.
>
> /tcp - tcp syslog, queued on the client side, ensured on
> the server side, possibly encrypted if data passes external
> networks.
>
Pierre Habouzit <[EMAIL PROTECTED]> writes:
> The syslog daemon shall not eat anymore than 0.01% of your CPU.
That's just silly. :P
For a cluster of syslog servers, the syslog daemon shall use whatever
CPU time it needs. If it needs more than one CPU, and more than one
CPU is available, then it
Pierre Habouzit wrote:
> To scare people away. But maybe the ability to log into mysql was
> enough. No kidding, that's a great feature of the Description, it says
> to every clever sysadmin: don't use me.
Well, I don't know if you or me or Debian will use it but Fedora is
going to switch to it a
On Mon, Aug 06, 2007 at 08:15:58AM +1000, Hamish Moffatt wrote:
> On Sun, Aug 05, 2007 at 10:25:34PM +0200, SZALAY Attila wrote:
> > And I think that the real question is that there is place in Debian for
> > a multithread/process system logging daemon (against the singlethread
> > ones) or not. An
On Sun, Aug 05, 2007 at 11:49:12PM +0200, SZALAY Attila wrote:
> Hi All!
please don't CC me, I read the list, and my M-F-T specifically ask you
not to do so[0].
> On Sun, 2007-08-05 at 23:07 +0200, Pierre Habouzit wrote:
> > Why ? Do you need 4 CPU to soak your hard drive ? There is usually o
On Sun, Aug 05, 2007 at 10:25:34PM +0200, SZALAY Attila wrote:
> And yes, I know that the choosen method is depend on the function. But I
> think that this function is better to implement with multithread than
> multiprocess, because:
>
> 1. Reading a log message and write it to a file is highly p
Hi All!
On Sun, 2007-08-05 at 23:07 +0200, Pierre Habouzit wrote:
>
> Why ? Do you need 4 CPU to soak your hard drive ? There is usually one
> partition for every logs on the machine, so you don't get a lot writing
> many log files at a time. And if you're that concerned with performance,
> the
On Sun, Aug 05, 2007 at 10:34:03PM +0200, SZALAY Attila wrote:
> Hi All!
>
> On Sun, 2007-08-05 at 13:08 -0500, Ron Johnson wrote:
> >
> > Are you saying that Apache 1.x only ever used 1 CPU?
>
> I protest for multithread/process applications agains singlethread ones.
>
> I doesn't care which p
Hi All!
On Sun, 2007-08-05 at 13:08 -0500, Ron Johnson wrote:
>
> Are you saying that Apache 1.x only ever used 1 CPU?
I protest for multithread/process applications agains singlethread ones.
I doesn't care which paralellization is used i just want to say that
it's not too bad to write a multiX
Hi All!
On Sun, 2007-08-05 at 19:55 +0200, Steinar H. Gunderson wrote:
>
> This is also wrong. All threads in a program share address space, which means
> that all variables are shared by default, which means that every single
> non-local variable access has the potential of a race condition. Mul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/05/07 10:39, SZALAY Attila wrote:
> Hi All!
>
> On Sat, 2007-08-04 at 22:39 +0200, Steinar H. Gunderson wrote:
>> Your system admins sound rather odd. Lots of software is high performance
>> without ever using threads at all.
>
> Yes, but you c
On Sun, Aug 05, 2007 at 06:02:11PM +0200, SZALAY Attila wrote:
>> This is wrong. Note that "multithreading" is a different concept from
>> spawning many processes (ie. the traditional UNIX fork() model).
> You are right, but (I think) it's not harder to write a program which is
> multithread than w
On Sun, 2007-08-05 at 17:43 +0200, Steinar H. Gunderson wrote:
>
> This is wrong. Note that "multithreading" is a different concept from
> spawning many processes (ie. the traditional UNIX fork() model).
You are right, but (I think) it's not harder to write a program which is
multithread than whi
Hi All!
On Sat, 2007-08-04 at 22:39 +0200, Steinar H. Gunderson wrote:
>
> Your system admins sound rather odd. Lots of software is high performance
> without ever using threads at all.
Yes, but you cannot exploit the power of more than one CPU without
multithreading. Of course it's an other que
On Sun, Aug 05, 2007 at 05:39:11PM +0200, SZALAY Attila wrote:
> Yes, but you cannot exploit the power of more than one CPU without
> multithreading.
This is wrong. Note that "multithreading" is a different concept from
spawning many processes (ie. the traditional UNIX fork() model).
/* Steinar *
On Sun, Aug 05, 2007 at 12:21:46AM +1000, Hamish Moffatt wrote:
> System admins might regard multi-threaded as the key to high
> performance.
Your system admins sound rather odd. Lots of software is high performance
without ever using threads at all.
/* Steinar */
--
Homepage: http://www.sesse.n
* Bastian Blank:
> On Sat, Aug 04, 2007 at 01:44:14AM -0400, Roberto C. Sánchez wrote:
>> As the "target" user for this sort of package is a sysadmin type, I
>> would saw it is an important enough detail that it should be in the
>> short description.
>
> But only in the relation: multi-threaded ==
* Hamish Moffatt ([EMAIL PROTECTED]) [070804 16:22]:
> On Sat, Aug 04, 2007 at 12:24:58PM +0200, Bastian Blank wrote:
> > But only in the relation: multi-threaded == bad. You need much more
> > knowledge to handle concurrency correctly.
>
> Yes that's my reaction also.
>
> System admins might reg
On Sat, Aug 04, 2007 at 12:24:58PM +0200, Bastian Blank wrote:
> On Sat, Aug 04, 2007 at 01:44:14AM -0400, Roberto C. Sánchez wrote:
> > As the "target" user for this sort of package is a sysadmin type, I
> > would saw it is an important enough detail that it should be in the
> > short description.
On Sat, Aug 04, 2007 at 01:44:14AM -0400, Roberto C. Sánchez wrote:
> As the "target" user for this sort of package is a sysadmin type, I
> would saw it is an important enough detail that it should be in the
> short description.
But only in the relation: multi-threaded == bad. You need much more
k
On Sat, Aug 04, 2007 at 02:18:29PM +1000, Hamish Moffatt wrote:
> On Sat, Aug 04, 2007 at 12:12:50AM +0200, Michael Biebl wrote:
> > * Package name: rsyslog
> > Version : 1.18.0
> > Upstream Author : Rainer Gerhards <[EMAIL PROTECTED]>
> > * URL : http://www.rsyslog.com
On Sat, Aug 04, 2007 at 12:12:50AM +0200, Michael Biebl wrote:
> * Package name: rsyslog
> Version : 1.18.0
> Upstream Author : Rainer Gerhards <[EMAIL PROTECTED]>
> * URL : http://www.rsyslog.com
> * License : GPL v2 or later
> Programming Lang: C
> Descript
Package: wnpp
Severity: wishlist
Owner: Michael Biebl <[EMAIL PROTECTED]>
* Package name: rsyslog
Version : 1.18.0
Upstream Author : Rainer Gerhards <[EMAIL PROTECTED]>
* URL : http://www.rsyslog.com
* License : GPL v2 or later
Programming Lang: C
Descriptio
30 matches
Mail list logo
