Thanks for the information.
Is there any service in the existing standard distribution, where I can get
hands on these parameters ExecStartPre, ExecStart, ExecStartPost,
ExecReload, ExecStop, ExecStop, ExecMainCode, signal result and
ExecMainStatus under "Service Unit Objects".?
Unfortunately not
El 29/09/13 15:11, Lennart Poettering escribió:
> On Fri, 27.09.13 23:04, Kay Sievers ([email protected]) wrote:
>
>> On Fri, Sep 27, 2013 at 9:24 PM, Cristian Rodríguez
>> wrote:
>>> Distributions such as openSUSE and probably others never included
>>> upstart, in that case there is no need to inclu
---
units/systemd-fsck-root.service.in | 1 -
1 file changed, 1 deletion(-)
diff --git a/units/systemd-fsck-root.service.in
b/units/systemd-fsck-root.service.in
index 4388314..4162983 100644
--- a/units/systemd-fsck-root.service.in
+++ b/units/systemd-fsck-root.service.in
@@ -19,5 +19,4 @@ Type=
---
src/gpt-auto-generator/gpt-auto-generator.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/src/gpt-auto-generator/gpt-auto-generator.c
b/src/gpt-auto-generator/gpt-auto-generator.c
index ca54925..97b4742 100644
--- a/src/gpt-auto-generator/gpt-auto-generator.
---
src/fstab-generator/fstab-generator.c | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/src/fstab-generator/fstab-generator.c
b/src/fstab-generator/fstab-generator.c
index 6cecb4e..83aba7d 100644
--- a/src/fstab-generator/fstab-generator.c
+++ b/src/fstab-
FsckPassNo is listed as a compatibility option that shouldn't be used
in new units. Keeping compatibility with fstab's old fs_passno field
serves no particular purpose on a systemd system.
This patch series removes all usage of FsckPassNo from all generated
and shipped units:
* fstab-generator no
---
src/fstab-generator/fstab-generator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/fstab-generator/fstab-generator.c
b/src/fstab-generator/fstab-generator.c
index 9efccb9..6cecb4e 100644
--- a/src/fstab-generator/fstab-generator.c
+++ b/src/fstab-generator/fstab-gen
Am 29.09.2013 21:59, schrieb Lennart Poettering:
> On Sat, 28.09.13 16:35, Florian Klink ([email protected]) wrote:
>
>> Hi,
>>
>> I setup some freshly-bootstrapped Arch Linux containers using systemd
>> 204 (so only systemd inside, no old init systems)
>>
>> They are started using libvirt-lxc.
>> T
On Sat, 28.09.13 16:35, Florian Klink ([email protected]) wrote:
> Hi,
>
> I setup some freshly-bootstrapped Arch Linux containers using systemd
> 204 (so only systemd inside, no old init systems)
>
> They are started using libvirt-lxc.
> The root of the container filesystem is a mountpoint (in m
On Sun, 29.09.13 20:11, Andi Kleen ([email protected]) wrote:
>
> Hi,
>
> Is there a way to do the following in systemd?
>
> Run a program from the command line in a new cgroup container.
> After running output all the statistics accounted by cgroups,
> like CPU time, IO bytes, max memory usa
On Sun, Sep 29, 2013 at 03:37:30PM +0400, Andrey Borzenkov wrote:
> When crypttab contains noauto, cryptsetup service does not have any
> explicit dependencies. If service is started later manually (directly or via
> mount dependency) it will be stopped on isolate.
>
> mount units already have Ign
On Sun, Sep 29, 2013 at 08:11:53PM +0200, Andi Kleen wrote:
>
> Hi,
>
> Is there a way to do the following in systemd?
>
> Run a program from the command line in a new cgroup container.
> After running output all the statistics accounted by cgroups,
> like CPU time, IO bytes, max memory usage et
Hi,
Is there a way to do the following in systemd?
Run a program from the command line in a new cgroup container.
After running output all the statistics accounted by cgroups,
like CPU time, IO bytes, max memory usage etc.
Essentially like time(1), just using cgroups: systemd-time.
time does a
On Fri, 27.09.13 23:04, Kay Sievers ([email protected]) wrote:
> On Fri, Sep 27, 2013 at 9:24 PM, Cristian Rodríguez
> wrote:
> > Distributions such as openSUSE and probably others never included
> > upstart, in that case there is no need to include this code.
> >
> > This introduces --disable-upstar
On Sunday 2013-09-29 15:10, Dave Reisner wrote:
>On Sep 29, 2013 6:40 AM, "Jan Engelhardt" wrote:
>> On Thursday 2013-09-26 00:38, Tom Gundersen wrote:
>>
>> >+if [[ `basename $0` == 'installkernel' ]]; then
>>
>> Lack of quoting - bad bad bad.
>> Why not just write ${0##*/} ?
>
>Quoting doesn't m
On Sep 29, 2013 6:40 AM, "Jan Engelhardt" wrote:
>
> On Thursday 2013-09-26 00:38, Tom Gundersen wrote:
>
> >+if [[ `basename $0` == 'installkernel' ]]; then
>
> Lack of quoting - bad bad bad.
> Why not just write ${0##*/} ?
Quoting doesn't matter on the lhs here. Agree with the idiom in place of
When crypttab contains noauto, cryptsetup service does not have any
explicit dependencies. If service is started later manually (directly or via
mount dependency) it will be stopped on isolate.
mount units already have IgnoreOnIsolate set by default. Set it by
default for cryptsetup units as well.
On Thursday 2013-09-26 01:18, Mantas Mikulėnas wrote:
>> -cp --preserve "$KERNEL_IMAGE" "$BOOT_DIR_ABS/linux" || {
>> +cp "$KERNEL_IMAGE" "$BOOT_DIR_ABS/linux" &&
>> + chown root:root "$BOOT_DIR_ABS/linux" &&
>> + chmod 0600 "$BOOT_DIR_ABS/linux" || {
>
>How about `install -m 0600 -o root -g r
On Thursday 2013-09-26 00:38, Tom Gundersen wrote:
>+if [[ `basename $0` == 'installkernel' ]]; then
Lack of quoting - bad bad bad.
Why not just write ${0##*/} ?
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop
19 matches
Mail list logo
