Woof! It appears that FreeSWITCH writes freeswitch.history freeswitch.log freeswitch.pid freeswitch.xml.fsxml to the -log directory. Is there a way to put the files other than freeswitch.log into the -db directory instead? In my environment we archive and rotate everything in the log directory (which includes logs beside FreeSWITCH's), and these other FreeSWITCH files are getting rotated. Yeah, I can explicitly exclude them, but to me it seems those really belong in the -db directory anyway, as they are inherently data needed for the current executable of FreeSWITCH, and not logs. --Woof!
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 modify the logfile.conf.xml file and pick a new path for your freeswitch.log file... -MC On Tue, Dec 9, 2008 at 8:45 AM, Andy Spitzer <woof@nortel.com> 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 put the files other than freeswitch.log into the -db directory instead?
In my environment we archive and rotate everything in the log directory (which includes logs beside FreeSWITCH's), and these other FreeSWITCH files are getting rotated. Yeah, I can explicitly exclude them, but to me it seems those really belong in the -db directory anyway, as they are inherently data needed for the current executable of FreeSWITCH, and not logs.
--Woof!
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Woof! On Sat, 13 Dec 2008 18:52:59 -0500, Michael Collins <msc@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 mod_xml_rpc was also logging in log dir, and I haven't found a way to control that one--I haven't looked that hard, I must admit. Weekends are a great way to forget everything you were doing the week before! --Woof!
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 put the files other than freeswitch.log into the - db directory instead?
In my environment we archive and rotate everything in the log directory (which includes logs beside FreeSWITCH's), and these other FreeSWITCH files are getting rotated. Yeah, I can explicitly exclude them, but to me it seems those really belong in the -db directory anyway, as they are inherently data needed for the current executable of FreeSWITCH, and not logs.
--Woof!
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Woof! On Mon, 15 Dec 2008 11:56:53 -0500, Brian West <brian@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 off in the db folder. They are not logs, and should not be rotated. --Woof!
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 log of what commands you've run recently... it's definitely NOT a database.... neither is the pid file. while the pid file isn't a db, it's also not really a log... but i don't know that i'd agree with making a "run" directory just to house the pid. -Ray
Woof! On Mon, 15 Dec 2008 13:16:32 -0500, Raymond Chandler <intralanman@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 to determine the command line history (http://tiswww.case.edu/php/chet/readline/history.html#SEC15). So it IS a database. It may also be seen as a log of commands, as it happens to be a nice ASCII file, but that's an intended side effect of the way the library writes it. --Woof!
participants (4)
-
Andy Spitzer
-
Brian West
-
Michael Collins
-
Raymond Chandler