asterisk users - Dec 2003 - Multiple mpg123 processes when starting asterisk

When I start asterisk, it appears that multiple mpg123 processes start.
Would this be normal operation?
 
 
 2729 ?        S      0:00 /usr/sbin/asterisk
 2735 ?        S      0:00 mpg123 -q -s --mono -r 8000 -b 2048 -f 8192
av-1.mp3
 2736 ?        S      0:00 mpg123 -q -s --mono -r 8000 -b 2048 -f 8192
av-1.mp3
 2740 ?        S      0:00 mpg123 -q -s --mono -r 8000 -b 2048 -f 8192
-z av-1.mp3
 2742 ?        S      0:00 mpg123 -q -s --mono -r 8000 -b 2048 -f 8192
-z av-1.mp3
 2755 pts/1    R      0:00 ps -ax
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20031227/83795fda/attachment.htm

two for each music on hold class.

bkw

On Sun, 28 Dec 2003, Kevin wrote:
>
> When I start asterisk, it appears that multiple mpg123 processes start.
> Would this be normal operation?
>
>
>  2729 ?        S      0:00 /usr/sbin/asterisk
>  2735 ?        S      0:00 mpg123 -q -s --mono -r 8000 -b 2048 -f 8192
> av-1.mp3
>  2736 ?        S      0:00 mpg123 -q -s --mono -r 8000 -b 2048 -f 8192
> av-1.mp3
>  2740 ?        S      0:00 mpg123 -q -s --mono -r 8000 -b 2048 -f 8192
> -z av-1.mp3
>  2742 ?        S      0:00 mpg123 -q -s --mono -r 8000 -b 2048 -f 8192
> -z av-1.mp3
>  2755 pts/1    R      0:00 ps -ax
>

> When I start asterisk, it appears that multiple mpg123 processes start.  
> Would this be normal operation?
> 
>  2729 ?        S      0:00 /usr/sbin/asterisk
>  2735 ?        S      0:00 mpg123 -q -s --mono -r 8000 -b 2048 -f 8192
av-1.mp3
>  2736 ?        S      0:00 mpg123 -q -s --mono -r 8000 -b 2048 -f 8192
av-1.mp3
>  2740 ?        S      0:00 mpg123 -q -s --mono -r 8000 -b 2048 -f 8192 -z
av-1.mp3
>  2742 ?        S      0:00 mpg123 -q -s --mono -r 8000 -b 2048 -f 8192 -z
av-1.mp3
Someone already mentioned two occurences of the above for each music
on hold class defined (by you) in asterisk.

In some cases, you may also find additional occurences of the above running
if asterisk (and mpg123) did not shut down correctly. The problem is
related to how asterisk kills mpg123 when asterisk is told to stop. Search
the archives for SIG TERM is the last 60 days. (Or, simply stop asterisk
and check to see if any remaining mpg123 processes are running. If so,
kill them.)

Rich