Woof!
On Sat, 13 Dec 2008 18:52:59 -0500, Michael Collins m...@freeswitch.org wrote:
All you'd have to do is modify the logfile.conf.xml file and pick a new path
for your freeswitch.log file...
I agree. I had discovered this option and considered it as a workaround. Then
I also found that
I can't figure out why the log file would need to be in the db folder...
/b
On Dec 9, 2008, at 10:45 AM, Andy Spitzer wrote:
Woof!
It appears that FreeSWITCH writes
freeswitch.history
freeswitch.log
freeswitch.pid
freeswitch.xml.fsxml
to the -log directory.
Is there a way to
Woof!
On Mon, 15 Dec 2008 11:56:53 -0500, Brian West br...@freeswitch.org wrote:
I can't figure out why the log file would need to be in the db folder...
I think you misunderstand.
It's these files:
freeswitch.history
freeswitch.pid
freeswitch.xml.fsxml
That I feel would be better
I think you misunderstand.
It's these files:
freeswitch.history
freeswitch.pid
freeswitch.xml.fsxml
That I feel would be better off in the db folder. They are not logs, and
should not be rotated.
if freeswitch.history isn't a log, what is it? seems to me taht it's a
Woof!
On Mon, 15 Dec 2008 13:16:32 -0500, Raymond Chandler
intralan...@freeswitch.org wrote:
if freeswitch.history isn't a log, what is it? seems to me taht it's a
log of what commands you've run recently... it's definitely NOT a
database
Actually, I the readline/history library uses it
Another option for you, ironically, is to have the freeswitch.log file plus
the other log files that are not freeswitch's, to go into a third directory
that is uniquely set up for this purpose. That way it wouldn't be disruptive
to move a bunch of files from log to db. All you'd have to do is