Bug 714339

It is easy to build the binary utilities, so please include them again or alternatively, put them in a separate asterisk-utils package.

To build asterisk with the utilities included:

- edit SOURCES/menuselect.makeopts and change the "MENUSELECT_UTILS=" line to "MENUSELECT_UTILS=aelparse astcanary astman conf2ael muted refcounter smsq stereorize streamplayer"

- edit asterisk.spec and uncomment them in the %files section:
%{_sbindir}/aelparse
%{_sbindir}/astcanary
%{_sbindir}/asterisk
%{_sbindir}/astgenkey
%{_sbindir}/astman
%{_sbindir}/autosupport
%{_sbindir}/conf2ael
%{_sbindir}/muted
%{_sbindir}/rasterisk
%{_sbindir}/refcounter
%{_sbindir}/safe_asterisk
%{_sbindir}/smsq
%{_sbindir}/stereorize
%{_sbindir}/streamplayer

- then build rpm

(In reply to comment #1)
>
> %{_sbindir}/safe_asterisk

I'm OK with building the rest, but the functionality of the safe_asterisk script is better handled by modifying the systemd service file.

I'll add some comments to the systemd service file about how to add that
functionality.

Thanks. I just checked all the utils in the "make menuconfig" but I only use smsq and am not familiar with the other utilities.

If I understand correctly, safe_asterisk implements a respawn in case of a crash by creating its own tty. Replacing that with native systemd functionality is better I guess.

I have changed my mind about systemd and safe_asterisk.

Last night I have seriously tried running systemd on Fedora 15, for the second time. Though it may work great on the regular out-of-the-box desktop experience, it has so many issues on my 'runlevel 3' system that it is a definite no-go for me. And I am not alone http://monolight.cc/2011/05/the-systemd-fallacy/

Switching back to upstart was easy, but then I discovered that some fundamental services like cron and smartd dont even have initscripts no more.
I have been running redhat/fedora since 1999, but if this is the way it is heading I will have to switch to something else.
So please, keep supporting the old init system and include those scripts. I do not use safe_asterisk, but there may be people out there who do.
Thank you.

(In reply to comment #4)
> I have changed my mind about systemd and safe_asterisk.
> 
> Last night I have seriously tried running systemd on Fedora 15, for the second
> time. Though it may work great on the regular out-of-the-box desktop
> experience, it has so many issues on my 'runlevel 3' system that it is a
> definite no-go for me. And I am not alone
> http://monolight.cc/2011/05/the-systemd-fallacy/
> 
> Switching back to upstart was easy, but then I discovered that some fundamental
> services like cron and smartd dont even have initscripts no more.
> I have been running redhat/fedora since 1999, but if this is the way it is
> heading I will have to switch to something else.
> So please, keep supporting the old init system and include those scripts. I do
> not use safe_asterisk, but there may be people out there who do.

I won't get into a long discussion about systemd, except to say that I disagree.  The SysV init script is going to stay in F15 but will be dropped in F16 and replaced with a native systemd service file.

In any case I've added the rest of the binaries... They should show up in the rawhide packages tomorrow.  F15 will take longer as I want to make sure that the 1.8.4.3 security update makes it into stable before pushing out a new package.