| Summary: | ASTERISK-05433: [patch] setpriority failing should not be fatal at startup. | ||
| Reporter: | stevekstevek (stevekstevek) | Labels: | |
| Date Opened: | 2005-11-02 17:23:42.000-0600 | Date Closed: | 2008-01-15 15:54:43.000-0600 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) asterisk-priority-not-fatal.patch | |
| Description: | Presently, if ast_set_priority fails at startup, this is treated as a fatal error -- whether you're trying set highpriority or not. It fails for me in the case where I'm starting asterisk as a non-root user, _and_ it's already running as real-time. In this case, the code is actually trying to set it to run _not_ as high priority, and failing. In any case, My 2c is that it's probably sufficient to log a warning here, and not to make this fatal. | ||
| Comments: | By: Kevin P. Fleming (kpfleming) 2005-11-07 21:28:57.000-0600 Committed to CVS HEAD, thanks! By: Digium Subversion (svnbot) 2008-01-15 15:54:43.000-0600 Repository: asterisk Revision: 7014 U trunk/ChangeLog U trunk/asterisk.c ------------------------------------------------------------------------ r7014 | kpfleming | 2008-01-15 15:54:42 -0600 (Tue, 15 Jan 2008) | 2 lines issue ASTERISK-5433 ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=7014 | ||