In case of systemd has "_" label and run as root, if a service file
has "User=" option and the command line file has a special SMACK label
then systemd will fail to access to given file. SMACK label is ignored
for root uid processes. But if a service has a "User=" then systemd
will call setresuid()
Hi,
> What's the usecase for setting empty environment variables?
>
> JBG
I use it to pass along information in my generator:
"Environment=MAILTO=" means "don't send any mail in case of failure".
By the default the mail would be sent the to @localhost .
The support for this is already there,
I was playing around with systemd-nspawn and systemd-run. The latter doesn't
seem to let me run a command that solely exists on the container.
simple way of reproducing: drop a file foo into the container, then on the
host run
systemd-run -M mycontainer /path/to/foo
I expected this to run fo
在 2014年11月20日 星期四 21:35:05，Lukáš Nykrýn 写道：
> "Jóhann B. Guðmundsson" píše v Čt 20. 11. 2014 v 18:10 +:
> > On 11/20/2014 04:24 PM, Lukáš Nykrýn wrote:
> > > Hi,
> > >
> > > rhel7 / centos7 is shipped with heavily patched systemd 208, which does
> > > not contain new interesting features and f
Hi Lennart,
>> That's normal behavior in the case of a platform rfkill device and a
>> device-specific rfkill device. The platform rfkill functionality can
>> sometimes (often?) cut power to the device through BIOS and GPIOs, and
>> it will drop off the USB or PCI bus. But the device itself can
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
On Fri, 21.11.14 02:24, Vasiliy Tolstov (v.tols...@selfip.ru) wrote:
> 2014-11-20 15:22 GMT+03:00 Lennart Poettering :
> > Both LLMNR and mDNS are strictly per-link, they will not announce IP
> > addresses that are not on the very link that is used for traffic. That
> > means if you have eth0 then
On Thu, 20.11.14 19:56, Lukasz Stelmach (stl...@poczta.fm) wrote:
> I talked to the kernel guys at my office and they told me that it is
> quite usual (at least for USB devices, and my wlan and bt are USB)
> that devices are stopped and unregistered in the kernel before
> a system is suspended end
On Thu, 20.11.14 11:42, Greg KH (gre...@linuxfoundation.org) wrote:
> On Thu, Nov 20, 2014 at 03:50:43PM -0300, Cristian Rodríguez wrote:
> > El 20/11/14 a las 15:40, Lukasz Stelmach escribió:
> >
> > >
> > > $ ls /sys/class/rfkill/
> > > rfkill41 rfkill42
> > > $ systemctl -t device | grep rfk
On Thu, 20.11.14 13:34, Dan Williams (d...@redhat.com) wrote:
> That's normal behavior in the case of a platform rfkill device and a
> device-specific rfkill device. The platform rfkill functionality can
> sometimes (often?) cut power to the device through BIOS and GPIOs, and
> it will drop off t
On Thu, 20.11.14 17:23, Didier Roche (didro...@ubuntu.com) wrote:
> >a) make /etc writable before systemd is invoked. If you use an initrd
> >this is without risk, given that the initrd should really invoke
> >fsck on the root disk anyway, and there's hence little reason to
> >transiti
On Thu, 20.11.14 14:48, Martin Pitt (martin.p...@ubuntu.com) wrote:
> > Sounds resonable. But first, can you elaborate on the reason for 0700
> > rather than 0755?
>
> Mostly so that users on the host can't call suid root binaries in the
> container. If containers are restricted with selinux/appa
2014-11-20 20:34 GMT+01:00 Dan Williams :
> On Thu, 2014-11-20 at 14:56 +0100, Michael Biebl wrote:
>> I had some rather "interesting" experience with the rfkill service as well.
>> See [1]. Basically, running rfkill on one device, made the other device go
>> away.
>
> That's normal behavior in th
On 11/20/2014 08:18 PM, Iago López Galeiras wrote:
Empty environment variables in Environment= and EnvironmentFile= options
work.
What's the usecase for setting empty environment variables?
JBG
___
systemd-devel mailing list
systemd-devel@lists.free
2014-11-20 15:22 GMT+03:00 Lennart Poettering :
> Both LLMNR and mDNS are strictly per-link, they will not announce IP
> addresses that are not on the very link that is used for traffic. That
> means if you have eth0 then the hostname will be announced with eth0's
> set of addersses on it. If you h
intrigeri píše v Čt 20. 11. 2014 v 21:40 +0100:
> Lukáš Nykrýn wrote (20 Nov 2014 20:35:05 GMT) :
> > (is debian still using 208? :) ).
>
> Nope, we have v215 in Debian testing/sid :)
>
> Cheers!
> --
> intrigeri
> ___
> systemd-devel mailing list
> sys
Lukáš Nykrýn wrote (20 Nov 2014 20:35:05 GMT) :
> (is debian still using 208? :) ).
Nope, we have v215 in Debian testing/sid :)
Cheers!
--
intrigeri
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/
"Jóhann B. Guðmundsson" píše v Čt 20. 11. 2014 v 18:10 +:
> On 11/20/2014 04:24 PM, 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 p
---
src/test/test-unit-file.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/src/test/test-unit-file.c b/src/test/test-unit-file.c
index 03b3e25..f31a1bb 100644
--- a/src/test/test-unit-file.c
+++ b/src/test/test-unit-file.c
@@ -222,6 +222,9 @@ static void test_config_
Clarified commit message (thanks Koen Kooi)
Iago López Galeiras (2):
test: support empty environment variables in unit files
update TODO
TODO | 2 --
src/test/test-unit-file.c | 22 ++
2 files changed, 22 insertions(+), 2 deletions(-)
--
2.1.3
___
Empty environment variables in Environment= and EnvironmentFile= options
work.
---
TODO | 2 --
1 file changed, 2 deletions(-)
diff --git a/TODO b/TODO
index d4138fe..3e8d04c 100644
--- a/TODO
+++ b/TODO
@@ -191,8 +191,6 @@ Features:
* generator that automatically discovers btrfs subvolumes, i
Am 20.11.2014 um 21:10 schrieb Jóhann B. Guðmundsson:
On 11/20/2014 08:05 PM, Reindl Harald wrote:
your problem is that you have a hostile attitude against anybody not
doing like you want
No I dont.
- that's excatly the same as your well known fedora-devel posts "*we*
as QA" sounding like
On 11/20/2014 08:05 PM, Reindl Harald wrote:
your problem is that you have a hostile attitude against anybody not
doing like you want
No I dont.
- that's excatly the same as your well known fedora-devel posts "*we*
as QA" sounding like you are the "we" alone
Aha right like you should b
Am 20.11.2014 um 20:54 schrieb Jóhann B. Guðmundsson:
Personally I think it's illogical that Red Hat customer spending their
time and money paying Red Hat to ask them to test and tell them if
*their* product works
personally i think it's *the difference* between pure commercial
software and b
On 11/20/2014 06:48 PM, Reindl Harald wrote:
Am 20.11.2014 um 19:41 schrieb Jóhann B. Guðmundsson:
On 11/20/2014 06:27 PM, Reindl Harald wrote:
what you asked don't matter since this is a *developer list* and so no
place where a RHEL customer with support is expected to jump blindly
and try
On Thu, Nov 20, 2014 at 03:50:43PM -0300, Cristian Rodríguez wrote:
> El 20/11/14 a las 15:40, Lukasz Stelmach escribió:
>
> >
> > $ ls /sys/class/rfkill/
> > rfkill41 rfkill42
> > $ systemctl -t device | grep rfkill
> > sys-devices-pci:00-:00:1a.0-usb3-3\x2d1-3\x2d1:1.0-bluetooth-hci0-r
On Thu, 2014-11-20 at 14:56 +0100, Michael Biebl wrote:
> 2014-11-20 14:17 GMT+01:00 Lennart Poettering :
> > On Tue, 18.11.14 18:37, Łukasz Stelmach (stl...@poczta.fm) wrote:
> >
> >> Hi.
> >>
> >> Recently, after I had found an update for my BIOS, my desktop started to
> >> resume properly (befor
On 20.11.2014 14:17, Lennart Poettering wrote:
> On Tue, 18.11.14 18:37, Łukasz Stelmach (stl...@poczta.fm) wrote:
>
>> Recently, after I had found an update for my BIOS, my desktop started to
>> resume properly (before I could only suspend it). Kernel and systemd do
>> their jobs fine. But they s
El 20/11/14 a las 15:40, Lukasz Stelmach escribió:
>
> $ ls /sys/class/rfkill/
> rfkill41 rfkill42
> $ systemctl -t device | grep rfkill
> sys-devices-pci:00-:00:1a.0-usb3-3\x2d1-3\x2d1:1.0-bluetooth-hci0-rfkill42.device
>
> sys-devices-pci:00-:00:1a.7-usb1-1\x2d3-1
Am 20.11.2014 um 19:41 schrieb Jóhann B. Guðmundsson:
On 11/20/2014 06:27 PM, Reindl Harald wrote:
what you asked don't matter since this is a *developer list* and so no
place where a RHEL customer with support is expected to jump blindly
and try unsupported packages
Right which makes this
On 11/20/2014 06:27 PM, Reindl Harald wrote:
what you asked don't matter since this is a *developer list* and so no
place where a RHEL customer with support is expected to jump blindly
and try unsupported packages
Right which makes this not the place to ask for this either. ( should be
as
On 20.11.2014 18:57, Greg KH wrote:
> On Thu, Nov 20, 2014 at 12:05:23PM +0300, Andrei Borzenkov wrote:
>> On Thu, Nov 20, 2014 at 11:53 AM, Mantas Mikulėnas wrote:
>>> On Thu, Nov 20, 2014 at 5:40 AM, Andrei Borzenkov
>>> wrote:
The problem is, there no easy way to build device name fr
Am 20.11.2014 um 19:22 schrieb Jóhann B. Guðmundsson:
On 11/20/2014 06:12 PM, Reindl Harald wrote:
Am 20.11.2014 um 19:10 schrieb Jóhann B. Guðmundsson:
On 11/20/2014 04:24 PM, Lukáš Nykrýn wrote:
Hi,
rhel7 / centos7 is shipped with heavily patched systemd 208, which does
not contain new int
On 11/20/2014 06:12 PM, Reindl Harald wrote:
Am 20.11.2014 um 19:10 schrieb Jóhann B. Guðmundsson:
On 11/20/2014 04:24 PM, 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
night
Am 20.11.2014 um 19:10 schrieb Jóhann B. Guðmundsson:
On 11/20/2014 04:24 PM, 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 wit
On 11/20/2014 04:24 PM, 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. Currently it is b
On Thu, Nov 20, 2014 at 12:05:23PM +0300, Andrei Borzenkov wrote:
> On Thu, Nov 20, 2014 at 11:53 AM, Mantas Mikulėnas wrote:
> > On Thu, Nov 20, 2014 at 5:40 AM, Andrei Borzenkov
> > wrote:
> >>
> >> The problem is, there no easy way to build device name from rfkillN for
> >> BindsTo. May be add
On Thu, Nov 20, 2014 at 12:44:43PM +0100, Lennart Poettering wrote:
> Heya,
>
> Marco D'Itri was asking about a potential hackfest at FOSDEM 2015 in
> Brussels. I am all for it, but we'd really need somebody to organize
> it, i.e. find a room for us.
>
> Anyone volunteering for this?
>
> Harald
> Brussels. I am all for it, but we'd really need somebody to organize
> it, i.e. find a room for us.
>
> Anyone volunteering for this?
If nobody else steps up, I might do it, but I do have a very tight
schedule currently, so I would rather have someone else do it.
If somebody else does this and fo
Lennart Poettering wrote on 20/11/14 11:44:
> Heya,
>
> Marco D'Itri was asking about a potential hackfest at FOSDEM 2015 in
> Brussels. I am all for it, but we'd really need somebody to organize
> it, i.e. find a room for us.
>
> Anyone volunteering for this?
>
> Harald, any chance you can pic
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. Currently it is based on 217 from Fedora rawhide and final goal
Le 20/11/2014 13:45, Lennart Poettering a écrit :
On Wed, 19.11.14 09:45, Didier Roche (didro...@ubuntu.com) wrote:
Hey,
Some other topic related to "empty /etc" discussions: when preparing some
generic distro images, we are have the desire to ensure that all new
instances will get a different
strv_extend returns 0 in the case of success which means that
else if (bus_track_deserialize_item(&m->deserialized_subscribed, l) == 0)
log_warning("Unknown serialization item '%s'", l);
will be printed when value is added correctly.
---
src/core/dbus.c| 2 +-
src/core/manager.c | 2 +-
2014-11-20 14:17 GMT+01:00 Lennart Poettering :
> On Tue, 18.11.14 18:37, Łukasz Stelmach (stl...@poczta.fm) wrote:
>
>> Hi.
>>
>> Recently, after I had found an update for my BIOS, my desktop started to
>> resume properly (before I could only suspend it). Kernel and systemd do
>> their jobs fine.
Hey,
Lennart Poettering [2014-11-20 12:29 +0100]:
> > d /var/lib/containers 0700 - - -
> >
> > to tmpfiles.d/var.conf? I can also add this to the Debian tmpfiles.d
> > file, but it's not really Debian specific.
>
> Sounds resonable. But first, can you elaborate on the reason for 0700
> rathe
On Wed, 19.11.14 11:01, Jakub Filak (jfi...@redhat.com) wrote:
>
> +int get_process_environ(pid_t pid, char **environ) {
If this is really just about pushing this into the journal: the
journal is actually binary safe, we could just drop the data there
without escaping it. That said, it certainl
On Wed, 19.11.14 11:01, Jakub Filak (jfi...@redhat.com) wrote:
> /proc/[pid]/cwd and /proc/[pid]/root are symliks to corresponding
> directories
Looks good! Applied this one already! Thanks!
>
> The added functions returns values of that symlinks.
> ---
> src/shared/util.c| 39
On Wed, 19.11.14 11:01, Jakub Filak (jfi...@redhat.com) wrote:
> ---
> src/shared/util.c| 13 +
> src/shared/util.h| 4
> src/test/test-util.c | 17 +
> 3 files changed, 34 insertions(+)
>
> diff --git a/src/shared/util.c b/src/shared/util.c
> index 0166
On Thu, 20.11.14 06:40, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> В Tue, 18 Nov 2014 18:37:03 +0100
> Łukasz Stelmach пишет:
>
> >
> > After several suspend/resumes systemctl shows more than three dozens of
> > rfkill devices even though I've got only one BT and one WLAN.
> >
> > --8<---
On Tue, 18.11.14 18:37, Łukasz Stelmach (stl...@poczta.fm) wrote:
> Hi.
>
> Recently, after I had found an update for my BIOS, my desktop started to
> resume properly (before I could only suspend it). Kernel and systemd do
> their jobs fine. But they seem to have problem cooperating.
>
> For the
On Wed, 19.11.14 09:45, Didier Roche (didro...@ubuntu.com) wrote:
> Hey,
>
> Some other topic related to "empty /etc" discussions: when preparing some
> generic distro images, we are have the desire to ensure that all new
> instances will get a different /etc/machine-id file.
> As part of the emp
On Wed, 19.11.14 15:57, Vasiliy Tolstov (v.tols...@selfip.ru) wrote:
> > Note that link-local ipv6 addresses for the name resolution stuff
> > aren't fun to use in Linux right now, as the glibc NSS eats up the
> > scopeid, when a client wants to resolve a hostname and specifies an
> > address fami
On Wed, 19.11.14 14:31, Florian Koch (florian.koch1...@gmail.com) wrote:
> Hi,
>
> i try to a centos7 (bootstrapped with yum) system with systemd-nspawn
> (systemd-nspawn -D centos7 -b) on opensuse 13.2
> This works basically, but there are some problems:
>
> 1. remove pam_loginuid from /etc/pa
Hi
On Tue, Nov 18, 2014 at 12:17 PM, wrote:
> From: Philippe De Swert
>
> udev_monitor_enable_receiving() enables a udev_monitor to recieve
> events. If this fails, the worker here created most likely won't
> recieve any events and will probably not be very useful. So now
> we check if the even
Heya,
Marco D'Itri was asking about a potential hackfest at FOSDEM 2015 in
Brussels. I am all for it, but we'd really need somebody to organize
it, i.e. find a room for us.
Anyone volunteering for this?
Harald, any chance you can pick this up?
Last time we met at a hackcenter in Brussels which
On Thu, 20.11.14 10:32, Martin Pitt (martin.p...@ubuntu.com) wrote:
> Hello all,
heya,
> we just got a bug report [1] about the systemd-nspawn@.service not
> working very well by default:
>
> First, /var/lib/containers/ does not exist by default. To guard
> against information leaks or hard lin
> Op 19 nov. 2014, om 19:44 heeft Iago López Galeiras het
> volgende geschreven:
>
> with this file:
>
> [Unit]
> Description=Test empty variables
>
> [Service]
> Environment=TEST= TEST2=
> ExecStart=/bin/bash -c "env"
>
> [Install]
> WantedBy=default.target
>
> I get this output:
>
> Nov
Andrei Borzenkov wrote on 19/11/14 17:49:
> В Tue, 18 Nov 2014 16:22:18 +
> Colin Guthrie пишет:
>
>> Michael Biebl wrote on 18/11/14 15:55:
>>> 2014-11-18 16:30 GMT+01:00 Colin Guthrie :
Michael Biebl wrote on 18/11/14 15:09:
> 2014-11-18 15:59 GMT+01:00 Colin Guthrie :
>> Didie
Hello all,
we just got a bug report [1] about the systemd-nspawn@.service not
working very well by default:
First, /var/lib/containers/ does not exist by default. To guard
against information leaks or hard link attacks by users, this
directory should be 0700 by default. LXC does the same (/var/li
On Thu, Nov 20, 2014 at 11:53 AM, Mantas Mikulėnas wrote:
> On Thu, Nov 20, 2014 at 5:40 AM, Andrei Borzenkov
> wrote:
>>
>> The problem is, there no easy way to build device name from rfkillN for
>> BindsTo. May be additional format specifier that would query udev
>> database. Alternatively syst
On Thu, Nov 20, 2014 at 5:40 AM, Andrei Borzenkov
wrote:
> The problem is, there no easy way to build device name from rfkillN for
> BindsTo. May be additional format specifier that would query udev
> database. Alternatively systemd-rfkill can be changed to accept sysfs
> path directly.
>
You su
61 matches
Mail list logo
