Openembedded Core Discussions
 help / color / mirror / Atom feed
From: <jackie.huang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/6] Add status command for LSB compliance for some packages
Date: Tue, 20 Aug 2013 11:25:40 +0800	[thread overview]
Message-ID: <cover.1376968627.git.jackie.huang@windriver.com> (raw)

From: Jackie Huang <jackie.huang@windriver.com>

test info:
MACHINE ??= "qemux86-64"
IMAGE_INSTALL_append = " at sysklogd"

$ bitbake core-image-sato

root@qemux86-64:~# /etc/init.d/atd status
/usr/sbin/atd (pid 580) is running...
root@qemux86-64:~# /etc/init.d/syslog status
syslogd (pid 695) is running...
klogd (pid 697) is running...
root@qemux86-64:~# /etc/init.d/nfsserver status
/usr/sbin/rpc.mountd (pid 685) is running...
nfsd (pid 683 682 681 680 679 678 677 676) is running...
root@qemux86-64:~# /etc/init.d/bootlogd status
/sbin/bootlogd is stopped
root@qemux86-64:~# /etc/init.d/dbus-1 status
/usr/bin/dbus-daemon (pid 704 589) is running...
root@qemux86-64:~# /etc/init.d/sshd status
/usr/sbin/sshd (pid 627) is running...

--
The following changes since commit 57662d4f813d5795cac1529633db80a09efdb089:

  meta-skeleton: Add busybox config fragment example (2013-08-13 23:03:44 +0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib jhuang0/r_status_for_daemons_0820_0
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=jhuang0/r_status_for_daemons_0820_0

Jackie Huang (6):
  dbus: add init.d/dbus-1 status command for LSB compliance
  sysvinit: add init.d/bootlogd status command for LSB compliance
  nfs-utils: add init.d/nfsserver status command for LSB compliance
  openssh: add init.d/sshd status command for LSB compliance
  sysklogd: add init.d/syslog status command for LSB compliance
  at: add init.d/atd status command for LSB compliance

 .../nfs-utils/nfs-utils/nfsserver                  |   25 ++++++++++++++++-
 .../openssh/openssh-6.2p2/init                     |   15 ++++++++++-
 meta/recipes-core/dbus/dbus-1.6.10/dbus-1.init     |    9 +++++-
 meta/recipes-core/sysvinit/sysvinit/bootlogd.init  |   28 +++++++++++++++++---
 meta/recipes-extended/at/files/S99at               |   13 ++++++++-
 meta/recipes-extended/sysklogd/files/sysklogd      |   13 ++++++++-
 6 files changed, 93 insertions(+), 10 deletions(-)

-- 
1.7.4.1



             reply	other threads:[~2013-08-20  3:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20  3:25 jackie.huang [this message]
2013-08-20  3:25 ` [PATCH 1/6] dbus: add init.d/dbus-1 status command for LSB compliance jackie.huang
2013-08-20  3:25 ` [PATCH 2/6] sysvinit: add init.d/bootlogd " jackie.huang
2013-08-20  6:39   ` Phil Blundell
2013-08-20  9:33     ` jhuang0
2013-08-20  3:25 ` [PATCH 3/6] nfs-utils: add init.d/nfsserver " jackie.huang
2013-08-20  6:36   ` Phil Blundell
2013-08-20  3:25 ` [PATCH 4/6] openssh: add init.d/sshd " jackie.huang
2013-08-22  6:42   ` Khem Raj
2013-08-22  7:02     ` jhuang0
2013-08-22  7:15       ` ChenQi
2013-08-20  3:25 ` [PATCH 5/6] sysklogd: add init.d/syslog " jackie.huang
2013-08-20  3:25 ` [PATCH 6/6] at: add init.d/atd " jackie.huang

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=cover.1376968627.git.jackie.huang@windriver.com \
    --to=jackie.huang@windriver.com \
    --cc=openembedded-core@lists.openembedded.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