[Asterisk-Users] multiple instances of asterisk spawning
Steven Critchfield
critch at basesys.com
Tue Apr 27 10:28:02 MST 2004
On Tue, 2004-04-27 at 11:57, Joseph Finley wrote:
> Please stick to the topic and do not direct personal attacks. Doing so will
> turn off potential contributors to the * community.
Maybe you need to check your assumptions. The closest thing to an
"attack" was my stating of opinion that the requester was a new unix
user. I'm sure given time, the user would have either confirmed or
refuted the opinion and life moves on.
As for turning off potential contributors, you must maintain current
contributers to ever think of getting potential ones. I know I haven't
done a great deal of code contributions, but I do help when possible on
list. Granted that has been slipping as the newer users piss me off so
much more frequently and my activities to relieve that annoyance
therefore grows more time consuming.
BTW, Learn to use proper quoting and inline responding so you look like
you might have a clue.
> -----Original Message-----
> From: asterisk-users-admin at lists.digium.com
> [mailto:asterisk-users-admin at lists.digium.com] On Behalf Of Steven
> Critchfield
> Sent: Tuesday, April 27, 2004 12:21 PM
> To: asterisk-users at lists.digium.com
> Subject: Re: [Asterisk-Users] multiple instances of asterisk spawning
>
>
> On Tue, 2004-04-27 at 10:04, Steven Kokinos wrote:
> > Hello-
> >
> > I have noticed that since i upgraded my kernel, asterisk spawns many
> > copies (usually approximately 18) when starting up. It then runs fine,
> > but there doesn't seem to be any reason for this behavior. I have tried
> > moving between different kernel versions, and all but the stock fedora
> > core 1 kernel exhibits the same behavior.
> >
> > I have verified running this with both safe_asterisk (as I usually do)
> > as well as manually at the command line with no difference in behavior.
>
> READ THE DAMN ARCHIVES, or at least semi recent discussions.
>
> I'm betting you are a fairly new unix user as you don't seem to recognize a
> multi threaded app. Asterisk is behaving similarly to apache, starting many
> threads to service quite a few items at once.
>
> Your kernel upgrade is probably not the only thing that has happened here.
> It was commented recently in this mailing list that a recent change in RH ha
> changed the default behaviour of ps. This change is why you are now seeing
> something else.
--
Steven Critchfield <critch at basesys.com>
More information about the asterisk-users
mailing list