All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2-utils: Add gfs2-cluster systemd unit
Date: Tue, 13 Dec 2011 14:23:24 +0000	[thread overview]
Message-ID: <1323786204.2725.7.camel@menhir> (raw)
In-Reply-To: <1323786024-6233-1-git-send-email-anprice@redhat.com>

Hi,

On Tue, 2011-12-13 at 14:20 +0000, Andrew Price wrote:
> Adds a systemd unit file to start gfs_controld at the correct point in
> the boot sequence. I've tested this as much as I can on Fedora 16 but it
> may require some more tweaking once the init scripts for cman, clvmd,
> etc. have been migrated. The gfs2 init script has not been migrated as
> systemd should now handle mounting of gfs2 file systems specially, after
> remote-fs-pre.target.
> 
> Signed-off-by: Andrew Price <anprice@redhat.com>
> ---
>  gfs2/system/gfs2-cluster.service |   12 ++++++++++++
>  1 files changed, 12 insertions(+), 0 deletions(-)
>  create mode 100644 gfs2/system/gfs2-cluster.service
> 
> diff --git a/gfs2/system/gfs2-cluster.service b/gfs2/system/gfs2-cluster.service
> new file mode 100644
> index 0000000..d6bc0ca
> --- /dev/null
> +++ b/gfs2/system/gfs2-cluster.service
> @@ -0,0 +1,12 @@
> +[Unit]
> +Description=GFS2 Control Daemon
> +After=syslog.target network.target cman.service
> +Before=remote-fs-pre.target
> +Wants=remote-fs-pre.target
> +
> +[Service]
> +Type=forking
> +ExecStart=/usr/sbin/gfs_controld $OPTIONS
> +
> +[Install]
> +WantedBy=multi-user.target

We probably don't need the $OPTIONS, but it will probably do no harm
either. Otherwise looks good,

Steve.




  reply	other threads:[~2011-12-13 14:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13 14:20 [Cluster-devel] [PATCH] gfs2-utils: Add gfs2-cluster systemd unit Andrew Price
2011-12-13 14:23 ` Steven Whitehouse [this message]
2011-12-13 14:36 ` Fabio M. Di Nitto
2011-12-13 14:41   ` Steven Whitehouse
2011-12-13 15:00   ` Andrew Price
2011-12-13 15:09     ` Fabio M. Di Nitto

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=1323786204.2725.7.camel@menhir \
    --to=swhiteho@redhat.com \
    /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.