[Asterisk-bugs] [Zaptel 0010181]: sudo make config fails to call chkconfig

noreply at bugs.digium.com noreply at bugs.digium.com
Wed Jul 11 12:12:57 CDT 2007


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10181 
====================================================================== 
Reported By:                seanbright
Assigned To:                qwell
====================================================================== 
Project:                    Zaptel
Issue ID:                   10181
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.4.3 
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        Yes 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             07-11-2007 09:55 CDT
Last Modified:              07-11-2007 12:12 CDT
====================================================================== 
Summary:                    sudo make config fails to call chkconfig
Description: 
When building zaptel, I use a non-privileged user account, but when I run
make install and make config I use sudo.  On my CentOS 5.0 install:

Linux xxx.xxx.xxx 2.6.18-8.1.6.el5 http://bugs.digium.com/view.php?id=1 SMP Thu
Jun 14 17:46:09 EDT 2007
i686 i686 i386 GNU/Linux

Executing `sudo make config` does not call chkconfig.  Su'ing and then
running `make config` calls chkconfig appropriately.
====================================================================== 

---------------------------------------------------------------------- 
 qwell - 07-11-07 12:12  
---------------------------------------------------------------------- 
In the patch that I attached, if chkconfig couldn't be found, it would set
CHKCONFIG to :.

That was not what I committed - I instead documented the issue, since it
can very easily break other things if your PATH isn't setup properly. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-11-07 12:12  qwell          Note Added: 0067132                          
======================================================================




More information about the Asterisk-bugs mailing list