Although util-linux's fstab.d work has stalled, there is still systemd code
that needs porting to libmount. See Karel's last comment:
https://github.com/systemd/systemd/issues/12506
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
Hi,
SUSE has this nice white paper about systemd in SLE 12:
systemd in SUSE® Linux Enterprise 12
A kinder, gentler introduction from SUSE
https://www.suse.com/docrep/documents/huz0a6bf9a/systemd_in_suse_linux_enterprise_12_white_paper.pdf
It is a good candidate for "Publications" or "Manuals
Mantas Mikulėnas gmail.com> writes:
>
>
> I'd buy into it if vfat weren't so brittle – several times I had to use
syslinux in /boot because the ESP lost *both* kernels I had in it... "sync;
sync; unmount; mount; check" was part of my kernel update ritual for a
while. Maybe it's the Linux
Orion Poplawski cora.nwra.com> writes:
>
> Andrei Borzenkov gmail.com> writes:
> > 11.03.2016 00:11, Orion Poplawski пишет:
> > > Uoti Urpala pp1.inet.fi> writes:
> > >> On Thu, 2016-03-10 at 17:51 +, Orion Poplawski wrote:
> > >>> It appears that this is a trigger for this issue.
Karel Zak kzak at redhat.com writes:
The current implementation directly monitor /proc/self/mountinfo and
/run/mount/utab files. It's really not optimal because utab file is
private libmount stuff without any official guaranteed semantic.
[...]
Please update libmount requirement in
Daniel Drake drake at endlessm.com writes:
So, moments after sending 2 SIGTERMs, SIGKILL is sent to all gdm
processes. There does not seem to be any consideration of giving the
process some time to respond to SIGTERMs, nor the fact that I have
hacked gdm.service to have SendSIGKILL=no as an
Squid is known to be borked when running as a daemon (background):
http://bugs.squid-cache.org/show_bug.cgi?id=3826#c12
But still I am experiencing a difference between systemd's built in signal
delivery and systemctl kill.
# systemctl -l status squid.service
* squid.service - Squid Web Proxy
Kai Krakow hurikhan77 at gmail.com writes:
To check this, I've just pulled the original source from git and built it.
This is original upstream behavior, no special Gentoo thing. The fsck.btrfs
utility is just a shell script. It seems to originate from xfs-progs:
Bastien Nocera hadess at hadess.net writes:
Hey,
I've seen that Ubuntu recently added transparent support for trimming
filesystems on SSDs:
https://blueprints.launchpad.net/ubuntu/+spec/core-1311-ssd-trimming
and in the patch for util-linux:
