[asterisk-bugs] [Asterisk 0017492]: logger.conf does not create subdirectories or give warnings about them missing

[Asterisk Bug Tracker]

The following issue has been ASSIGNED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17492 
====================================================================== 
Reported By:                lmadsen
Assigned To:                junky
====================================================================== 
Project:                    Asterisk
Issue ID:                   17492
Category:                   Core/Configuration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
JIRA:                       SWP-1670 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 260521 
Request Review:              
====================================================================== 
Date Submitted:             2010-06-09 07:39 CDT
Last Modified:              2010-10-13 07:28 CDT
====================================================================== 
Summary:                    logger.conf does not create subdirectories or give
warnings about them missing
Description: 
Today in testing and documenting the logger.conf, we read that logging can
be performed into a full path if you start the filename with a front-slash
(we feel you should also be able to specify a relative path from
/var/log/asterisk by defining something like:   mydirectory/messages -- but
we know that is a feature request).

However, if you specify something like:

/var/log/asterisk/my_new_directory/messages =>
verbose,notice,warning,error


Then when you do the 'logger reload' you can see that it has loaded
successfully with 'logger show channels', but no ERROR is produced showing
that the directory does not exist, or an inability to write to the location
specified.

No error is also produced when the logging takes place (i.e. when you
place a call).

I believe this could be a pretty major error for someone who may expect
the logging to work like that ;)
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-13 07:28 junky          Status                   acknowledged =>
assigned
2010-10-13 07:28 junky          Assigned To               => junky           
======================================================================