Hello all,
I've noticed that systemd-networkd.service (ordered Before=network.target)
finishes its startup before the connection is established/failed. Because of
this, some networking daemons ordered After=network.target (like openvpn) are
prone to failures when they attempt to connect at
Hi Ivan,
On Wed, Apr 2, 2014 at 11:41 AM, Ivan Shapovalov intelfx...@gmail.com wrote:
Hello all,
I've noticed that systemd-networkd.service (ordered Before=network.target)
finishes its startup before the connection is established/failed. Because of
this, some networking daemons ordered
On 04/02/2014 03:41 AM, Ivan Shapovalov wrote:
Hello all,
I've noticed that systemd-networkd.service (ordered Before=network.target)
finishes its startup before the connection is established/failed. Because of
this, some networking daemons ordered After=network.target (like openvpn) are
On Wed, Apr 2, 2014 at 3:22 PM, Matthew Monaco m...@0x01b.net wrote:
On 04/02/2014 03:41 AM, Ivan Shapovalov wrote:
Hello all,
I've noticed that systemd-networkd.service (ordered Before=network.target)
finishes its startup before the connection is established/failed. Because of
this, some
Hi,
I have recently switched to RHEL7. I had earlier written a sample service
script test_service.sh in the /etc/init.d folder and i used the usual
method
$/etc/init.d/test_service.sh start
to start the script and
$/etc/init.d/test_service.sh stop
to stop the script.
the service script
On Wed, Apr 02, 2014 at 07:12:57PM +0530, shubham sharma wrote:
Hi,
I have recently switched to RHEL7. I had earlier written a sample service
script test_service.sh in the /etc/init.d folder and i used the usual
method
$/etc/init.d/test_service.sh start
to start the script and
If a persistent timer has no stamp file yet, it behaves just like a normal
timer until it runs for the first time. If the system is always shut down
while the timer is supposed to run, a stamp file is never created and
Peristent=true has no effect.
This patch fixes this by creating a stamp file
Am 27.03.2014 23:41, schrieb Thomas Bächler:
On virtually any newer Asus mainboard, the eeepc-wmi driver is loaded.
It exposes a backlight device despite the lack of any physical backlight
devices. This fake backlight device has max_brightness set to 0. Since
the introduction of the
Systemd 212 defaults to remove all IPC (including SYSV memory) when a
user fully logs out.
Because the postgresql service does not count as a login, if you ssh
in as postgres (I'm rsycing wal files) and then logout. Systemd
removes the postgres SYSV memory bringing down postgres with fun
errors
Oh dear. Perhaps there's a way to use cgroups data to more selectively
do cleanup when there's overlap between regular users and service
users?
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
If the kernel is started with debug, that's for the kernel to switch
into debug mode. We should rely on a namespace for our options, like
everything else (with the exception of quiet). Some people want to
only debug the kernel, not systemd, and the opposite as well so make
everyone happy.
diff
On Wed, Apr 02, 2014 at 03:27:52PM -0700, Greg KH wrote:
If the kernel is started with debug, that's for the kernel to switch
into debug mode. We should rely on a namespace for our options, like
everything else (with the exception of quiet). Some people want to
only debug the kernel, not
If the kernel is started with debug, that's for the kernel to switch
into debug mode. We should rely on a namespace for our options, like
everything else (with the exception of quiet). Some people want to
only debug the kernel, not systemd, and the opposite as well so make
everyone happy.
diff
13 matches
Mail list logo
