usecase. Please elaborate what you are trying to
do.
"systemctl daemon-reexec"'s usecase is pretty simple so far: update
systemd from one version to the next, and thus make sure to run the
new version of the code.
"systemctl switch-root"'s usecase is pretty simple too: transition
r is
> it based on experience?
We had to pick something. And 16M should be more than enough, but
generally available. So far noone complained, we got no bug reports
that it is too much or too little.
Lennart
--
Lennart Poettering, Berlin
___
systemd-
s is documented in detail.
Please contact the kubernetes folks and ask them to follow the
documented interfaces.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
controls location of
> configuration files? For all I can tell such variable does not exist.
Whch configuration files precisely?
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
s is how systemd exposes its state. If you don't want to use that,
you won't get the state information.
Sorry,
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
lib). Not really user friendly and not
> possible to do with simple command.
Fetching files from /lib or /usr/lib? What precisely do you mean?
For such build-time params we expose systemd.pc as pkg-config file,
which has various paths as variables.
Lennart
--
Le
hat we've had since the sysvinit? And also when isolating I suppose.
Are you running systemd? If so, please get rid of "killproc". It will
interfere with systemd's service management.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel m
ure how this would related to iwd.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
shuts down, and systemd decides
> not to restart it. iirc, there was a list of pids that would NOT be
> killed at that stage... it appears that the pid for ssh.service isn't
> getting placed in that list. How did that work again?
What is "killprocs"?
Is something killing services behi
t disable lingering for the users in question
> > before running the dnf upgrade command? Not ideal but it's a workaround
> > as you asked!
>
>
> Yep I guessed that would be the only thing to do.
>
> How do I get a list of all users with linger enabled?
Look in the /va
stack in include files, but they all do it differently, hence we
can't really carry that upstream.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
lyze log-level debug" to turn on debug
logging in PID 1 any time.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
ger").
So what sessions are those? Or do you have lingering enabled?
Do you maybe have cronjobs for the user installed?
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Do, 29.10.20 17:55, Marcin Kocur (marcin2...@gmail.com) wrote:
> W dniu 26.10.2020 o 11:19, Lennart Poettering pisze:
> > > Is this intended? Should I report bug to systemd or sane? The scanner is
> > > connected to my PC all the time.
> > sane.
> >
> >
'm not sure about even that.
That is the correct way: check for the one "negative" action type
(i.e. "remove"), and run your rules on all the other action types,
i.e. on all "positive" action types. (Where "positi
nel bind/unbind mess the sane rules already were broken)
Also see the NEWS note on the upcoming systemd version 247:
https://github.com/systemd/systemd/blob/master/NEWS#L5
> Is this intended? Should I report bug to systemd or sane? The scanner is
> connected to my PC all
t; If I trigger the device manually with action "change", the variable is still
> not there, as per the rule.
Yeah, the rule is broken. udev rules should be written in a style that
a "change" event can be triggered any time, and the devices keep their
properties. Writing ru
> and this resulted in date 1.1.1970.
All RH-based distro have patched the time check out of e2fsck since a
long time. In particular in RTC-less systems it sounds like a very
poor idea to leave that in. The right fix is certainly to remove this
behaviour from fsck, and not to force an unnecessari
es that mean no there isn't and also that there should not be, or are you
> open to considering allowing a suppression mechanism similar to that
> available in rsyslogd?
Not a fan of such hacks. Fix the programs or filter during display,
don#t suppress at time of collectio
er.)
This is the stuff systemd-timesyncd does when initializing:
https://github.com/systemd/systemd/blob/master/src/timesync/timesyncd.c#L27
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https:
On Do, 22.10.20 11:47, Belisko Marek (marek.beli...@gmail.com) wrote:
> On Thu, Oct 22, 2020 at 10:52 AM Lennart Poettering
> wrote:
> >
> > On Mi, 21.10.20 22:13, Belisko Marek (marek.beli...@gmail.com) wrote:
> >
> > > Hi,
> > >
> > > I
rked and an
NTP fix could be acquired of course.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
rotected?
>
> i thought mprotect(PROT_EXEC) would get filtered
> with or without bti, is that not the case?
We can adjust the filter in systemd to match any combination of
flags to allow and to deny.
Lennart
--
Lennart Poettering, Berlin
___
t me know.
[An acceptable compromise might be to allow
mprotect(PROT_EXEC|PROT_BTI) if MDWE is on, but prohibit
mprotect(PROT_EXEC) without PROT_BTI. Then at least you get one of the
two protections, but not both. I mean, MDWE is not perfect anyway on
non-x86-64 already: on 32bit i386 MDWE prote
with this: it's a bit weird to alter the bits after
the fact. Can't glibc set up everything right from the begining? That
would keep both concepts working.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
m your PAM stacks? This smells like a
distro integration thing to me, might make sense to inquire your
distro maintainers about this.
Consider logging in, and using "loginctl" to check if your session is
properly recognized and tracked.
Lennart
--
Lennart Poettering, Berlin
_
f this doesn't work at login time there must be something borked with
your display manager, or possibly systemd-logind.
Which systemd version is this? Which distro? Which display manager?
Lennart
--
Lennart Poettering, Berlin
___
systemd-deve
<<<<<< NOW MY USER IS HERE
And?
It's still owned by the "scanner" group like before, which the line
three up shows you.
The extra ACL entry probably comes from some "uaccess" rule somebody
sets on the device. But I don#t now what rules you added or what sa
one I used for syslog? If not should there be
> one?
No.
> 2) Could resolved be changed so that this message is only emitted
> (say) once for every 100 or 500 times that the condition is
> detected.
We actually try hard to suppress
On Fr, 16.10.20 17:45, Lennart Poettering (lenn...@poettering.net) wrote:
> > 2. Debugging with "rd.udev.debug systemd.log_level=debug":
> > The same 10 HDD BTRFS volume with 4 drives connected to the motherboard
> > and 6 drives connected to the HBA *fails* to
On Fr, 16.10.20 16:26, Daniel J. R. May (daniel@danieljrmay.com) wrote:
> On Fri, 2020-10-16 at 15:16 +0200, Lennart Poettering wrote:
> > So the btrfs ready ioctl is called and the device considered by the
> > kernel btrfs implementation to be ready
> > (i.e. assembl
d retriggering of udev
rules you might see this more than once per device.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
roblem supposed to be be?
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
/sysroot/ → /.
> Anyway I'm mainly confused why the btrfs udev rule is seemingly not
> applied in this case.
For historical reasons udev log level is independent from the rest of
systemd log level. Thus use udev.log_priority=debug to turn on udev
debug logging.
Lennart
--
Lennart Poette
slice /user.slice/user-$UID.slice/ and
then below that further cgroups for the sessions of the user, and the
user services and so on.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists
ing the level of expertise you
need to participate even higher by requiring them to use a UNIX nerd
quality MUA.
Hence, this is a pointless discussion. What people actually do
matters, and what the book says doesn't.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
the
main pid of a service however, verify that it points to the right
process. The "systemctl kill" line you are using really just then
sends a signal to that one process.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing li
On Mi, 30.09.20 13:57, Alan Perry (al...@snowmoose.com) wrote:
>
>
> On 9/23/20 9:29 AM, Lennart Poettering wrote:
> > On Di, 22.09.20 10:06, Alan Perry (al...@snowmoose.com) wrote:
> >
> > > > > device add events will get stuck at the probe step.
> >
argue with Linus' second-in-command about what Linux memory management
doesn't or does do.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
with fedora 28 is ancient, of course.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
artition table signatures off disk. If
things hang there, and the blkid prober worker process freezes then
this really looks like a hw/driver problem, i.e. IO access from the
block device just hangs.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mail
; system?
Have you checked the logs?
Please always start with saying which systemd version this is, and
which distro, otherwise it's very hard to grok what your setup is
like?
Maybe the eMMC driver has issues and simply hangs? dmesg might show
something in that case.
Lennart
--
Lennart Poettering, Ber
move", KERNEL=="ttyPS0", TAG+="systemd"
> >>
> >> should do it. Whether this should go upstream depends on how common
> >> this device is.
> >
> >
> > Well yes, but that should have been already covered by the existing
> > u
I need performance. My system
> generates a substantial amount of logs. I want to be able to store
> messages with an arrival rate of 10 000 messages per second at
> least.
The rsyslog maintainer doesn't like systemd very much. Much of what he
puts in the docs as big fa
any different
log sources that log at the same time).
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
e
*precise* character-by-character error message you saw?
It might be that the error code is actually generated by firmware, and
we just display it, which means we can't do much about this.
Either way, please provide the character-exact error message!
(A photo would do too)
bus this means all
dbus services are instantly considered to be down, and terminated if
they still have processes down.
Question is why your dbus daemon is shutdown, but given that the logs
you appended start too late this cannot be determined from your logs.
Lenna
u issue "systemd-analyze log-level debug" first, to
request debug output.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
ntainer(m, SD_BUS_TYPE_DICT_ENTRY,
> "oa{sa{sv}}") returns 0 which aborts the loop.
This does look correct to me.
> At this point I am not sure if sd_bus actually behaves correctly and
> GetManagedObjects() returns only one path or if I messed up the parsing of
> the reply so
the nspawn cmdline, to get
more verbose output. But output will generally suck if this is really
just a syscall/ioctl translation issue, you need to know what are you
doing if you want to track that down.
Lennart
--
Lennart Poettering, Berlin
___
systemd
or similar long-blocking syscalls from a thread
that also is supposed to run your bus connection then of course the
processing of the bus connection cannot take place then.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing lis
t; generally
requires /etc/symlink to be a readable symlink.
https://www.freedesktop.org/software/systemd/man/localtime.html
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Di, 08.09.20 17:35, Francis Moreau (francis.m...@gmail.com) wrote:
> On Mon, Sep 7, 2020 at 4:38 PM Lennart Poettering
> wrote:
> >
> > "React on the socket close?" — What do you mean by that?
> >
>
> I mean if my service explicitly calls close() the
rget
[Timer]
OnActiveSec=2min
[Install]
WantedBy=timers.target
This will enqueue the timer during early boot, but not actually
activate it until default.target has been reached. Then once active,
after 2mn the associated service is triggered.
Lennart
--
Lennart Poetteri
uld connect again. The system had
> been mostly idle and there were no upgrades since it booted up 2 days
> earlier. The previous ssh login attempt was 4 hours before.
It's a bug. Should be fixed by 86e045ecefc404d4fccbeb78aa212ec4714a5763.
id
> backing up broken configurations)?
What does "started successfully" mean to you?
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
links that change unit type
(i.e. the unit suffix after the dot) as aliases. It also doesn't
accept symlinks that change if a unit is templated or not. Objects
can't magically change their type, and they cannot suddenly
become/stop being templated or not.
Sorry,
Lennart
--
On Mo, 07.09.20 14:19, Kevin P. Fleming (ke...@km6g.us) wrote:
> On Mon, Sep 7, 2020 at 11:58 AM Lennart Poettering
> wrote:
> > Not sure I can parse this. Both timers and services are units in
> > systemd. You can enable timer units, and you can enable service units,
> >
rmally, you#d enter the array once and then iterate through the
dict entries contained therein. i.e. unless there's an "aa" object
somewhere (i.e. "array of array") you'd do the while loop around the
dict entries, not the array object.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
ave a different series of seqno on each boot, and it good
enough to compare log record order for recrods of the same boot, but
not of different boots.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.o
-support-for-filling-the-kernel-entropy-pool
The third point there: "The systemd-boot EFI boot loader included in
systemd is able to maintain and provide a random seed stored in the
EFI..."
Other boot loaders should be able to implement the same.
Lennart
--
Lennart Poettering, Berlin
ction of foobar.service, which
then means that if the service is enabled, foobar.timer is enabled
implicitly.
it really boils down to what you put in [Install]. And key really is
that timers are just *one* way to trigger a service, and the same
service might be triggered via a multitude
it up after forgetting about logind. Put all
> those devices into a non-default seat, override their file permissions,
> and assume they are untrusted (can be eavesdropped).
Note that I myself never worked on a wayland compositor or suchlike, I
have no experience with your perspective on these things: we
and do something.
Pet vs. cattle...
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
tion,
singular times. But doing so regularly on every single boot is
probably something to avoid, but boot counting would require that.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Sa, 05.09.20 18:46, Richard Hector (rich...@walnut.gen.nz) wrote:
> Hi all,
>
> Quoting from another thread:
>
> On 5/09/20 4:36 am, Lennart Poettering wrote:
> > Unit instances can be activated on-the-fly without further prepartion
> > or regsitration of the
On Mo, 07.09.20 18:04, Mantas Mikulėnas (graw...@gmail.com) wrote:
> On Mon, Sep 7, 2020 at 5:33 PM Lennart Poettering
> wrote:
>
> > On Mo, 07.09.20 13:51, Kai Hendry (hen...@webconverger.com) wrote:
> >
> > > Hi guys,
> > >
> > > After making
d that work for you? (Maybe we could even tweak this a bit in
systemd, so that when you invoke shutdown() on the socket systemd
holds for you we do not consider that a failure anymore, but a clean
way to tell systemd to stop the socket).
Lennart
--
Lennart Poettering, Berlin
_
; me know.
> https://github.com/systemd/systemd/issues?q=sd-encrypt
Hm?
>
> Sidenote: would be cool if a basic en.network could be generated.
Generated, from what? When?
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-de
On Sa, 05.09.20 09:49, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> 05.09.2020 01:05, Lennart Poettering пишет:
> >
> > I explained this already. DNS server data today is much less config
> > than state, acquired dynamically via DHCP, hence most distros don#t
> > c
ed are files called /home/$USER.home,
they contain a GPT partition table with a single partition as
mentioned above, of partition type
773f91ef-66d4-49b5-bd83-d683bf40ad16, and with a LUKS2 volume
inside. That LUKS2 volume needs to carry some extra metadata in its
he
On Mo, 24.08.20 01:24, Chris Murphy (li...@colorremedies.com) wrote:
> User reports this from 'homectl inspect'
>
> LUKS Discard: online=no offline=yes
>
> Does this mean 'fstrim' is issued before luksClose? And 'fallocate' is
> issued before luksOpen?
Yes.
Lennart
--
think this discussion kinda lost its usefulness, I am just repeating
myself, and will thus refrain from further input on this thread. If my
explanations aren't enough, aren't acceptable I think we both have to
live with that.
Lennart
--
Lennart Poettering, Berlin
_
xit-on-idle do not exist? A model like that is currently
not implemented. Can you elaborate on the usecase?
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Fr, 04.09.20 21:41, Dave Howorth (syst...@howorth.org.uk) wrote:
> On Fri, 4 Sep 2020 17:44:23 +0200
> Lennart Poettering wrote:
> > On Fr, 04.09.20 17:10, Reindl Harald (h.rei...@thelounge.net) wrote:
> >
> > > > No, that's not supported in sd-boot. A boot l
On Fr, 04.09.20 21:51, Dave Howorth (syst...@howorth.org.uk) wrote:
> On Fri, 4 Sep 2020 21:32:19 +0200
> Lennart Poettering wrote:
> > On Fr, 04.09.20 14:10, Shravan Singh (shra...@bluesparq.com) wrote:
> >
> > > Hello Lennart,
> > >
> > > C
is a very basic change one that needs to be
> supported by the system. Why guard it with so much.
We don't do that. Just make /etc/ writable ffs, if you want stuff in
/etc to be changable.
Lennart
--
Lennart Poettering, Berlin
___
systemd-de
al attention. But there are many other engineers in this
world, maybe you can find one that shares your priorities on this and
he will fix it for you. I am not going to be that, but at least I can
offer to review the patches and merge them if they are good.
Lennart
--
Lennart Poettering, Berlin
_
On Fr, 04.09.20 14:10, Shravan Singh (shra...@bluesparq.com) wrote:
> Hello Lennart,
>
> Can you help me in understanding why this push was rejected?
> *Make timedatectl nicely work with read-only filesystems #8277 *
The explanation is in the PR comments.
Lennart
--
Lennart Poette
resizing automatically.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
up".
Anyway, long story short: you typically do not enable services that
are only supposed to activated by timer units, enabling those timers
should entirely suffice, and the timers will start the services when
the time comes.
Lennart
--
Lennart Poettering, Berlin
___
s, e.g. both at boot
and regularly at some specific time.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
irectory name it was not
> properly found by the timer-triggered service run.
As mentioned this doesn#t have anything to do with timers or no
timers. The rule is just that the ".d/" must be append to the unit or
template name, i.e. after the ".service", as you noticed.
Lennart
iggred. i.e. if timer activated or activated as dep or
at boot should not matter at all.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
rate
timestamps we generate them when we flush that. So maybe that flushing
happens after the fake rtc thing?
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
me way as
/dev/urandom is kernel API /proc/sys/kernel/random/boot_id is kernel
API and we should rely on it to work and if it doesn't then it needs
to be fixed in the kernel.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@
bugreport.cgi?bug=963977
Umpf, that's a bad kernel bug. It suggests the boot_id is picked
before the random pool is fully initialized.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
es what fake-hwclock does automatically, and
also does SNTP. it should be fine for most usecases, no need to resort
to fake-hwclock)
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
lder versions of the
OS/kernel if it doesn't boot. Thus some form of write access is
necessary if you care about robustness.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
ample
Fedora does that since 2011:
https://bugzilla.redhat.com/show_bug.cgi?id=707917
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
lrwxrwxrwx 1 root root9 2020-08-24 12:47 systemd-userdbd.socket ->
> /dev/null
Well knock yourself out, but masking is not necessary, you can just
disable homed/userdbd/timesyncd if you don#t want it, and repart is
conditioned out anyway, so masking doesn't really get you much.
Lennart
--
L
where persistant configuration is supposed to be.
I am sorry, but /etc on Linux is a single directory, and you can only
cleanly choose between all configuration read only or none, there's no
nice way for a middle ground. Sorry.
Lennart
--
Lennart Poettering, Berlin
__
also interfering with received RAs?
we bind per interface, there should not be a conflict.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
e ones (i.e. Conflicts=).
Sorry,
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
in the status of "starting" the
> service when the core dump happened when stopping the service, and why isn't
> the original core dump message included as well?
I cannot parse this, and I cannot tell you how you configured your
syslog and why it shows less data.
Lennar
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
l
> ext4 partition or is it required that the kernel and initrd live on the
> EFI partition too?
No, that's not supported in sd-boot. A boot loader is a boot loader,
it should contain a fragile storage stack. It's kinda what sd-boot is
supposed to do better than grub.
Lennart
--
Lennart Poett
on XBOOTLDR and combine them.
XBOOTLDR is supposed to be used only if you have an existing ESP that
is too small to carry kernels, and you'd rather not resize it.
XBOOTLDR should be vfat too, as with sd-boot you still need an fs the
firmware can read.
Lennart
--
Le
ogind with some new concept, no suggestion. Or
simply bypassing logind and opening the devices directly with root
privs? or test this in virtualization?
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@
check if number of active sessions is > 0.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
701 - 800 of 8632 matches
Mail list logo
