[systemd-devel] We are working on Secure Container Applications.

Daniel J Walsh dwalsh at redhat.com
Mon Jan 9 13:42:58 PST 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The idea is to run multiple instances of the same application within a
container.  For example multiple Apache servers.

I am working on a tool to create these containers, which will create a
service unit file.

# virt-sandbox-service create -e /usr/sbin/httpd httpd_sanbox
Created container dir /var/lib/libvirt/filesystems/httpd_sanbox
Created sandbox config /etc/libvirt-sandbox/httpd_sanbox.sandbox
Created unit file /etc/systemd/system/httpd_sanbox.service

One problem we see with this is when the httpd program gets updated,
it runs a systemctl reload httpd.service, to cause the httpd service
to restart.  We would like to get this reload command from systemd
also.

What do you guys think of adding something like the following to the
service unit?

ReloadRequest: httpd.service

Then anyone asking to reload the httpd.service would also cause the
httpd_sandbox.service to get the reload.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8LX2IACgkQrlYvE4MpobMoMQCgmwQoZvm68QzFw8iEwdOVD5/p
g3sAoNUB9Hb2YnD5M1Egj6zxj+1f31TL
=C4jm
-----END PGP SIGNATURE-----


More information about the systemd-devel mailing list