[MPICH] start mpd if it has not started

[Ralph M. Butler]

> Date: Wed, 3 Aug 2005 17:42:43 -0400
> From: Kamaraju Kusumanchi <kamaraju at gmail.com>
> To: mpich-discuss at mcs.anl.gov
> Subject: Re: [MPICH] start mpd if it has not started
>
> On 8/3/05, Ralph M. Butler <rbutler at mtsu.edu> wrote:
> >
> > > Date: Wed, 3 Aug 2005 17:12:19 -0400
> > > From: Kamaraju Kusumanchi <kamaraju at gmail.com>
> > > To: mpich-discuss at mcs.anl.gov
> > > Subject: Re: [MPICH] start mpd if it has not started
> > >
> > > On 8/3/05, Ralph M. Butler <rbutler at mtsu.edu> wrote:
> > >
> > > > It depends on your intended usage of course, but you might want to
> > > > simply use the -d (--daemon) option, e.g.:
> > > >     $ mpd --daemon
> > > > In this case, you do not need the & for background because mpd
> > > > will background itself.  If there is an mpd already running, it
> > > > will exit silently.  Of course, if there is no other mpd running,
> > > > but the new one fails for some other reason, that will appear to
> > > > be silent also.  When running as a daemon, all output goes into
> > > > the syslogs.
> > > >
> > > >
> > >
> > > This looks interesting. Could someone tell me where this log file is located?
> >
> > That depends on your system's configuration.  mpd uses the
> > syslog facility and logs messages of different priorities.
> > On a linux system they are likely to be in /var/log/X where X
> > is syslog* or messages*, etc.  This is configurable in
> > /etc/syslog.conf for example.
> >
> >
>
> Thanks for the reply. On my system (Debian, sid) it is stored in
> /var/log/syslog .

Some kinds of messages will go into /var/log/messages, esp. certain
errors.  So, you might do an 'ls -ltr' if you want to see which
file(s) changed most recently.