Re: [Monetdb-developers] [Monetdb-checkins] MonetDB5/conf monetdb5.conf.in, , 1.34, 1.35
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.
-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. Note that both changes don't make "slotting" of monetdb any more possible than it is now.
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
On 12-10-2008 13:48:14 +0200, Martin Kersten wrote:
-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.
afaict it worked out of the box, I'm only concerned with logs not being in the location one would expect
-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.
a pid-file is not a lock, maybe there is some confusion here? The pid-file is only there for start-stop-daemon and alike programs that like to stop merovingian without doing a `ps ax | grep '[m]erovingian' | cut -c1-7 | xargs kill` or something else that gives little control to what should actually be killed.
On Sun, Oct 12, 2008 at 02:14:17PM +0200, Fabian Groffen wrote:
On 12-10-2008 13:48:14 +0200, Martin Kersten wrote:
-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.
Indeed /var/log is generaly what is done on linux/unix. Some for /var/run. I'd say we only use the MonetDB5 subdir for what used to be dbfarm. And we just moved the sql/xquery logs also under there. Niels
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.
afaict it worked out of the box, I'm only concerned with logs not being in the location one would expect
-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.
a pid-file is not a lock, maybe there is some confusion here? The pid-file is only there for start-stop-daemon and alike programs that like to stop merovingian without doing a `ps ax | grep '[m]erovingian' | cut -c1-7 | xargs kill` or something else that gives little control to what should actually be killed.
------------------------------------------------------------------------- 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
-- Niels Nes, Centre for Mathematics and Computer Science (CWI) Kruislaan 413, 1098 SJ Amsterdam, The Netherlands room C0.02, phone ++31 20 592-4098, fax ++31 20 592-4312 url: http://www.cwi.nl/~niels e-mail: Niels.Nes@cwi.nl
Niels Nes wrote:
On Sun, Oct 12, 2008 at 02:14:17PM +0200, Fabian Groffen wrote:
On 12-10-2008 13:48:14 +0200, Martin Kersten wrote:
-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.
Indeed /var/log is generaly what is done on linux/unix. Some for /var/run. I'd say we only use the MonetDB5 subdir for what used to be dbfarm. And we just moved the sql/xquery logs also under there.
ok, then we just look for more defensive code actions concerning system wide actions, such as merovingian, and provide enligthning errors.
Niels
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.
afaict it worked out of the box, I'm only concerned with logs not being in the location one would expect
-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.
a pid-file is not a lock, maybe there is some confusion here? The pid-file is only there for start-stop-daemon and alike programs that like to stop merovingian without doing a `ps ax | grep '[m]erovingian' | cut -c1-7 | xargs kill` or something else that gives little control to what should actually be killed.
------------------------------------------------------------------------- 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
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.
You're confusing logs and logs. The logs traditionally in /var/log are of a totally different order from the write-ahead logs in MonetDB. MonetDB log's are an integral part of the database and not an optional add-on like the logs in /var/log. Those latter logs are useful to see what has happened, but they are not meant to secure transactions. The contents of /var/log can be deleted with impunity, but that is not the case for the write-ahead logs of MonetDB.
-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.
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
-- Sjoerd Mullender
participants (4)
-
Fabian Groffen -
Martin Kersten -
Niels Nes -
Sjoerd Mullender