Roger Qiu schrieb:
> I'm planning to use tmpwatch's `fuser` feature.
>
> But I'd prefer to run this simple service using systemd's tmpfiles.
> Does systemd tmpfiles support running `fuser` so that way it won't
> delete any files that have an open file descriptor?
>
> I couldn't see any mention
> Well, would that enable automatic, correcting routing between the
> container and the host's external network? That's kinda what this all
> is about...
>
> Lennart
>
In case we know, which interface provides the external network, it is also
possible to use proxy ndp
to give containers routea
Hello all,
I'm planning to use tmpwatch's `fuser` feature.
But I'd prefer to run this simple service using systemd's tmpfiles.
Does systemd tmpfiles support running `fuser` so that way it won't
delete any files that have an open file descriptor?
I couldn't see any mention of in the docs and s
On 18 Feb 2015, at 18:47, Lennart Poettering wrote:
> Hmm, this appears to be caused by a timer that is not reset. First the
> timer fd is set to the earliest possible trigger, then epoll_wait() is
> entered, which immediately quites. Then the tiemrfd elapse counter is
> read which is 1.
>
> It w
On Tue, Apr 28, 2015 at 07:25:34PM -0400, John Morrissey wrote:
> I noticed this behavior recently on a Debian jessie system running systemd
> 215-17. systemd got itself in a loop like the previous reporter's:
Aaaand of course I forgot the URL to the previous post:
http://lists.freedesktop.org/
Some distributions (such as Fedora) are using the VARIANT field to
indicate to select packages which of several default configurations
they should be using. For example, VARIANT=Server provides a
different default firewall configuration (blocking basically
everything but SSH and the management cons
On Tue, 28.04.15 20:33, Tobias Hunger (tobias.hun...@gmail.com) wrote:
> Hi Lennart,
>
> I only cared since it was blocking systemd 219 in arch. I never had
> any problem and assumed this was fixed since systemd 219 landed in
> Arch a while back.
OK, everyone who maintains this in distros, pleas
Hi Lennart,
I only cared since it was blocking systemd 219 in arch. I never had
any problem and assumed this was fixed since systemd 219 landed in
Arch a while back.
Best Regards,
Tobias
On Tue, Apr 28, 2015 at 5:48 PM, Lennart Poettering
wrote:
> On Sun, 12.04.15 17:58, Tobias Hunger (tobias.
Hello.
Based on a previous email that i sent to this list i wrote a python app
that notifies the user on the desktop about systemd logins, failed
systemd services, the status of some user defined services and also
monitors systemd files in /usr/lib/systemd and /etc/systemd/ directories
for modify,w
On Tue, 28.04.15 19:51, Benedikt Morbach (benedikt.morb...@googlemail.com)
wrote:
> On Tue, Apr 28, 2015 at 7:36 PM, Lennart Poettering
> wrote:
> > If eth1 shows up first, then it will be configured, and thus the local
> > ip forwaring turned off, the global is left untouched. Since the other
>
On Tue, Apr 28, 2015 at 7:36 PM, Lennart Poettering
wrote:
> If eth1 shows up first, then it will be configured, and thus the local
> ip forwaring turned off, the global is left untouched. Since the other
> interface hasn't shown up yet/has not been configured the global
> setting doesn't matter f
On Tue, 28.04.15 18:55, Benedikt Morbach (benedikt.morb...@googlemail.com)
wrote:
> this inevitably leads to race conditions and also means that IPForward=yes on
> one interface is equivalent to setting it on _every_ interface.
> (except when it isn't, see below)
>
> Suppose you have two network
this inevitably leads to race conditions and also means that IPForward=yes on
one interface is equivalent to setting it on _every_ interface.
(except when it isn't, see below)
Suppose you have two networks
* /etc/systemd/network/eth0.network
[Match]
Name=eth0
[Network]
Address=1
On Mon, 27.04.15 17:49, Christian Hesse (l...@eworm.de) wrote:
> > As for the actual lockup, I'm afraid I don't understand at all
> > what is happening (I'm anot familiar at all with how journald
> > interacts with other services and D-Bus/logind).
> >
> > So from my POV my best recommendation wo
On Sun, 12.04.15 17:58, Tobias Hunger (tobias.hun...@gmail.com) wrote:
> Hi Lennart,
>
> I just asked about the status of this, so I have links handy:
>
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811
> https://bugs.archlinux.org/task/44016
> https://bugs.debian.org/cgi-bin/bugr
On Fri, 03.04.15 14:58, Lennart Poettering (lenn...@poettering.net) wrote:
> systemd-fsckd would try to connect to some AF_UNIX/SOCK_STREAM socket
> in the fs, after forking and before execing fsck in the child, and
> pass the connected socket to fsck via the -C switch. If the socket is
> not conn
Daniel Mack wrote on 24/04/15 16:48:
> shutdownd was killed entirely. As a result, we have one less daemon
> lurking around, a nice DBus-API for something that used to be
> proprietary, and even less code:
>
> 20 files changed, 727 insertions(+), 905 deletions(-)
>
> However, this means that dir
On Tue, Apr 28, 2015 at 11:07:42AM +0200, Hans de Goede wrote:
> Like the T440s these need the sensitity to be set significantly higher
> then the default of 128 for the trackpoint to be usable. Like with the
> T440s 200 seems to be a good value to get a reasonable but not too high
> sensitivity.
A
Am 2015-04-28 11:33, schrieb Lennart Poettering:
On Tue, 28.04.15 16:19, 樊超 (fcvi...@gmail.com) wrote:
I want to let my service run when shutdown,and it needn't close by
systemd,so can i set the DefaultDependencies of [Unit] to "no"?
I don't understand the meaning of DefaultDependencies.
It's [U
On Tue, 28.04.15 13:49, Mantas Mikulėnas (graw...@gmail.com) wrote:
> On Tue, Apr 28, 2015 at 1:39 PM, Lennart Poettering
> wrote:
>
> > On Tue, 28.04.15 13:17, Mantas Mikulėnas (graw...@gmail.com) wrote:
> >
> > > > Moreover, when this is set up
> > > > the mount propagation from the user's nam
On Tue, Apr 28, 2015 at 1:39 PM, Lennart Poettering
wrote:
> On Tue, 28.04.15 13:17, Mantas Mikulėnas (graw...@gmail.com) wrote:
>
> > > Moreover, when this is set up
> > > the mount propagation from the user's namespace to the rest of system
> > > must be turned off for the root directory, and t
On Tue, 04.11.14 16:10, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
> Hi Lennart,
>
> Were you able to figure out the problem? You were suspecting that we
> might not be getting cgroup empty notifications from kernel.
Finally fixed in git! It was a race in systemd-run itself, not in PID 1.
On Thu, 23.04.15 12:08, Cam Hutchison (c...@xdna.net) wrote:
> Lennart Poettering writes:
>
> >On Thu, 23.04.15 06:58, Cam Hutchison (c...@xdna.net) wrote:
>
> >> The specifics of my logging that is temporarily volatile is captured in
> >> these rsyslog configs:
> >>
> >> local1.*
On Tue, 28.04.15 12:39, Alexandre Detiste (alexandre.deti...@gmail.com) wrote:
> Hi,
>
> I need a sponsor to upload an update of this package.
I figure this mail was supposed to go to some debian ML?
Lennart
--
Lennart Poettering, Red Hat
___
system
sorry, sent to wrong list !!
2015-04-28 12:39 GMT+02:00 Alexandre Detiste :
> I need a sponsor to upload an update of this package.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-d
On Tue, 28.04.15 13:17, Mantas Mikulėnas (graw...@gmail.com) wrote:
> > Moreover, when this is set up
> > the mount propagation from the user's namespace to the rest of system
> > must be turned off for the root directory, and this will break general
> > assumptions around mounting things through
Hi,
I need a sponsor to upload an update of this package.
Development has pretty much staled (both in Debian package
& upstream), as this is a rather empty shell that lets
systemd do all the hard , and it is pretty much "done".
Cheers,
https://anonscm.debian.org/cgit/collab-maint/systemd-cron.g
On Tue, 28.04.15 12:11, Michał Zegan (webczat_...@poczta.onet.pl) wrote:
> What if I will just make the / and similar mounts shared?
You have to turn off mount propagation for /tmp, so that the per-user
/tmp instance is not propagated to the rest of the system.
But after turning this off you ca
Lennart Poettering writes:
>On Thu, 23.04.15 06:58, Cam Hutchison (c...@xdna.net) wrote:
>> The specifics of my logging that is temporarily volatile is captured in
>> these rsyslog configs:
>>
>> local1.*/tmp/log/dnsmasq.log
>> local4.*/tmp/log/ld
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It may be possible, actually. Why oh why btrfs has no per user quotas?
this would be beneficial in some scenarios like this one.
W dniu 2015-04-28 o 12:17, Mantas Mikulėnas pisze:
> On Tue, Apr 28, 2015 at 1:06 PM, Lennart Poettering
> mailto:lenn...
On Tue, Apr 28, 2015 at 1:06 PM, Lennart Poettering
wrote:
> On Tue, 28.04.15 12:03, Michał Zegan (webczat_...@poczta.onet.pl) wrote:
>
> > (sorry, I haven't sent a reply to the list)
> > What about namespacing and mounting tmpfs per user? You can specify a
> > filesystem size when mounting tmpfs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What if I will just make the / and similar mounts shared? Well, I am
not entirely sure about this whole terminology, not sure if I
understand it. About x11, in case of gnome I think a second x server
is spawned to service a request in context of a sess
On Tue, 28.04.15 12:03, Michał Zegan (webczat_...@poczta.onet.pl) wrote:
> (sorry, I haven't sent a reply to the list)
> What about namespacing and mounting tmpfs per user? You can specify a
> filesystem size when mounting tmpfs can't you?
Well, you can set this up with some packages for individu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(sorry, I haven't sent a reply to the list)
What about namespacing and mounting tmpfs per user? You can specify a
filesystem size when mounting tmpfs can't you?
W dniu 2015-04-28 o 11:48, Michał Piotrowski pisze:
> Hi,
>
> 2015-04-28 11:39 GMT+02:00
On Tue, Apr 28, 2015, 11:38 AM Lennart Poettering
wrote:
On Tue, 28.04.15 09:31, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
> I started running Fedora server on a systemd-nspawn container.
>
> I am wondering what is the best practice when an issue occurs:
> - send to Fedora user ML
> - se
Hi,
2015-04-28 11:39 GMT+02:00 Lennart Poettering :
> On Tue, 28.04.15 00:55, Michał Zegan (webczat_...@poczta.onet.pl) wrote:
>
> > Hello.
> >
> > I have discovered how to add resource limits for the user, like how
> > much memory the user can use, or how much cpu time.
> > Here is the problem:
On Mon, 27.04.15 23:35, Kai Krakow (hurikha...@gmail.com) wrote:
> Hello!
>
> The man page reads:
>
> [MATCH] SECTION OPTIONS
>The network file contains a "[Match]" section, which determines if a
>given network file may be applied to a given device; and a
>"[Network]" sec
On Tue, 28.04.15 00:55, Michał Zegan (webczat_...@poczta.onet.pl) wrote:
> Hello.
>
> I have discovered how to add resource limits for the user, like how
> much memory the user can use, or how much cpu time.
> Here is the problem: /tmp seems a way for the user to circumvent this
> restriction. Is
On Tue, 28.04.15 09:31, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
> I started running Fedora server on a systemd-nspawn container.
>
> I am wondering what is the best practice when an issue occurs:
> - send to Fedora user ML
> - send to systemd-devel ML
> - send both with CC
>
> I am afra
On Tue, 28.04.15 16:19, 樊超 (fcvi...@gmail.com) wrote:
> I want to let my service run when shutdown,and it needn't close by
> systemd,so can i set the DefaultDependencies of [Unit] to "no"?
> I don't understand the meaning of DefaultDependencies.
> It's [Unit] like this:
> After=network.target netw
On Tue, 28.04.15 07:05, Peter Paule (systemd-de...@fedux.org) wrote:
> > Hmm, but that already lists a native config keyword for "stderr"?
> >
>
> Yes, I saw that too late. I copied the default configuration of the Arch Linux
> nginx package and used that.
So, does it work if you use the config
Like the T440s these need the sensitity to be set significantly higher
then the default of 128 for the trackpoint to be usable. Like with the
T440s 200 seems to be a good value to get a reasonable but not too high
sensitivity.
Signed-off-by: Hans de Goede
---
hwdb/70-pointingstick.hwdb | 10
I want to let my service run when shutdown,and it needn't close by
systemd,so can i set the DefaultDependencies of [Unit] to "no"?
I don't understand the meaning of DefaultDependencies.
It's [Unit] like this:
After=network.target network-online.target remote-fs.target
And I want to know if it matte
I started running Fedora server on a systemd-nspawn container.
I am wondering what is the best practice when an issue occurs:
- send to Fedora user ML
- send to systemd-devel ML
- send both with CC
I am afraid that when sending to only one list I will be told to ask
the other one, thus wasting ti
44 matches
Mail list logo
