similar to: [PATCH 0/2] appliance: When running systemd-tmpfiles, pass --boot

Commit a6330e9d3af0f5286f1d53d909fd868387b67f69 enabled /run for systemd-tmpfiles: while this works fine in most of the cases, there are few tmpfiles configurations that still references /var/run instead of /run. As result, include also /var/run in the systemd-tmpfiles execution. --- appliance/init | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appliance/init

Hi, this series improves the way LVM is used in the appliance: in particular, now lvmetad can eventually run at all, and with the correct configuration. Also improve the listing strategies. Changes in v2: - dropped patch #5, will be sent separately - move lvmetad statup in own function (patch #2) Thanks, Pino Toscano (4): daemon: lvm-filter: set also global_filter daemon: lvm-filter:

Setup the volatile /run in the appliance also with the tmpfiles configurations available. In particular, setting up correctly the lvm bits allow lvmetad to run. --- appliance/init | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appliance/init b/appliance/init index d440007..e678e42 100755 --- a/appliance/init +++ b/appliance/init @@ -88,7 +88,7 @@ machine_id=$(dd

Setup the volatile /run in the appliance also with the tmpfiles configurations available. In particular, setting up correctly the lvm bits allow lvmetad to run. --- appliance/init | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appliance/init b/appliance/init index d440007..e678e42 100755 --- a/appliance/init +++ b/appliance/init @@ -88,7 +88,7 @@ machine_id=$(dd

Hi, this series improves the way LVM is used in the appliance: in particular, now lvmetad can eventually run at all, and with the correct configuration. Also improve the listing strategies. Thanks, Pino Toscano (5): daemon: lvm-filter: set also global_filter daemon: lvm-filter: start lvmetad better daemon: lvm: improve filter for LVs with activationskip flag set daemon: lvm: list

v4: - Lots more analysis of the /init script and other parts. - Display a list of the longest to shortest activities. - Rebase on top of current head. Rich.

Read the content of /proc/cmdline using bash features, and use its [[ ... ]] expression to find texts in a variable. This shaves off 5 grep invocations. --- appliance/init | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/appliance/init b/appliance/init index f6fe9b9..8d662fa 100755 --- a/appliance/init +++ b/appliance/init @@ -75,7 +75,9 @@ $UDEVD --daemon

Hi, I have a KVM host running ubuntu 18.04 with libguestfs-tools version 1.36.13-1ubuntu3.3 installed from the Ubuntu's repo and when I try to use virt-cat for example on a VM it fails with: libguestfs: error: appliance closed the connection unexpectedly. > libguestfs: error: guestfs_launch failed. After doing "export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1" and running the

Currently when the appliance is booted we see warning messages like these ones: [/usr/lib/tmpfiles.d/systemd.conf:26] Failed to replace specifiers: /run/log/journal/%m [/usr/lib/tmpfiles.d/systemd.conf:28] Failed to replace specifiers: /run/log/journal/%m [/usr/lib/tmpfiles.d/systemd.conf:29] Failed to replace specifiers: /run/log/journal/%m They are apparently harmless, but are caused because

Tools could require the use of pseudo-terminals, so make sure we have /dev/pts available in the appliance. The "command" API already bind-mounts it when running commands, so this is the only bit needed. --- appliance/init | 2 ++ 1 file changed, 2 insertions(+) diff --git a/appliance/init b/appliance/init index e678e42..8be27a2 100755 --- a/appliance/init +++ b/appliance/init @@ -72,6

v1 was here: https://www.redhat.com/archives/libguestfs/2016-March/thread.html#00157 Not running the 'hwclock' command reduces boot times considerably. However I'm not sure if it is safe. See the question I posted on qemu-devel: http://thread.gmane.org/gmane.comp.emulators.qemu/402194 At the moment, about 50% of the time is consumed by SeaBIOS. Of this, about ⅓rd is SGABIOS

OS = Ubuntu 18.04 LXD container Samba version = 4.11.12 Repo = Louis' (many thanks) I recently upgraded from 4.10.14->4.10.17->4.11.12 Now the samba-ad-dc service fails with the following upon reboot: --- root at samba:~# systemctl status samba-ad-dc ? samba-ad-dc.service - Samba AD Daemon Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled; vendor preset: enabled)

Hi all, I use centos7 and don't want to use tmpwatch as well as crond. I have a question to use `systemd-tmpfiles-clean.service` with my custom configured file in `tmpfiles.d` to delete outdated files periodically in some log dir. I have a `tmpfiles.d` configured file in `/etc/tmpfiles.d` named `my_log.conf` in following contents. ``` #Type Path Mode UID GID Age Arg r

When converting from a single transaction to a linked list, I forgot to free the storage for each member of the list. Reported-by: Richard W.M. Jones <rjones at redhat.com> Fixes: 7f5bb9bf13f041ea7702bda557d9dd668bc3423a Signed-off-by: Eric Blake <eblake at redhat.com> --- I'm still not sure why 'make check' passes while 'make check-valgrind' fails for

On Thu, 23 May 2019, Stephen John Smoogen wrote: > I might actually be able to have a workable answer: > > alias drf='/usr/bin/df -x tmpfs' /usr/bin/df \ -x autofs -x binfmt_misc -x cgroup -x configfs -x debugfs \ -x devpts -x devtmpfs -x efivarfs -x hugetlbfs -x mqueue \ -x nfsd -x proc -x pstore -x rpc_pipefs -x securityfs \ -x selinuxfs -x sysfs -x tmpfs :-) --

Hey I wanted to try my hand at doing some GPU passthrough so on my ASUS M5A97 which in the pass worked with an older BIOS (but said BIOS had issues after S3 suspend) - but with a BIOS the PCI passthrough does not work. That is due to:: (XEN) IVHD Error: Invalid IO-APIC 0xff (XEN) AMD-Vi: Error initialization

Hello, I am running into problems with virt-builder on my Ubuntu-14.04 install. Please find the checklist below: 1. What are you trying to achieve? I'm trying to build a standard Ubuntu 14.04 disk image. 2. What exact commands did you run? I ran "virt-builder ubuntu-14.04" 3. What was the precise error/output of these commands? The process gets stuck indefinitely at

CentOS: 7.1.1503 I have a problem with systemd which somehow manages to fill /tmp up with a lot of files. These files obviously are from the Apache server and don't pose a problem per se. The problem is that these files don't get removed daily: du -hs systemd-private-* 7,7G systemd-private-mpg7rm 0 systemd-private-olXnby 0 systemd-private-qvJJ5o 0 systemd-private-Rs2nBv It was my

This is a patch to fix one annoyance of having rsync processes race: I usually keep our servers synced with the following script, run by cron. #!/bin/sh lockfile -r 2 -l 1000 /tmp/synchome.lock || exit 1 rsync -e ssh -avHP --delete zorro01:/home/\* /home >/dev/null rm -f /tmp/synchome.lock -- Sometimes my users (including myself) are in a hurry and syncronise files and directories in their

Test case adapted from Hu Zhang's RHBZ#1242853, thanks. --- tests/regressions/Makefile.am | 2 + tests/regressions/rhbz1011907-1165785.sh | 66 ++++++++++++++++++++++++++++++++ 2 files changed, 68 insertions(+) create mode 100755 tests/regressions/rhbz1011907-1165785.sh diff --git a/tests/regressions/Makefile.am b/tests/regressions/Makefile.am index c4f60ae..026987b 100644 ---