But that does not discuss where you can and where you cannot place
your own lock files (the -p argument)
On Fri, Sep 12, 2008 at 3:35 PM, Jan-Henrik Haukeland <address@hidden
> wrote:
The Monit pid-file is discussed briefly here
http://www.tildeslash.com/monit/doc/manual.php#files
On 12. sep.. 2008, at 13.58, Moshe Cohen wrote:
After some further playing around, I noticed that the default file
is placed in the home directory (which just happened to be my
current directory).
Stating the file as ~/xxx works.
What are the exact rules for legal lock files ?
On Fri, Sep 12, 2008 at 2:07 PM, Moshe Cohen <address@hidden>
wrote:
Thanks.
Followup question:
starting monit regularly (no -p) works and creates a .monit.pid
file in the current directory
starting another instance with "-p xxx" fails and the log says
there is no permission to create the file. ( -p /tmp/xxx works,
though. )
How come the default PID file is created but the specified one has
no permission - both on same current directory ?
TIA
Moshe
On Fri, Sep 12, 2008 at 7:58 AM, Jan-Henrik Haukeland <address@hidden
> wrote:
Just specify a different pidfile using the -p switch to Monit
On 11. sep.. 2008, at 22.59, Moshe Cohen wrote:
How can I run more than one instances of Mon it on the same machine?
Currently, starting a new Monit instance just awakens the existing
daemon of the existing instance.
Moshe
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general