Fabian Groffen wrote:
On 12-10-2008 09:38:04 +0000, Martin Kersten wrote:
Update of /cvsroot/monetdb/MonetDB5/conf In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv19179
Modified Files: monetdb5.conf.in Log Message: Move the MonetDB related files to a clearly marked achorpoint default
-mero_msglog=@localstatedir@@DIRSEP@log@DIRSEP@merovingian.log -mero_errlog=@localstatedir@@DIRSEP@log@DIRSEP@merovingian.log +mero_msglog=@localstatedir@@DIRSEP@MonetDB5@DIRSEP@merovingian.log +mero_errlog=@localstatedir@@DIRSEP@MonetDB5@DIRSEP@merovingian.log
May I suggest to leave in "log" in here. Traditionally, logfiles are stored in /var/log. No real need to deviate from that, I think? /var/log/MonetDB5 would be ok, I guess.
that calls for creating it upon first use, like mserver5. a makedir inbetween does not seem a big problem, despite the fact that is already identifiable as log already from its name.
-mero_pidfile=@localstatedir@@DIRSEP@run@DIRSEP@merovingian.pid +mero_pidfile=@localstatedir@@DIRSEP@MonetDB5@DIRSEP@merovingian.pid
Pidfiles are traditionally stored in /var/run. I think this is not a good idea.
this then depends on the platforms for which 'traditionally' applies. Recall that all gdk_lock files for databases are held there where protection is called for.
Note that both changes don't make "slotting" of monetdb any more possible than it is now.
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers