'tracepoint:syscalls:sys_enter_exec*{ printf("pid: %d, comm: %s,
args: ", pid, comm); join(args->argv); }'
to trace exec()s.
Although I see other executables being run, though nothing related to
systemd, I don't see systemd-cgroups-agent being run.
Thanks again for any ideas...
peace & happiness,
marti
Hi Mantas,
Yes, it looks like cgroups v1.
Would this be a kernel bug? systemd bug?
Thanks...
peace & happiness,
martin
On Wed, 11 Oct 2023 08:19:59 +0300, Mantas Mikulėnas
wrote:
> Is this with cgroups v1 or v2? If cgroups v1 is involved (thanks Docker), I
> recall it was a b
arting. It
does not send STOPPING=1. winbindd is much simpler during shutdown.
I can get logs for this one too if necessary.
Thanks for any help.
peace & happiness,
martin
and After are redundant, every standard service will be
ordered after local-fs.target unless it also has
DefaultDependencies=no.
My answer/question:
I want my service to be run DIRECTLY (at first place) AFTER the local
filesystems (in /etc/fstab) were mounted.
Martin.
--
Martin Stenzel (马丁-斯坦泽
striked
"RemainAfterExit", etc.
Is there any way I can see the whole process verbosely?
Martin.
--
Martin Stenzel (马丁-斯坦泽尔)
An der Drehscheibe 9
50733 Köln
Deutschland
-BEGIN PGP PUBLIC KEY BLOCK-
mDMEZHjlmRYJKwYBBAHaRw8BAQdAEr/C08aStyKx+vztCxz4Nn8BHO2Lx0O
-all'?
Thanks,
Martin
Am 29.04.23 um 18:20 schrieb Dan Nicholson:
For Endless OS we went the opposite way under the idea that we don't
want to have to go add an entry for every service that might get added
when the packages change. Basically we work under the assumption that
a package included
on firstboot on Debian.
What would you then suggest:
a. Disable every single service unit after copy to the
/lib/systemd/system location manually?
b. Add a 99-disable.preset file with 'disable *'? (I wonder why Debian
does not have it and if it then may brake something)
Thanks,
Martin
On Sat
Dear Paul,
Am 29.04.23 um 17:13 schrieb Paul Menzel:
Dear Martin,
Am 29.04.23 um 16:12 schrieb Martin Petzold:
we are building our OS with debootstrap (Debian bullseye). Our image
shall be flashed on embedded devices. In order to get a unique
machine-id we removed '/etc/machine-id
)
Custom Debian bullseye (with some packages from bullseye-backports)
Custom Kernel 5.10
U-Boot
[1] https://systemd.io/BUILDING_IMAGES/
[2] https://wiki.debian.org/MachineId
Thanks,
Martin
On 2023-03-24 20:01, Michal Koutný wrote:
> On Sun, Mar 19, 2023 at 07:16:56PM +0000, Martin wrote:
>> Any idea, what I might missing?
>
> Permissions?
> (Incresing logging verbosity may give you some hints. [1][2])
Thank you very much!
I'm not sure, if I will debug that, b
Dears,
I have a Debian 11 host with Debian 11 nspawn container, i.e. kernel
5.10.0-20 and systemd 247.3-7+deb11u1 on amd64.
My container.nspawn file contains, among others, the lines
[Exec]
PrivateUsers=false
[Files]
Bind=/sys/kernel/debug
The directory is populated on the host, but in the
have seen, that there is currently active work on those packages
(specifically systemd-resolved came up and was moved from systemd package).
We are also happy to give feedback on our test results and any bugs /
risks within our environment.
Thanks,
Martin
system to wait for /dev/ttyLXU0 to become available (via udev?).
>
Have you tried systemd.default_timeout_start_sec= ?
Martin
s acpi_index==1 and another one has index==1
(IIRC the first is derived from ACPI _DSM, the second from SMBIOS / DMI
type 41).
Martin
t is, I'd prefer it over other solutions simply because
it's more transparent. Capability bits tend to go unnoticed.
Martin
f you use CAP_SYS_ADMIN, you might as well use setuid. Same
argument - if you restrict the program properly, it comes down to
exactly the same thing that polkit would do, just far simpler.
Martin
en trigger aborted commands
> or UA's as well which will be picked up by the kernel/respected
> drivers.
Thanks a lot. I'm not quite certain which of these paragraphs would
apply to the situation I had in mind (administrator remapping an
existing LUN on a storage array to a different volume). That s
On Tue, 2021-04-27 at 16:41 -0400, Ewan D. Milne wrote:
> On Tue, 2021-04-27 at 20:33 +0000, Martin Wilck wrote:
> > On Tue, 2021-04-27 at 16:14 -0400, Ewan D. Milne wrote:
> > >
> > > There's no way to do that, in principle. Because there could be
> > > other
On Tue, 2021-04-27 at 16:14 -0400, Ewan D. Milne wrote:
> On Mon, 2021-04-26 at 13:16 +0000, Martin Wilck wrote:
> > On Mon, 2021-04-26 at 13:14 +0200, Ulrich Windl wrote:
> > > > >
> > > >
> > > > While we're at it, I'd lik
know
that WWID changes can happen with certain storage arrays. See
https://listman.redhat.com/archives/dm-devel/2021-February/msg00116.html
and follow-ups, for example.
Regards,
Martin
--
Dr. Martin Wilck , Tel. +49 (0)911 74053 2107
SUSE Software Solutions Germany GmbH
HRB 36809, AG Nür
s to react to the notification immediately, e.g. by
blocking IO to the device,
3) userspace tooling such as udev or multipathd need to figure out how
to how to deal with the situation cleanly, and eventually unblock it.
Wrt 1), we can only hope that it's the case. But 2) and 3) need work,
afaics.
On Thu, 2021-04-22 at 21:40 -0400, Martin K. Petersen wrote:
>
> Martin,
>
> > I suppose 99.9% of users never bother with customizing the udev
> > rules.
>
> Except for the other 99.9%, perhaps? :) We definitely have many users
> that tweak udev storage rules for a
Martin,
> I suppose 99.9% of users never bother with customizing the udev rules.
Except for the other 99.9%, perhaps? :) We definitely have many users
that tweak udev storage rules for a variety of reasons. Including being
able to use RII for LUN naming purposes.
> But we can actually c
On Wed, 2021-04-21 at 22:46 -0400, Martin K. Petersen wrote:
>
> Martin,
>
> > Hm, it sounds intriguing, but it has issues in its own right. For
> > years to come, user space will have to probe whether these attribute
> > exist, and fall back to the curr
Martin,
> Hm, it sounds intriguing, but it has issues in its own right. For
> years to come, user space will have to probe whether these attribute
> exist, and fall back to the current ones ("wwid", "vpd_pg83")
> otherwise. So user space can't be si
Hello Martin,
Sorry for the late response, still recovering from a week out of
office.
On Tue, 2021-04-06 at 00:47 -0400, Martin K. Petersen wrote:
>
> Martin,
>
> > The kernel's preference for type 8 designators (see below) is in
> > contrast with the established user sp
Martin,
> The kernel's preference for type 8 designators (see below) is in
> contrast with the established user space algorithms, which determine
> SCSI WWIDs on productive systems in practice. User space can try to
> adapt to the kernel logic, but it will necessarily be a slow a
ld start with making the "wwid" attribute
part of the udev rule logic, and letting distros configure whether the
kernel logic or the traditional udev logic would be used.
Please tell me your thoughts on this matter.
Regards,
Martin
PS: Incomplete list of algorithms for SCSI designator
Hi Lennart,
thanks again.
On Wed, 2021-01-27 at 23:56 +0100, Lennart Poettering wrote:
> On Mi, 27.01.21 21:51, Martin Wilck (mwi...@suse.com) wrote:
>
> if you want the initrd environment to fully continue to exist,
I don't. I just need /sys and /dev (and perhaps /proc and
s everything just fine (**). However, if I do
this, I end up in the real root file system, which is what I wanted to
avoid in the first place.
So, I guess I'll have to create bind mounts for /dev, /sys etc. in the
old root, possibly after entering a private mount namespace?
The other option wou
should not be required to
> maintain access to something you found.
True. But if udev ran without interruption, we could get rid of
coldplug after switching root. That could possibly save us a lot of
trouble.
Anyway, it's just a thought I find tempting.
Regrads
Martin
_
dolin:~/:[141]# systemctl show -p IgnoreOnIsolate nvme-monitor.service
IgnoreOnIsolate=yes
Tested only with systemd-234 so far. Any ideas what I'm getting wrong?
Martin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lis
On Mon, 2021-01-25 at 18:33 +0100, Lennart Poettering wrote:
> On Sa, 23.01.21 02:44, Martin Wilck (mwi...@suse.com) wrote:
>
> > Hi
> >
> > I'm experimenting with systemd's root storage daemon concept
> > (https://systemd.io/ROOT_STORAGE_DAEMONS/).
> >
>
;systemctl status"
would show the service as running even thought the instance inside the
root FS isn't actually running. I am unsure if all this can be achieved
easily with the current sytemd functionality, please advise.
I hope this makes a
On Thu, Oct 31, 2019 at 4:34 PM Lennart Poettering
wrote:
> On Di, 08.10.19 16:57, Martin Townsend (mtownsend1...@gmail.com) wrote:
>
> > Thanks for your help. In the end I just created a symlink from
> > /etc/machine-id to /data/etc/machine-id. It complains really
On Thu, Oct 17, 2019 at 4:55 PM Martin Townsend wrote:
>
> Hi,
>
> Does systemd support the networkd DHCP Server on multiple network
> interfaces. I ask as we have an embedded system running systemd 239
> and we want to configure a DHCP server on a bluetooth PAN and one
File: /etc/systemd/network/30-pan0-bridge.network
Type: bridge
State: routable (failed)
Driver: bridge
HW Address: 82:2f:45:2a:9c:5a
Address: 192.168.10.1
eth0 is named such that it should be configured before the pan0.
Best Regar
and the data partition is ready.
But the journal seems to be working ok and --list-boots is fine. The
initramfs would definitely be more elegant solution to ensure
/etc/machine-id is ready.
I don't suppose you know what requires /etc/machine-id so early in the boot?
Cheers,
Martin.
On Tue, Oct 8
disable the
/lib/systemd/system/systemd-machine-id-commit.service and create
/etc/machine-id myself using something like the MAC address and some
random numbers?
Cheers,
Martin.
On Mon, Oct 7, 2019 at 9:29 PM Mantas Mikulėnas wrote:
>
> Run both with SYSTEMD_LOG_LEVEL=debug in the envir
indices, debug hashmap, debug mmap cache, valgrind
Many Thanks,
Martin.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
temCallFilter" as a security measure and if one cannot
> rely
> on mechanisms any more, what good is such a feature?
Have you seen this? https://lwn.net/Articles/738694/
IMO this is a question related to seccomp design; "SystemCallFilter"
is just a convenient helper for using sec
st" doesn't work - unmasking must be done even if
"udev settle" fails or times out. "ExecStopPost" doesn't work either,
we don't want to run this when systemd-udev-settle.service is stopped
after having been started successfully.
See details below. Comments welcome.
Als
ome adventurous people even have it on NFS.
Martin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
the
documentation or ask on the mailing lists/forum of your firewall software.
Martin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
processes are still running. "lvm2-
monitor.service" runs "vgchange --monitor y". It almost looks as if
this had caused the devices to be visible by systemd, but that would be
wrong AFAICT.
Can you reproduce this with "udev.log-priority=debug"?
Regards,
be fixed (if anything). We can't change udev in this
regard. Too much code depends on the given semantics of ID_SERIAL.
Regards,
Martin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
s attributes in rules for "remove" events as errors in the first
place?
Regards,
Martin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
hem
is not (or unreliably) set on remove events, and thus causing your rule
not to be run. E.g. start with
ACTION=="remove", RUN+="..."
and then add the original conditions one by one.
Regards
Martin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
m your
problem description, I'd infer that this file system needs to be
mounted only at certain times (while the backup is running). My
suggestion would be to create a dedicated script (or systemd service,
for that matter) that would mount the file system, s
s system does not use an LVM partitioning.
fsfreeze should work without LVM. Of course you shouldn't be writing
tons of data to the file system while it's frozen, therefore LVM
snapshot + quick unfreeze would be more robust.
>
> > (I would just use `umount /var/backup`, however.)
Any comments from systemd devs on this issue? I'm particulary keen to
know if using the very permissive values on the /run/systemd/notify is
advisable or whether this would cause any security issues.
On Wed, Aug 1, 2018 at 6:46 PM Martin Townsend wrote:
>
> Hi Casey,
>
> Thanks
Hi Casey,
Thanks you for you prompt response.
On Wed, Aug 1, 2018 at 5:32 PM Casey Schaufler wrote:
>
> On 8/1/2018 3:18 AM, Martin Townsend wrote:
> > Hi,
> >
> > I have a service running with a SmackProcessLabel that uses the
> > supervisory watchd
re a better way of ensuring /run/systemd/notify can be accessed
by a service with a User defined SMACK label? or is this patch to
manager_setup_notify sufficient?
Many Thanks in Advance,
Martin.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
. Please advise.
For reference, I'm referring to the behavior documented in this bug
report: https://bugzilla.redhat.com/show_bug.cgi?id=1599658
Best Regards,
Martin Häcker
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.
eir journald deployments - should they want to retain more log messages.
Many thanks for your answers,
Martin Häcker
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
see my previous reply on the list.
Also, please don't cut away the https:// from links, this makes it impossible
to click on them.
Martin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
ps://github.com/systemd/systemd/commit/c92fcc4f4375b0
* My talk about it: https://www.youtube.com/watch?v=hq18daxTkLA
* Slides for the talk:
https://people.debian.org/~mpitt/systemd.conf-2016-graphical-session.pdf
Martin
signature.asc
Description
/cgroup/systemd: No such
file or directory
[!!] Failed to mount API filesystems, freezing.
systemd[1]: Freezing execution.
Many Thanks,
Martin.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman
eted
Jan 24 19:57:02 OS10 systemd[1]: Started Network Service.
Jan 24 19:57:02 OS10 systemd-networkd[3818]: vrf-test: netdev could not be
created: Operation not supported
Thanks,
Martin
___
systemd-devel mailing list
systemd-devel@lists.f
tact the Ubuntu bug tracker about this. These issues are not at all
related to upstream systemd development.
Martin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
My system: Ubuntu 17.04 , Linux 4.10.0-33, systemd 232-21ubuntu5
For a backup program, I wanted to prevent that the backup program is
interrupted by a suspend, sleep, hibernate oder shutdown which would cause
the backup to be destroyed. And if the backup runs automatically in the
background,
Yf$Z scheme,
which is actually just the BDF. The interface on my laptop is called
enp0s31f6 although the laptop doesn't have "slot 31". (1)
Martin
(1) Well, that's actually because the manufacturer saved the money to
implement the DMI BIOS correctly: there is even a DMI type 41 entry fo
em PCI slot numbers to
bus-device-function tuples. Obviously, the physical slot a controller
is connected to is less likely to change than the bus-device-function
number, so exposing it might make a lot of sense.
All of this requires support on the BIOS/Firmware side - without that,
none of the "p
ceTimeoutStartSec= setting might be OK to add...
Wouldn't this be, at least in part, be covered by using the newly
introduced "JobRunningTimeoutSec" for devices?
https://github.com/systemd/systemd/commit/db7076bf78bd8e466ae927b6d3ddf
64190c8d299
https://github.com/systemd/systemd/pull/5164
Martin
--
Dr.
Hello all,
quick announcement for things to watch out for in PR integration tests.
After Zbigniew's meson build system work landed two days ago [1], I now set up
our CI so that the "xenial-s390x" test builds using meson, while i386 and amd64
continue to run the classic autotools build. I
or the automount unit to be ordered before
> (and,
> if not noauto, be pulled in by) local-fs.target, even for network
> filesystems?
Please don't. We don't need additional failure points for local-
fs.target.
Martin
--
Dr. Martin Wilck <mwi...@suse.com>, Tel. +49 (0)911 74053 2
work, even if it's called right
after PID 1 is started. I'm pretty certain that that wasn't the case
for me. My client was running from an udev rule and thus not
unprivileged. That should be considered a bug, then?
My tests were done with systemd 228 a while ago.
Martin
--
Dr. Martin Wilck <m
of
systemd's service enablement logic).
Regards
Martin
--
Dr. Martin Wilck <mwi...@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
___
systemd-devel mailing list
systemd-d
Hello Lucas,
Lucas Ventura Carro [2017-03-07 9:25 +0100]:
> (1) Creating a symlink
> (2) Changing a kernel boot parameter
>
> But, using option (1) doesn't work, and I'm still having predictable names.
Did you rebuild the initrd after that? Without that, it won't work ind
>
> for you to fetch changes up to c05c6e9cedf20b64b22249f88af514a70b6edd4b:
>
> add LIB_ARCH_TUPLE for tilegx-linux-gnu (2017-02-27 16:21:06 +0100)
Imported into https://github.com/systemd/systemd/pull/5474
Thanks!
Martin
___
systemd
he device times out before the "last
resort" timer starts it (and before the last devices appear).
Martin
--
Dr. Martin Wilck <mwi...@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
___
uch other bells and whistles aside from busybox and udev) and it
works fine.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
___
systemd-devel mailing lis
writable.
> > > # systemctl status systemd.timesyncd
> > > * systemd.timesyncd.service
> > >Loaded: not-found (Reason: No such file or directory)
> > >Active: inactive (dead)
It's systemd-timesyncd (dash, not dot).
Viele Grüße,
Martin
--
Martin Pitt
; NTP synchronized: no
> RTC in local TZ: no
> DST active: n/a
I don't see an inconsistency? If timedated is not running then
timedatectl can't actualy talk to it and just shows values which it
can make up by itself.
Thanks,
Martin
--
Martin Pi
k in /etc
pointing to /dev/null. This is called "masking" and what "systemctl
mask" does, and is sort of a stronger version of "disable" (in the
sense that it will also not be started any more through Requires= and
friends).
Martin
--
Martin Pitt
get
about it). So IMHO the "(to the level the firmware permits this)"
qualification seems to adequately address that?
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
__
re if dangling symlinks should be counted as
"enabled", but this should least explain your observation.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
___
e it's just UI obfuscation, but perhaps label setting/removing
is limited to project members?
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
___
systemd-devel
st straightforward
way would be to tag or set a property on those devices which you want
to handle in libvirtd yourself, and then add something like
TAG=="libvirtd", GOTO="skip_selinux_context"
[... original rule that changes context goes here ..]
LABEL="skip_seli
On 29/10/16 22:20, Brian Kroth wrote:
> On Sat, Oct 29, 2016, 07:02 Reindl Harald <h.rei...@thelounge.net
> <mailto:h.rei...@thelounge.net>> wrote:
> Am 29.10.2016 um 13:37 schrieb Antoine Martin:
> > Just like "screen" or "tmux",
Hi,
Just like "screen" or "tmux", we want to ensure that some xpra sessions
(aka "screen for X11", VNC-like but seamless) can survive when the user
logs out.
Background: xpra runs X11 applications using an Xvfb server, when
client(s) are connected we forward the pixels/keyboard/mouse/etc.
Based
egression from 231, so we could easily move them
to 233. Should we?
Thanks for pushing this!
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
___
systemd-deve
ce units are mostly being used to know when the
corresponding mount units get started.
Anton Gerasimov [2016-09-20 11:37 +0200]:
> Yes, just adding 'KERNEL=="hda" TAGS+="systemd"' to udev rules did the
> trick. Thank you!
That means you are missing /lib/udev/rules.d/99-syste
uses systemd to never "see" it. We don't understand
the bug at all yet, nor are able to reproduce it with reasonable
effort.
Does your problem happen at every boot, or only sometimes? In the
former case it might actually not be a race condition but a more
systematic error, such as missi
temd/system-generators/ with a different name.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: PGP signature
___
systemd-devel mail
nce continues to
run after you log out of the graphical session, as long as that user
still has some other (non-graphical) session open.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian
d to apply transitively, and to Wants= as well, which sounds
quite strange). OTOH adding "PartOf=graphical-session.target" to all
graphical session specific user services works fine and works with the
existing systemd model and dependencies.
Martin
--
Martin Pitt
Martin Pitt [2016-07-07 9:29 +0200]:
> I'll go ahead and create a PR with the unit and a manpage, using
> graphical-session.target for now. Then the name bikeshedding can be
> continued there.
https://github.com/systemd/systemd/pull/3678
--
Martin Pitt
reate a PR with the unit and a manpage, using
graphical-session.target for now. Then the name bikeshedding can be
continued there.
BTW, I updated http://people.canonical.com/~pitti/tmp/session.sh to
have a kde.target as well, to demonstrate that this works with two
independent sessions.
Th
There is Alias= in the [Install] section, but this
cannot really be used for this purpose -- we don't want to change
the /usr/lib/systemd/user/user-graphical.target symlink every time
that we start a user session in a DM.
Hence my idea of a graphical.target user unit which would act like an
alias, as
Jóhann B. Guðmundsson [2016-07-06 14:02 +]:
> Martin is proposing changes to and dependency's on the graphical.target
I'm not changing anything. graphical.target as it exists in systemd
today is for the *system* instance. I'm talking about the *user*
instance, which has no graphical.tar
Martin Pitt [2016-07-06 13:47 +0200]:
> Simon McVittie [2016-07-05 10:27 +0100]:
> > Could this be done by having the .desktop file in /usr/share/xsessions
> > or /usr/share/wayland-sessions start an appropriate systemd user unit
> > directly, and wait for it to terminate?
&g
> There's also StopWhenUnneeded=, which might useful on the targets.
Indeed. The version 3 approach now uses that, and this finally works
as intended. Thanks for pointing out!
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Develop
Andrei Borzenkov [2016-07-06 14:44 +0300]:
> On Wed, Jul 6, 2016 at 2:25 PM, Martin Pitt <martin.p...@ubuntu.com> wrote:
> >$ cat .config/systemd/user/gnome-session.target
> >[Unit]
> >Description=User systemd services for GNOME graphical session
>
Simon McVittie [2016-07-05 10:27 +0100]:
> On 04/07/16 21:01, Martin Pitt wrote:
> > A session type like "GNOME" or "KDE" then defines which top-level
> > servcies it wants.
>
> Could this be done by having the .desktop file in /usr/share/xsessio
Martin Pitt [2016-07-06 13:47 +0200]:
> I have a gut feeling that this should be expressible with systemd
> dependencies -- i. e. "if gnome-session.service stops, then stop
> gnome-session.target". Naïvely this would be
> "PartOf=gnome-session.target" in gnom
t/stop the targets are
unaffected by this change; I'll follow up to Simon's reply about that).
So again, the only change we should do in systemd is to ship the
graphical.target user unit.
WDYT?
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Develope
ical.slice" any more which you can
refer to in units. We certainly don't want to use the root slice
(-.slice) as we don't want to kill *all* the user services on
graphical logout.
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
e
graphical-xfce.slice), and the whole Xsession gets wrapped into
starting/stopping the per-session-type slice [2].
It's still a prototype (work on this is postponed until end of July on
a sprint), but so far this works reasonably well.
Martin
[1] https://git.launchpad.net/~pitti/+git/systemd-grap
uot;?
Try adding a .service with "Type=idle" and add it to your default
target (usually multi-user.target). This should run the unit after the
system is booted (i. e. running or degraded).
(Tested here with systemd 230)
Martin
--
Martin Pitt| http://www.piware
1 - 100 of 535 matches
Mail list logo
