On Wed, 25 Apr 2012 11:28:14 -0400, Martin Langhoff wrote:
> Apologies if this has been discussed -- a search through the archives
> didn't find anything.
>
> Reading the announcement of systemd v28...
>
> "At shutdown we no longer invoke "hwclock --systohc", i.e. do not write
> the system clock
Thank you very much to all.
2012/4/25 Bill Nottingham
> Antonio Trande ([email protected]) said:
> > $ systemctl status fedora-storage-init.service
> > fedora-storage-init.service - Initialize storage subsystems (RAID, LVM,
> > etc.)
> > Loaded: loaded
> (/usr/lib/systemd/system/fedora
This reverts commits d72238fcb34abc81aca97c5fb15888708ee937d3 and
f3accc08.
OLPC runs / as a bind-mount, so this must be remounted RO during
shutdown to avoid corruption.
As Lennert can't recall the exact reasons for making the shutdown
code skip bind mounts, revert to previous behaviour to solve
Antonio Trande ([email protected]) said:
> $ systemctl status fedora-storage-init.service
> fedora-storage-init.service - Initialize storage subsystems (RAID, LVM,
> etc.)
> Loaded: loaded (/usr/lib/systemd/system/fedora-storage-init.service;
> static)
> Active: active (exited) sin
Apologies if this has been discussed -- a search through the archives
didn't find anything.
Reading the announcement of systemd v28...
"At shutdown we no longer invoke "hwclock --systohc", i.e. do not write
the system clock back to the RTC. Why? In general there's not really a
reason to assume th
Hello all
We'd like to launch some processes in a private mount namespace so
that they can each use a limited amount of private hugepages without
running as root.
The idea was to use PrivateTmp=true to get systemd to call unshare for
us and then configure the service with:
PermissionsStartOnly=t
>
> Certainly that's what I've seen from:
> systemctl status fedora-storage-init.service
>
>
> fedora-storage-init.service - Initialize storage subsystems (RAID, LVM,
> etc.)
> Loaded: loaded (/lib/systemd/system/fedora-
> storage-init.service; static)
> ...
>
> See the word "static" ther
On Wed, 2012-04-25 at 09:46 +0100, Colin Guthrie wrote:
> 'Twas brillig, and Antonio Trande at 24/04/12 16:57 did gyre and gimble:
> > Thank for your elucidation. Another my question about the services.
> >
> > In particular the fedora-storage-init.service (together to
> > /fedora-storage-init-lat
On Wed, Apr 25, 2012 at 9:34 AM, Colin Guthrie wrote:
> Is there any defined strategy for tidying up the
> /tmp/systemd-namespace-* folders (other than /tmp on tmpfs)?
>
> Nothing seems to be shipped by default in the tmpfiles.d stuff and it
> should really be on service stop that this is cleanup
On Wed, Apr 25, 2012 at 01:34, Colin Guthrie wrote:
> Is there any defined strategy for tidying up the
> /tmp/systemd-namespace-* folders (other than /tmp on tmpfs)?
>
I posted a bug a while back on a serious implication of namespace directory
proliferation:
https://bugs.freedesktop.org/show_bug
'Twas brillig, and Antonio Trande at 24/04/12 16:57 did gyre and gimble:
> Thank for your elucidation. Another my question about the services.
>
> In particular the fedora-storage-init.service (together to
> /fedora-storage-init-late.service/ and /fedora-wait-storage.service /),
> according to sys
My company [1] uses systemd and Twisted extensively. To improve our service
deployment options, we sponsored Twisted support for systemd's socket
activation model. This capability has landed [2] and will appear in the
next Twisted release.
However, the proposed documentation [3] still needs some r
Hi,
Is there any defined strategy for tidying up the
/tmp/systemd-namespace-* folders (other than /tmp on tmpfs)?
Nothing seems to be shipped by default in the tmpfiles.d stuff and it
should really be on service stop that this is cleanup up anyway I believe.
Col
--
Colin Guthrie
gmane(at)coli
We have an issue with some of our configuration management tools where
daemon-reload and daemon-reexec are necessary for updated service units.
Unfortunately, running either briefly interferes with normal service
manipulation commands like start, stop, and restart. A tool running on the
wrong side
On Tue, 24.04.12 21:47, David Strauss ([email protected]) wrote:
> Mark Shuttleworth posted recently on Ubuntu sticking with Upstart [1]:
>
> "Rumours and allegations of a move from Upstart to SystemD are unfounded:
> Upstart has a huge battery of tests, the competition has virtually none.
>
On Tue, Apr 24, 2012 at 22:23, Kok, Auke-jan H wrote:
> Not unless they posted technical stuff, in which case it's possible they
> do not wish to share
> their findings.
>
Indeed, I'm particularly interested in technical stuff discussing
functionality gaps or theoretical criticism of the systemd
You can see what these services do by looking at
/lib/systemd/system/fedora-storage*.service
They load the fedora-* scripts in /lib/systemd.
For example, fedora-storage-init.service and
fedora-storage-init-late.service both run /lib/systemd/fedora-storage-init.
If you look at that file, you'll se
17 matches
Mail list logo
