| Summary: | ASTERISK-07088: Asterisk doesn't fork and become a daemon | ||
| Reporter: | Will Kemp (willkemp) | Labels: | |
| Date Opened: | 2006-06-03 20:22:24 | Date Closed: | 2006-06-04 16:14:43 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Running Asterisk from the command line, with just 'asterisk', it doesn't fork and become a daemon if the following lines are in asterisk.conf : [options] verbose = 4 ; Verbosity level for logging (- v) Adding these lines to asterisk.conf in an otherwise unmodified sample version of /etc/asterisk causes this to happen. I first noticed this in version 1.2.0 or 1.2.2, i believe - but it was around that time that i first used this option in asterisk.conf . Since then, i've been working around it by starting Asterisk with 'asterisk >/dev/null 2>&1 &' and have only just got round to trying to work out what's causing it. | ||
| Comments: | By: Russell Bryant (russell) 2006-06-04 16:14:42 This is known behavior. I have brought it up to Mark before and he likes it this way (using the verbose option implies not to fork). To work around this issue, you can use alwaysfork=yes in the [options] section of asterisk.conf, or start asterisk with the -F option. Thanks | ||