From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: Alex Netes <alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] /etc/init.d/opensmd: Improve systemd integration
Date: Sun, 16 Sep 2012 14:22:11 +0200 [thread overview]
Message-ID: <5055C473.5050401@acm.org> (raw)
In-Reply-To: <20120916093159.GB8243@calypso>
On 09/16/12 11:31, Alex Netes wrote:
> Hi Bart,
>
> On 18:07 Fri 14 Sep , Bart Van Assche wrote:
>> On recent SLES and openSUSE systems it is necessary to read the
>> file /lib/lsb/init-functions instead of /etc/rc.status for proper
>> integration with systemd. Also, prevent that the opensm process is
>> started twice and drop /var/lock/subsys/opensm.
>
> There could be a problem (which also persists in the original script), that in
> theory you can run two OpenSM instances (on different ports) which is not
> being supported by the init script. Any thoughts how this can be addressed?
How about following the same approach as for srp_daemon: modify
/etc/init.d/opensm such that it starts a script that starts the opensm
process on all ports on which it should be started ?
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
prev parent reply other threads:[~2012-09-16 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 16:07 [PATCH] /etc/init.d/opensmd: Improve systemd integration Bart Van Assche
[not found] ` <50535650.6050306-HInyCGIudOg@public.gmane.org>
2012-09-16 9:31 ` Alex Netes
2012-09-16 12:22 ` Bart Van Assche [this message]
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=5055C473.5050401@acm.org \
--to=bvanassche-hinycgiudog@public.gmane.org \
--cc=alexne-VPRAkNaXOzVWk0Htik3J/w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.