xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@entel.upc.edu>
To: Mark <mark+lists@internecto.net>
Cc: xen-devel@lists.xen.org
Subject: Re: Xen scripts rewrite
Date: Fri, 2 Mar 2012 14:30:48 +0100	[thread overview]
Message-ID: <CAPLaKK4KvAbGzEneCFbg4s4bB+NG8ZoV-XXd-deWLoWZyp89yQ@mail.gmail.com> (raw)
In-Reply-To: <20120301124243.9B202298942@mx1.internecto.net>

2012/3/1 Mark <mark+lists@internecto.net>:
> Greetings,
>
> I am trying to wrap my head around the xen scripts in /etc/xen/scripts.
> I am currently looking at locking.sh but I don't really understand what
> it is doing.
>
> I see that claim_lock has a while loop, it seems to wait until it can
> write its own PID to $lockdir/owner. If the file $lockdir/owner exists,
> check if the pid is still running. If it's still running when the
> loop is done, steal the lock by writing $$ to $lockdir/owner anyway.
>
> Anyway. Can someone please further explain this file in plain English
> and detail. Am I right with my above assumptions, and when are locks
> even used?
>
> As said, I request as much detail as possible - the rewrite is to
> improve efficiency, readability and user customisation. As it is now
> you have too much functions that confuse me silly.
>
> If I am succesful I will share the outcome, so there's an incentive if
> you need one.

If you can, could you also clean the scripts of bashisms? so all of
them use /bin/sh. Now some of them use /bin/sh and some use /bin/bash
and I don't really like to install bash just for launching some
hotplug scripts.

> Thank you,
> Mark
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

      parent reply	other threads:[~2012-03-02 13:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 12:38 Xen scripts rewrite Mark
2012-03-01 13:29 ` Mark van Dijk
2012-03-02 19:47   ` Ian Campbell
2012-03-01 13:35 ` Marek Marczykowski
2012-03-01 17:32   ` Mark
2012-03-01 17:50     ` Marek Marczykowski
2012-03-02 13:30 ` Roger Pau Monné [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=CAPLaKK4KvAbGzEneCFbg4s4bB+NG8ZoV-XXd-deWLoWZyp89yQ@mail.gmail.com \
    --to=roger.pau@entel.upc.edu \
    --cc=mark+lists@internecto.net \
    --cc=xen-devel@lists.xen.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).