Thanks Mathieu. So, it is not possible to set this at build time by passing a parameter to the configure script... IMHO, a symbolic link is not a good idea in production environments. BR
Pablo On Tue, Feb 17, 2009 at 1:05 PM, Mathieu Rene <[email protected]> wrote: > You can specify those as runtime argument. > > $ ./freeswitch -h > these are the optional arguments you can pass to freeswitch > -nf -- no forking > -u [user] -- specify user to switch to > -g [group] -- specify group to switch to > -help -- this message > -core -- dump cores > -hp -- enable high priority settings > -vg -- run under valgrind > -nosql -- disable internal sql scoreboard > -stop -- stop freeswitch > -nc -- do not output to a console and background > -c -- output to a console and stay in the foreground > -conf [confdir] -- specify an alternate config dir > -log [logdir] -- specify an alternate log dir > -db [dbdir] -- specify an alternate db dir > -mod [moddir] -- specify an alternate mod dir > -htdocs [htdocsdir] -- specify an alternate htdocs dir > -scripts [scriptsdir] -- specify an alternate scripts dir > > But in my opinion, you should keep all files at the same place and make a > symbolic link if you really want stuf to be accessible from /var/log > > > Mathieu > > _______________________________________________ > Freeswitch-users mailing list > [email protected] > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org > > _______________________________________________ Freeswitch-users mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
