First of all, according to docs, `DeviceAllow` syntax is somewhat different
from what you have.
Second, you might want to check `DevicePolicy`, as now your unit has access
not only to `/dev/zero`, but also to four other devices.
And hm, I thought, those directives control access to device nodes. W
El Tue, 3 de Jun 2014 a las 11:18 PM, Mohit Agrawal
escribió:
Hi,
I want to block the device through the systemd cgroup so I have
created a below unit file
[Unit]
Description=mydevblock
[Service]
DeviceAllow=/dev/zero
ExecStart=/usr/bin/dd if=/dev/zero of=/root/file_1 bs=1M count=40
Restart
Hi,
I want to block the device through the systemd cgroup so I have created a below
unit file
[Unit]
Description=mydevblock
[Service]
DeviceAllow=/dev/zero
ExecStart=/usr/bin/dd if=/dev/zero of=/root/file_1 bs=1M count=40
Restart=always
[Install]
WantedBy=multi-user.target
As per my understan
Hi,
It seems networkd has acquired some right-justification in its logging.
Why? This is very strange.
$ journalctl -b -u systemd-networkd
-- Logs begin at Sun 2014-03-09 03:04:51 EDT, end at Wed 2014-06-04 00:40:26
EDT. --
Jun 04 00:34:13 logos systemd-networkd[582]:bond0: net
On Tue, Jun 3, 2014 at 5:31 PM, Djalal Harouni wrote:
> Currently just running: test/test-kdbus will trigger the BUG_ON()
> appended at the bottom.
>
> This is due to the test in check_domain_make() where we try to register
> the same domain twice line: 297, hence kdbus_domain_new() fails with
> -
On Tue, Jun 3, 2014 at 9:58 PM, Lennart Poettering
wrote:
>
> On Mon, 02.06.14 21:02, Tom Gundersen ([email protected]) wrote:
>
> > On Mon, Jun 2, 2014 at 8:47 PM, Reventlov
> > wrote:
> > > Since network files are applied to links whenever the links
> > > appear, how do systemd manage the "disappear
On Tue, Jun 3, 2014 at 8:58 PM, Lennart Poettering
wrote:
> On Mon, 02.06.14 21:02, Tom Gundersen ([email protected]) wrote:
>
>> On Mon, Jun 2, 2014 at 8:47 PM, Reventlov
>> wrote:
>> > Since network files are applied to links whenever the links
>> > appear, how do systemd manage the "disappearance"
On Mon, 02.06.14 21:02, Tom Gundersen ([email protected]) wrote:
> On Mon, Jun 2, 2014 at 8:47 PM, Reventlov
> wrote:
> > Since network files are applied to links whenever the links
> > appear, how do systemd manage the "disappearance" of a default route ?
>
> You can have several default routes, so
On Sun, 01.06.14 20:53, Rico Sagner ([email protected]) wrote:
>
> +static int property_get_machineid(
> +sd_bus *bus,
> +const char *path,
> +const char *interface,
> +const char *property,
> +sd_bus_message *rep
On Mon, 02.06.14 13:31, Simon McVittie ([email protected]) wrote:
> On 01/06/14 20:03, Mantas Mikulėnas wrote:
> > Out of curiosity, wouldn't the existing
> > org.freedesktop.DBus.Peer.GetMachineId() work here?
>
> In principle Peer.GetMachineId() returns the D-Bus machine ID
> /var/
On Sun, 01.06.14 22:03, Mantas Mikulėnas ([email protected]) wrote:
>
> On Sun, Jun 1, 2014 at 9:01 AM, Lennart Poettering
> wrote:
> >
> > On Sat, 31.05.14 18:21, Rico Sagner ([email protected]) wrote:
> >
> > Heya!
> >
> > I think that the two ids would probably be better exposed by PID 1
>
On Tue, 03.06.14 11:21, Łukasz Stelmach ([email protected]) wrote:
> It was <2014-06-01 nie 07:52>, when Lennart Poettering wrote:
> > On Fri, 30.05.14 12:45, Piotr Wilczek ([email protected]) wrote:
> >
> >> This patch adds posibility for journal to get process data from
> >> socket data
It was forgotten in b1e90ec515408aec2702522f6f68c4920b56375b
See https://bugs.freedesktop.org/show_bug.cgi?id=79582
---
src/shared/log.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/shared/log.c b/src/shared/log.c
index 9039db3..6f17705 100644
--- a/src/shared/log.c
+++ b/src/shared
Currently just running: test/test-kdbus will trigger the BUG_ON()
appended at the bottom.
This is due to the test in check_domain_make() where we try to register
the same domain twice line: 297, hence kdbus_domain_new() fails with
-EEXIST at line domain.c:289
Later on error path we clear the non-
On Tue, Jun 03, 2014 at 12:55:54PM +0200, Kay Sievers wrote:
> On Mon, Jun 2, 2014 at 5:57 PM, Djalal Harouni wrote:
> > Currently just running: test/test-kdbus will trigger the BUG_ON()
> > appended at the bottom.
> >
> > This is due to the test in check_domain_make() where we try to register
> >
Lennart Poettering on Fri, 2014/05/16 18:56:
> On Wed, 30.04.14 23:20, Christian Hesse ([email protected]) wrote:
>
> > 4. udev launches my executable 'ykfde'
> > 5. ykfde asks for a second password (second factor)
> > 6. user types second password on keyboard
> > 7. ykfde reveives second password an
Tom Gundersen on Fri, 2014/05/16 14:54:
> On Fri, May 16, 2014 at 12:24 AM, Lennart Poettering
> wrote:
> > On Wed, 07.05.14 08:22, Christian Hesse ([email protected]) wrote:
> >
> >> Hello everybody,
> >>
> >> currently it is not possible to create tun/tap device with networkd. Is
> >> this feature
On Tue, Jun 03, 2014 at 11:05:53AM +0200, Kay Sievers wrote:
> On Tue, Jun 3, 2014 at 10:58 AM, Michal Sekletar wrote:
>
> > Currently systemd-localed does conversions from X11 keymap to VConsole
> > keymap
> > and vice-versa. There was a request coming from Anaconda installer team at
> > Red
>
Hello,
I am working on system running in lxc container that use systemd.
On host user session (uid=5000) starts automatically but in container I have
following error message:
May 12 00:18:15 localhost user-session-launch[110]:
pam_systemd(login:session): Asking logind to create session: ui
On Sat, May 31, 2014 at 10:23 PM, Djalal Harouni wrote:
> Make sure that the credentials of the connection at creation time will
> last so the kdbus_policy_check_own_access() will work as expected.
Applied.
Thanks,
Kay
___
systemd-devel mailing list
sy
On Mon, Jun 2, 2014 at 5:57 PM, Djalal Harouni wrote:
> Currently just running: test/test-kdbus will trigger the BUG_ON()
> appended at the bottom.
>
> This is due to the test in check_domain_make() where we try to register
> the same domain twice line: 297, hence kdbus_domain_new() fails with
> -
On Mon, Jun 2, 2014 at 8:47 PM, Reventlov
wrote:
> Hello.
>
> Since network files are applied to links whenever the links
> appear, how do systemd manage the "disappearance" of a default route ?
>
> For example, let's say i have one wireless interface and one ethernet
> interface that are both up,
On Tue, Jun 3, 2014 at 11:37 AM, Tom Gundersen wrote:
> On Mon, Jun 2, 2014 at 2:09 PM, Patrik Flykt
> wrote:
>> On Fri, 2014-05-30 at 17:21 +0100, Tom Gundersen wrote:
>>> I'm wondering if the criterion should be to request broadcast if and
>>> only if we have not configured an IP address (I.e.
On Mon, Jun 2, 2014 at 2:09 PM, Patrik Flykt
wrote:
> On Fri, 2014-05-30 at 17:21 +0100, Tom Gundersen wrote:
>> I'm wondering if the criterion should be to request broadcast if and
>> only if we have not configured an IP address (I.e. only in
>> discovering, requesting and init-reboot), as that s
It was <2014-05-30 pią 14:13>, when Michal Sekletar wrote:
> On Fri, May 30, 2014 at 12:45:21PM +0200, Piotr Wilczek wrote:
>> This patch adds posibility for journal to get process data from
>> socket data (if available) instead of from procfs.
>>
>> Additionally a new procinfo structure is added
It was <2014-06-01 nie 07:52>, when Lennart Poettering wrote:
> On Fri, 30.05.14 12:45, Piotr Wilczek ([email protected]) wrote:
>
>> This patch adds posibility for journal to get process data from
>> socket data (if available) instead of from procfs.
>>
>> Additionally a new procinfo structur
On Tue, Jun 3, 2014 at 10:58 AM, Michal Sekletar wrote:
> Currently systemd-localed does conversions from X11 keymap to VConsole keymap
> and vice-versa. There was a request coming from Anaconda installer team at Red
> Hat which was about splitting this functionality to separate library.
>
> I am
Hello,
Currently systemd-localed does conversions from X11 keymap to VConsole keymap
and vice-versa. There was a request coming from Anaconda installer team at Red
Hat which was about splitting this functionality to separate library.
I am curious if other people would be interested in such librar
28 matches
Mail list logo