similar to: [PATCH] appliance: run systemd-tmpfiles also for /var/run

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. 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:

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

https://bugzilla.redhat.com/show_bug.cgi?id=1165785 Since the --boot option is relatively new (added 2013-12), I suspect this will break older versions of systemd. However it should be fine for all currently supported versions of Fedora. Rich.

lvmetad only works if the /run/lvm directory is created. It is normally created by systemd-tmpfiles, but prior to libguestfs 1.34 we didn't invoke systemd-tmpfiles to create directories under /run (fixed in upstream commit a6330e9d3af0f5286f1d53d909fd868387b67f69). If for some reason lvmetad does start, then LVM filtering will be broken (fixed in upstream commit

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

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

Hi, I have the following example: it ''should have a form with an action attribute'' do response.should have_tag( "form[action=?]", ''/users/1/machines/1/trouble_tickets'') end for a form like so: <% form_for( :trouble_ticket, :url => { :action => ''create'', :user_id => @machine.current_owner,

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

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)

Modern distributions are moving toward a common boot scheme called "The Boot Loader Specification". This patch enables syslinux's (vesa)menu.c32 modules to parse the drop-in files that are defined by this new specification. Link to The Boot Loader Specification: https://systemd.io/BOOT_LOADER_SPECIFICATION Link to demonstration bootdisk image (82MB gzipped):

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

Would some one help me for this question? thanks very much. On 2016?05?25? 14:18, Qiang Chen wrote: > 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

so, there no method to delete special files that below a directory? such as in the directory [root at chenqiang]# tree . ??? test_10d ??? test_20d 0 directories, 2 files [root at chenqiang]# ll total 8 -rw-r--r-- 1 root root 4 5? 20 19:14 test_10d -rw-r--r-- 1 root root 4 5? 10 19:15 test_20d So, I want to delete file test_20d, keep test_10d, how to do that? thx. On 2016?05?27? 02:12,

This is useful for debugging (but we can't print it unconditionally since we cannot run grep etc yet). It also allows us to identify when udevd is invoked so we can time it for boot analysis. --- appliance/init | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/appliance/init b/appliance/init index f6fe9b9..657943c 100755 --- a/appliance/init +++ b/appliance/init @@

On Sat, May 25, 2019 at 3:42 PM Sebastian Herbszt <herbszt at gmx.de> wrote: > > Gregory Lee Bartholomew wrote: > > Modern distributions are moving toward a common boot scheme called > > "The Boot Loader Specification". > > Which distributions are using this yet? > > > This patch enables syslinux's > > (vesa)menu.c32 modules to parse the

On Tuesday 29 March 2016 12:14:21 Richard W.M. Jones wrote: > 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

On 06/26/17 14:42, Timo Sirainen wrote: > On 26 Jun 2017, at 23.19, Marc Perkel <marc at perkel.com> wrote: >> Ever since 2.26 I haven't been able to upgrade. In fact the install locks up my server. >> >> I get into and infinite recursive loop where the config-guess program calls itself until the server locks up from overload. >> >> I'm running Centos

Jonathan Billings <billings at negate.org> writes: > On Oct 3, 2017, at 13:12, hw <hw at adminart.net> wrote: >> >> I?m using the packages from mariadb.org. The old version that comes in >> Centos isn?t recommended, and I need features only the newer versions >> provide. >> >> >> Lighttpd is from epel, and it has basically the same