Re: [systemd-devel] systemd unit checker tool
Hi On Tue, Apr 7, 2015 at 10:49 AM, Lennart Poettering wrote: > > We probably should add chekcs for these to "systemd-analyze verify" > even... Perhaps packaging guidelines should recommend running this command or it should be part of the macro that packages include that logs warnings when unit files has any of these issues Rahul ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] bandwidth per service
Hi I see device specific ones at http://www.freedesktop.org/software/systemd/man/systemd.resource-control.html I was wondering, whether it would be feasible to add bandwidth limits either by size or percentage for any particular service? squid, torrent daemons etc could use this. Rahul ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] newer systemd for rhel7/centos7
Hi On Fri, Nov 21, 2014 at 6:36 AM, Andrei Borzenkov wrote: > On Thu, Nov 20, 2014 at 9:10 PM, "Jóhann B. Guðmundsson" > wrote: > > > > Wont you break your RHEL support if you run this? > > > > Is not EPEL applicable to CentOS as well? > It is a misconception that installing a package by itself would break any support contracts in the first place and one that has been corrected multiple times. In addition to that, EPEL is applicable to rebuilds of RHEL including but not limited to CentOS and Scientific Linux. It is also easy enough to spin a new instance of RHEL without activating the subscription for the purpose of testing as well. Rahul ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] newer systemd for rhel7/centos7
Hi On Thu, Nov 20, 2014 at 11:24 AM, Lukáš Nykrýn wrote: > Hi, > > rhel7 / centos7 is shipped with heavily patched systemd 208, which does > not contain new interesting features and for us it is a backporting > nightmare. > > I have prepared an experimental repo with newer version of systemd for > epel7. > I don't mind doing that if the goal here is eventually rebase in RHEL/CentOS. If not, I won't be investing time on it Rahul ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] shared: fix cppcheck warnings
Hi On Mon, Oct 20, 2014 at 10:06 PM, Boris Egorov wrote: > Oh, you are right. This should probably be left as is. > It should be reported to cppcheck http://sourceforge.net/p/cppcheck/wiki/Home/ Preferably with a small test case. Ignoring false positives makes it harder to figure out when there is an actual issue. Rahul ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] logind: Support /etc/systemd/logind.conf.d/*.conf
Hi On Thu, Oct 16, 2014 at 6:27 AM, Josh Triplett wrote: > This makes it possible to drop in configuration file snippets from a > package or other configuration management mechanism. > Shouldn't those go into /usr according to http://0pointer.net/blog/projects/stateless.html Rahul ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] clarify what microsoft and oracle stands for
--- man/systemd-detect-virt.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/man/systemd-detect-virt.xml b/man/systemd-detect-virt.xml index 1e8230c..4f9980a 100644 --- a/man/systemd-detect-virt.xml +++ b/man/systemd-detect-virt.xml @@ -68,8 +68,8 @@ virtualization technology. The following technologies are currently identified: qemu, kvm, vmware, -microsoft, -oracle, xen, +microsoft (Hyper-V), +oracle (VirtualBox), xen, bochs, chroot, uml, openvz, lxc, -- 2.1.0 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-detect-virt and vendors
Hi On Wed, Oct 8, 2014 at 10:37 AM, Zbigniew Jędrzejewski-Szmek wrote: > This would break compatibility, because systemd-detect-virt would > have to start returning different strings. Ah, I was thinking more about ConditionVirtualization but I guess we are kinda struck with what we already have for command line use. I guess I will just send some patches to clarify things in the man page and add a --list command and leave the rest as it is? Rahul ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-detect-virt and vendors
Hi On Wed, Oct 8, 2014 at 9:46 AM, Lennart Poettering wrote: > > I think what would make a lot of sense though is to add a section to > the man page somewhere, that explains which ID refers to which > software from which vendor. Also, it might make sense to add a new > switch to the tool, that dumps the table of known identifiers plus > some description. > Fair enough. I will see if I can do that. Would it be ok to add appropriate aliases to existing terms, virtualbox - oracle and hyperv - microsoft and mark the vendor names as deprecated? That way we retain compatibility while having the consistency (this is more than just about being pretty!) that everything is named after the technology and not the mismash of vendors names (oracle, microsoft) and technology names (kvm...) in a list. I will write up some patches to see if I can implement this cleanly and we will see how it goes. Rahul ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd-detect-virt and vendors
Hi Bringing up here for discussion as suggested in https://bugzilla.redhat.com/show_bug.cgi?id=1150477 Just for the background, I was checking to see if systemd-detect-virt supported virtualbox and grepped the man page and concluded it didn't since I didn't find the term. I was going to write up a patch to support it but a recheck in the man page showed support for "oracle" and "microsoft". Grepping through the source, confirmed this actually means virtualbox and hyper-v respectively. Using vendor names like this is pretty confusing. Not everyone knows that say virtualbox is owned by Oracle (It was a startup, acquired by Sun which itself was acquired by Oracle) and worse still, Oracle supports multiple virtualization technologies included a variant of Xen rebranded as Oracle VM. We really should be more specific and call it virtualbox and hyper-v instead, similar to say virt-what and other similar tools. I will be happy write the patches if this makes sense. Rahul ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] note on relative symlink in os-release
--- man/os-release.xml | 12 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/man/os-release.xml b/man/os-release.xml index 4e02f80..b298304 100644 --- a/man/os-release.xml +++ b/man/os-release.xml @@ -90,11 +90,15 @@ files at the same time. /usr/lib/os-release is the recommended place to store OS release information as -part of vendor trees. Frequently, -/etc/os-release is simply a -symlink to /usr/lib/os-release, +part of vendor trees. +/etc/os-release should be a +relative symlink to +/usr/lib/os-release, to provide compatibility with applications only -looking at /etc. +looking at /etc. A relative +symlink instead of an absolute symlink is +necessary to avoid breaking the link in a chroot or +initrd environment such as dracut. os-release contains data that is defined by the operating system vendor and -- 2.1.0 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
