linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Alex Netes <alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 3/4 for opensm] /etc/init.d/opensmd: Improve systemd integration
Date: Wed, 24 Oct 2012 16:45:51 +0200	[thread overview]
Message-ID: <5087FF1F.20907@acm.org> (raw)
In-Reply-To: <5087FC29.4030303-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On 10/24/12 16:33, Doug Ledford wrote:
> On 10/24/2012 9:27 AM, Alex Netes wrote:
>> On 16:44 Fri 21 Sep     , Bart Van Assche wrote:
>>>   start () {
>>> +    if [ -e $pidfile ]; then
>>
>> On opensm segfault (happens one in a while :), pidfile won't be removed, so
>> you won't be able to start the opensm again. I guess that same thing can
>> happen on warm reboot.
>
> The stop action in the script should handle cleanup for you.  If it's
> called, and a pid file exists, but the pid is not running, it should
> remove the pid file and the subsystem lock file so that a clean start works.

Hello Doug,

Do we really need the lock file ? On some Linux systems (Ubuntu) the 
/var/lock/subsys directory does not even exist.

Bart.

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2012-10-24 14:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21 14:44 [PATCH 3/4 for opensm] /etc/init.d/opensmd: Improve systemd integration Bart Van Assche
     [not found] ` <505C7D44.9060500-HInyCGIudOg@public.gmane.org>
2012-10-24 13:27   ` Alex Netes
2012-10-24 14:33     ` Doug Ledford
     [not found]       ` <5087FC29.4030303-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-10-24 14:45         ` Bart Van Assche [this message]
     [not found]           ` <5087FF1F.20907-HInyCGIudOg@public.gmane.org>
2012-10-24 14:48             ` Doug Ledford
2012-10-24 14:40     ` Bart Van Assche
     [not found]       ` <5087FDE5.30603-HInyCGIudOg@public.gmane.org>
2012-10-24 16:13         ` Alex Netes
2012-10-25  9:59           ` [PATCH 3/4 v2 " Bart Van Assche

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5087FF1F.20907@acm.org \
    --to=bvanassche-hinycgiudog@public.gmane.org \
    --cc=alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).