All of lore.kernel.org
 help / color / mirror / Atom feed
From: Owen Synge <osynge@suse.com>
To: ceph-devel@vger.kernel.org
Subject: Re: autodetecting init system.
Date: Mon, 11 May 2015 19:28:03 +0200	[thread overview]
Message-ID: <5550E6A3.8000404@suse.com> (raw)
In-Reply-To: <5550D903.8000802@suse.com>



On 05/11/2015 06:29 PM, Owen Synge wrote:
> Dear all,
> 
> Many init systems are used in linux now. Some ceph code needs to know
> the init system. (I must admit I have not looked into Solaris, MacOS and
> BSD and probably should have)
> 
> It would be nice to have one function that detects the init system
> 
> Since the init system can be specified in ceph and ceph-deploy
> explicitly it seems to be its reasonable to fail clearly to detect init
> system.
> 
> I see 4 ways I can see to detect init system.
> 
> (A) Check pid 1.
> (B) Use a database of OS to init mapping / compile time.
> (C) look for init manipulation tools and infure the init system from tools.
> 
> Comments:
> ~~~~~~~~
> 
> (A1) systmd can be detected easily with.
> 
>  grep -qs systemd /proc/1/comm


A further comment is how will this work in chroot / containers?

> 
> (A2) With init scripts such as its hard to know what the init system.
> 
> (B1) For operating systems like RHEL, SLE, CENTOS, Fedora and scientific
> linux this works well.
> 
> (B2) FOr operating systems like newer debian and ubuntu releases more
> than one init system can be installed and used on the OS, so making a
> database / doing it at compile time are not practical on all OS's
> 
> (C1) This is fairly reliable.
> 
> (C2) sysV tools have compatibility scripts / programs on other platforms
> so if you use a points system for each init system helper script you can
> infure systemd over sysV if sytemctrl exists for example.
> 
> So to summarise this:
> ~~~~~~~~~~~~~~~~~~~~
> 
> (1) No one system is perfect in all cases.
> (2) Combined these systesm can provide reliable init system detection.
> 
> My proposed approach.
> ~~~~~~~~~~~~~~~~~~~~
> 
> (I) Use all three approaches where each approach can provide and answer,
> or fail to provide an answer.
> 
> (II) Should any approaches disagree -> fail to detect init system.
> 
> (III) Should all approaches agree -> then return init system.
> 
> (III) Should no approaches provide an init system -> fail to return init
> system.
> 
> Comments
> ~~~~~~~~
> 
> This multi layered and comparing way of doing init systems may seem
> complete overkill, or maybe its useful.
> 
> What do you guys think?
> 
> Best regards
> 
> Owen
> 
> 
> 
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-- 
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG
Nürnberg)

Maxfeldstraße 5

90409 Nürnberg

Germany
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-05-11 17:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 16:29 autodetecting init system Owen Synge
2015-05-11 16:37 ` John Spray
2015-05-11 17:26   ` Owen Synge
2015-05-11 17:34   ` Sage Weil
2015-05-12  7:25     ` Owen Synge
2015-05-11 17:28 ` Owen Synge [this message]
2015-05-11 21:45 ` Loic Dachary
2015-05-12  7:56   ` Owen Synge
2015-05-12  9:45     ` Loic Dachary
2015-05-12 10:27       ` Owen Synge
2015-05-12 12:34         ` Loic Dachary

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=5550E6A3.8000404@suse.com \
    --to=osynge@suse.com \
    --cc=ceph-devel@vger.kernel.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.