On Tue, Dec 24, 2013 at 02:19:36AM +0100, Philipp Kern wrote:
On 2013-12-23 13:15, Sergey B Kirpichev wrote:
[a potentially badly-phrased question]
...I don't think many continue to read your rant and take your
feedback seriously. Apart from those who already resonate with
your opinion. And
On Tue, Dec 24, 2013 at 05:47:05PM +0100, Tzafrir Cohen wrote:
On Tue, Dec 24, 2013 at 02:19:36AM +0100, Philipp Kern wrote:
On 2013-12-23 13:15, Sergey B Kirpichev wrote:
[a potentially badly-phrased question]
...I don't think many continue to read your rant and take your
feedback
You don’t want anything like these in your local init service. For such
tests you have Nagios, Icinga or similiar daemons. And they can do much
deeper checks, e.g. can you login into your webservice because your
database backend on a different server is available.
Once your monitoring
On 2013-12-23 13:15, Sergey B Kirpichev wrote:
You don’t want anything like these in your local init service. For
such
tests you have Nagios, Icinga or similiar daemons. And they can do
much
deeper checks, e.g. can you login into your webservice because your
database backend on a different
Hi Thorsten,
On Wed, Oct 30, 2013 at 04:05:48PM +, Thorsten Glaser wrote:
* Write scripts for one system and generate the other from it
or even
* Write ???Debian init declaration??? and let something take care
of generating an initscript and whatever the other systems
use out of it
On Thu, 31 Oct 2013 06:33:44 +0100 John Paul Adrian Glaubitz wrote:
two places where to place systemd service files. One is located
below /usr/lib/systemd which is the directory where service files
provided by the package are placed, and one is /etc/systemd where
your own, custom service files
On Thu, Oct 31, 2013 at 01:47:37PM +, Steven Chamberlain wrote:
And overriding the *entire* service file seems excessive if you wish to
override just one line of the package's service file.
You add a file /etc/systemd/system/xxx.service.d/yyy.conf with the following
contents:
[Service]
On Thu, 31 Oct 2013 06:33:44 +0100 John Paul Adrian Glaubitz wrote:
messed up custom code may end up rendering your whole system unusable
if you are smart enough to mess up an rm command. Just have a look
at this wonderful bug in upstart [1].
[1]
On Thu, Oct 31, 2013 at 02:04:24PM +, Steven Chamberlain wrote:
[1] https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/557177
This doesn't appear to be a bug in Upstart.
Strictly, no, but there was a surprising amount of resistance to adding
some boilerplate to that script to
On Thu, Oct 31, 2013 at 03:59:25PM +, Jonathan Dowland wrote:
On Thu, Oct 31, 2013 at 02:04:24PM +, Steven Chamberlain wrote:
[1] https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/557177
This doesn't appear to be a bug in Upstart.
Strictly, no, but there was a surprising
on Tue, 29 Oct 2013 15:08:01 -0700 Russ Allbery wrote:
However, I, as a packager, want to stop writing and maintaining SysV init
scripts because they're awful.
I didn't really expect this. I'd assumed until now that most
maintainers would be concerned that existing init scripts don't work
On Wed, 30 Oct 2013 15:10:16 +0100 Helmut Grohne wrote:
Furthering this thought leads to turning non-Linux ports
into derivatives as presented by others in this thread.
If packages are no longer required to provide SysV init scripts,
producing a non-Linux Debian derivative would at least entail
Steven Chamberlain dixit:
[…]
substitute Upstart here if you prefer), each package's maintainer could:
[…]
* Write scripts for one system and generate the other from it
or even
* Write “Debian init declaration” and let something take care
of generating an initscript and whatever the other
On Wed, 30 Oct 2013 16:05:48 +, Thorsten Glaser wrote:
* Write scripts for one system and generate the other from it
or even
* Write “Debian init declaration” and let something take care
of generating an initscript and whatever the other systems
use out of it
Perhaps an existing
On Wed, 30 Oct 2013 20:39:32 + Jonathan Dowland wrote:
[...] Debian without non-Linux ports prior to February
2011, [...]
That's only when a non-Linux Debian port (GNU/kFreeBSD) first became a
_release architecture_; it existed as a port since May 2003. Hurd has
been an official unstable
On Mon, 28 Oct 2013 19:38:09 -0700, Russ Allbery wrote:
Brian May br...@microcomaustralia.com.au writes:
My understanding is that init scripts will still be required for FreeBSD
and The Hurd.
I would not assume that. At least, I personally don't think that
switching to upstart or systemd
2013/10/29 Steven Chamberlain ste...@pyro.eu.org:
[...]
Just wondering, if systemd upstream cares only for Linux and that's
considered okay, might they also start dropping support for
architectures they stop caring about (or for commercial reasons)? Say
MIPS, s390, SPARC. In that case,
17 matches
Mail list logo
