[icecast] CPU Utilization Weirdness

[Gary Major]

Made the change and so far so good, CPU is back where it should be. Running
2 streams at 56K 22Hz is using about 5% CPU total - most respectable I
think.

I have only been running this config for about 10 minutes, but so far so
good. Will post follow up tomorrow.

Thanks Jack - question tho: isn't using console mode 3 the same as using -b
(from the description in the conf file anyway) or it is the same but icecast
treat it differently at runtime.

----- Original Message -----
From: "Jack Moffitt" <jack at xiph.org>
To: <icecast at xiph.org>
Sent: Tuesday, February 05, 2002 11:50 AM
Subject: Re: [icecast] CPU Utilization Weirdness

<p>> > The only thing that seems to work is starting the processes and piping
them
> > to null. The only disadvantage to that is that icecast sucks all
available
> > CPU although it seems to release its hold on the CPU when I start other
> > programs.
>
> Now this is bringing back some memories.
>
> I thought only certain BSDs had this 'feature' that background processes
> still used stdout/stderr and that was a no-no.
>
> Try this:
>
> 1) don't use the -b switch.  Tell icecast to use console_mode 3 in the
> config file.
>
> 2) run icecast like so:  ./icecast > /dev/null 2> /dev/null
>
> 3) run ices hte same way.
>
> See if that helps at all.
>
> jack.
>
> --- >8 ----
> List archives:  http://www.xiph.org/archives/
> icecast project homepage: http://www.icecast.org/
> To unsubscribe from this list, send a message to
'icecast-request at xiph.org'
> containing only the word 'unsubscribe' in the body.  No subject is needed.
> Unsubscribe messages sent to the list will be ignored/filtered.
>

--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to 'icecast-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.