Am 21.02.2014 04:41, schrieb Zbigniew Jędrzejewski-Szmek:
On Fri, Feb 21, 2014 at 04:00:10AM +0100, Jason A. Donenfeld wrote:
systemd-networkd seems to get started by default in 209. Why is this?
What if I don't want to use it to manage my networks? Why does it have
to be on by default?
I
Am 21.02.2014 16:44, schrieb Colin Guthrie:
'Twas brillig, and Reindl Harald at 21/02/14 08:45 did gyre and gimble:
Am 21.02.2014 04:41, schrieb Zbigniew Jędrzejewski-Szmek:
On Fri, Feb 21, 2014 at 04:00:10AM +0100, Jason A. Donenfeld wrote:
systemd-networkd seems to get started by default
Am 13.03.2014 20:54, schrieb Anand Neeli:
I have multiple systems, How do i forward logs from one system running
systemd-journald to another remote systems
journal service, so that all the logs are stored on a centralized machine.
that's not the job of journald and falls into the use-case
Am 18.03.2014 22:59, schrieb Usman:
I am trying to test some code with respect to my services setup. I have two
services, lets say service_a and
service_b. In service_a unit file I have this:
OnFailure=service_b
And from the man page for OnFailure unit I get this:
A space-separated
Am 20.03.2014 15:02, schrieb Kevin Wilson:
--prefix etc.
I assume you mean:
--prefix /etc
and not
prefix /etc
is it so ?
KW
no: http://en.wikipedia.org/wiki/Et_cetera
you don't want your binary tree in /etc
On Wed, Mar 19, 2014 at 10:44 PM, Zbigniew Jędrzejewski-Szmek
Am 12.02.2014 21:19, schrieb Lennart Poettering:
On Wed, 12.02.14 20:05, Reindl Harald (h.rei...@thelounge.net) wrote:
maybe systemd-upstream should consider slow down development
and spend more energy in quality and stability
Well, firstly, it's hardly your business how we spend our time
Am 05.04.2014 23:22, schrieb Zbigniew Jędrzejewski-Szmek:
The whole issue started with bug #76935: the original reporter was
seemingly unaware of available kernel commandline options, and his
comments fairly quickly degenerated to rude personal attacks. It's
something that one sees quite
Am 11.04.2014 03:01, schrieb Lennart Poettering:
Tradditionally on Linux this is done via login.defs, but I am
really not convinced this should be runtime configurable. I'd prefer to
detect the minimal normal UID at compile time, and then use that to
distuingish normal from system users
Am 11.05.2014 18:30, schrieb Alex B:
2014-05-11 20:09 GMT+04:00 Dave Reisner d...@falconindy.com:
On Sun, May 11, 2014 at 07:53:55PM +0400, Alexander Bashmakov wrote:
Issue was rised in this thread:
https://mailman.archlinux.org/pipermail/arch-general/2014-May/036162.html
Disclaimer:
I
Am 17.05.2014 22:02, schrieb Cristian Rodríguez:
El 17/05/14 14:56, Dave Reisner escribió:
On Sat, May 17, 2014 at 12:39:47PM -0400, Cristian Rodríguez
wrote:
This is the standard* way used to pass special linker/compiler
flags such as -fPIE and -pie
* Standard in the sense it is
Am 27.05.2014 20:14, schrieb Kirill Elagin:
The container usecase alone is already the reason why I am so very sure
I want this stuff, and that it needs to be in networkd, and just work. I
want this fully automatic, so that we can create a hundred of veth
tunnels, and
Am 06.06.2014 11:50, schrieb Florian Weimer:
On 05/05/2014 04:35 PM, Lennart Poettering wrote:
Hmm? Well, a virtualized OS has to trust the hypervisor, there's no way
around that.
I'm referring to this:
* This function will use the architecture-specific hardware random
* number
Am 06.06.2014 11:48, schrieb Jóhann B. Guðmundsson:
On 06/05/2014 05:00 PM, Lennart Poettering wrote:
I think it would make sense to recommend that packagers and upstream
packages adopt Restart=on-failure or Restart=on-abnormal (where the
former is not appropriate) for all long-running
touch /forcefsck leads in deprecated warnings but in fact at least
on Fedora 19 *you need it* because the fsck don't happen otherwise
for sure, the last reboot of the machine below complaind too
so why don't it happen at boot?
Jun 8 14:51:31 localhost
Am 09.06.2014 17:05, schrieb Colin Guthrie:
'Twas brillig, and Reindl Harald at 08/06/14 13:59 did gyre and gimble:
touch /forcefsck leads in deprecated warnings but in fact at least
on Fedora 19 *you need it* because the fsck don't happen otherwise
for sure, the last reboot of the machine
Am 09.06.2014 17:28, schrieb Leonid Isaev:
On Mon, Jun 09, 2014 at 10:48:31AM +0300, Leho Kraav wrote:
Date: Mon, 09 Jun 2014 10:48:31 +0300
From: Leho Kraav l...@kraav.com
To: Reindl Harald h.rei...@thelounge.net,
systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] How
Am 09.06.2014 21:26, schrieb Alexander E. Patrakov:
10.06.2014 00:57, Reindl Harald wrote:
Am 09.06.2014 20:45, schrieb Alexander E. Patrakov:
10.06.2014 00:04, Reindl Harald wrote:
Am 09.06.2014 17:05, schrieb Colin Guthrie:
'Twas brillig, and Reindl Harald at 08/06/14 13:59 did gyre
Am 09.06.2014 21:07, schrieb Leonid Isaev:
On Mon, Jun 09, 2014 at 08:08:43PM +0200, Reindl Harald wrote:
all the decades before crond did run fine, logs exactly what
you need to know if /var/log/secure and /var/log/crond
without writing *hundret thousands* loglines all day long
on machines
Am 09.06.2014 22:32, schrieb Leonid Isaev:
On Mon, Jun 09, 2014 at 09:19:20PM +0200, Reindl Harald wrote:
[...]
on our production infrastrcuture these messages would be
*a lot* more than all other logs summarized
*and* they are spitted to /var/log/messages to make things worst
But why
Am 10.06.2014 12:20, schrieb Lennart Poettering:
On Mon, 09.06.14 09:33, Leho Kraav (l...@kraav.com) wrote:
After upgrading systemd 208 - 212, every single cron job creates
this flood in systemd journal:
Can I quiet this down somehow?
The idea with the journal is that we log
Am 10.06.2014 18:01, schrieb Lennart Poettering:
On Tue, 10.06.14 13:24, Leho Kraav (l...@kraav.com) wrote:
On 10.06.2014 13:20, Lennart Poettering wrote:
On Mon, 09.06.14 09:33, Leho Kraav (l...@kraav.com) wrote:
After upgrading systemd 208 - 212, every single cron job creates
this flood
Am 13.06.2014 16:35, schrieb Cristian Rodríguez:
El 13/06/14 05:19, Jay D Bhatt escribió:
Thanks. I surely forgot to attach log.
Now you can find it attached.
Nope, there is no attached log in your message
because he sent the attachment one message before
and found it useful to drop
Am 23.06.2014 21:09, schrieb Vasiliy Tolstov:
2014-06-23 16:13 GMT+04:00 Lennart Poettering lenn...@poettering.net:
Both. mDNS is a very much a peer-to-peer system, hence all participants
tend to implement both sides.
I actually intend to make this useful enough so that we can use it for
Am 25.06.2014 14:43, schrieb Michael Olbrich:
This treats it similarly to networkd, resolved and others and it matches
what 90-systemd.preset does.
---
Makefile.am | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Makefile.am b/Makefile.am
index 4b292b2..bfef1c3 100644
---
Am 02.07.2014 02:20, schrieb Zbigniew Jędrzejewski-Szmek:
this is in some sense a continuation of the subject of xz compression
for coredumps.
I've been benchmarking systemd-journal-remote + nc upload speed on
some fake data in which the MESSAGE fields are a few kb, big enough to
trigger
the main question is *why* is it systemd's business?
that flags are generelly set at the distribution level
and in case of Fedora they can differ between archs
because each arch has it's own %{optflags}
the whole mess exists because upstream projects
don't leave their fingers from that flags at
Am 06.07.2014 21:47, schrieb Lennart Poettering:
BTW, have you checked whether reuseing the XZ context might make the XZ
more competitive?
please try a simple test compress 50 MB with XZ and GZ, LZO, LZ4
or BZIP2 - XZ is *magnitudes* slower in any case, there is simply
nothing to optimize - XZ
Am 08.07.2014 12:22, schrieb Jon Severinsson:
Am 06.07.2014 21:47, schrieb Lennart Poettering:
BTW, have you checked whether reuseing the XZ context might make the XZ
more competitive?
On Sun Jul 6 15:01:11 PDT 2014 Reindl Harald wrote:
please try a simple test compress 50 MB with XZ
Am 10.07.2014 16:59, schrieb Jóhann B. Guðmundsson:
On 07/10/2014 12:51 PM, Zbigniew Jędrzejewski-Szmek wrote:
An administrator might want to block a certain sysusers config file from
being executed, e.g. to block the creation of a certain user.
---
src/sysusers/sysusers.c | 2 ++
1 file
Am 20.07.2014 23:38, schrieb Colin Guthrie:
'Twas brillig, and Colin Guthrie at 20/07/14 22:31 did gyre and gimble:
Those defaults could be set from a compile time check of
login.defs too.
FWIW, at least here, /etc/login.defs is not readable by regular users so
any build system that builds
Am 21.07.2014 03:10, schrieb sur...@emailengine.net:
On Sun, Jul 20, 2014, at 05:31 PM, Zbigniew Jędrzejewski-Szmek wrote:
2. tell systemd to log less with 'systemd-analyze set-log-level notice'.
Won't that lower the log level 'into' the journal as well?
hopefully
I'm happy to have
Am 21.07.2014 15:18, schrieb Mantas Mikulėnas:
On Mon, Jul 21, 2014 at 1:41 AM, sur...@emailengine.net wrote:
2014-07-20T00:15:01.978142-07:00 core systemd[1]: Starting
Session 2 of user root.
2014-07-20T00:15:01.979526-07:00 core systemd[1]: Started
Am 22.07.2014 22:47, schrieb Colin Walters:
On Mon, Jul 21, 2014, at 09:43 AM, Lennart Poettering wrote:
I am pretty strongly against this. Making this administrator
configurable apepars very wrong, this really should be a decision for
the distribution vendor, and that's it.
You list one
Am 23.07.2014 12:47, schrieb Tom Gundersen:
I think the lease should be remembered and reused in this case.
In general, saving the lease to disk is probably not a good idea. We
would need to store it on /var, and we may need to start the DHCP
server before /var has been mounted. To the extent
conditions like below
* stop mysqld instance 1
* stop mysqld instance 2
* the services still flush data but systemctl already returned
* rsync both datadir
* corruption
Original-Nachricht
Betreff: race conditions after SIGTERM
Datum: Thu, 24 Jul 2014 12:42:51 +0200
Von: Reindl Harald
in case of a non-forking
daemon knows trustable when it is finished
Am 24.07.2014 13:24, schrieb Reindl Harald:
maybe that's a systemd thing
i know Fedora 19 has not a recent systemd but the question
remains if systemctl in case of Type=simple may act the same
way while stop a service
or
twice a day and is hence not relieable to reproduce
Am 25.07.2014 12:11, schrieb Reindl Harald:
and it happended again
how can it be that if i have running mysqld-instances as
Type=simple directly starting mysqld that it is not safe
after systemctl stop returns to rsync the datadirs
i had
Am 30.07.2014 12:22, schrieb Ansgar Burchardt:
while looking at how to convert sysvinit scripts to service files in
Debian, I noticed that some scripts do an additional sanity check during
the restart action. That is, they run an extra command to validate the
configuration and only restart
http://www.freedesktop.org/software/systemd/man/systemd.exec.html
such error messages caused by list all sort of options
without any information when they where introduced are
really annoying - the docs should clearly say the minimum
required systemd version and the more options are added
the
Am 30.07.2014 13:42, schrieb Ansgar Burchardt:
On 07/30/2014 13:26, Jóhann B. Guðmundsson wrote:
On 07/30/2014 10:22 AM, Ansgar Burchardt wrote:
Add an ExecRestartPre option in the [Service] section. These commands
are executed when a restart is requested, before the service is stopped.
If
Am 30.07.2014 13:58, schrieb Tom Gundersen:
On Wed, Jul 30, 2014 at 1:21 PM, Reindl Harald h.rei...@thelounge.net wrote:
http://www.freedesktop.org/software/systemd/man/systemd.exec.html
such error messages caused by list all sort of options
without any information when they where
Am 30.07.2014 14:19, schrieb Jóhann B. Guðmundsson:
On 07/30/2014 12:09 PM, Lennart Poettering wrote:
On Wed, 30.07.14 12:22, Ansgar Burchardt (ans...@debian.org) wrote:
while looking at how to convert sysvinit scripts to service files in
Debian, I noticed that some scripts do an additional
Am 30.07.2014 14:35, schrieb Jóhann B. Guðmundsson:
On 07/30/2014 12:02 PM, Reindl Harald wrote:
they don't
Perhaps not in your world which seems to differ from many
don't jump on that personal level
if you would have *read* really what you respond to and not
stop at the first two words
Am 30.07.2014 15:04, schrieb Jóhann B. Guðmundsson:
On 07/30/2014 12:34 PM, Reindl Harald wrote:
*how* should that both help in calling apachectl -t *before* stop the
service and in case of a error-repsonse keep it running?
ExecStartPre= takes care of the startup check as in the usecase
Am 30.07.2014 17:31, schrieb Zbigniew Jędrzejewski-Szmek:
Some of our man pages in section 3 partially have history, see e.g. [1].
I think having such information is very useful, but keeping it accurate
is harder then it might seem at first. For example look at
SocketUser/SocketGroup settings.
Am 31.07.2014 um 07:03 schrieb Jóhann B. Guðmundsson:
On 07/31/2014 12:16 AM, Colin Guthrie wrote:
I think the use case is pretty clear tho'. Config (or general machine
state) has transitioned from working to broken in the time since the
service was started and while it's really not a nice
Am 31.07.2014 um 02:41 schrieb Michael Biebl:
2014-07-30 14:34 GMT+02:00 Reindl Harald h.rei...@thelounge.net:
ExecStopPre would be better suited as the pre-restart check because
it would achieve the goal and also prevent stop a service until it's
configuration is fixed - that catchs cases
Am 04.08.2014 um 17:09 schrieb Lennart Poettering:
On Wed, 30.07.14 13:21, Reindl Harald (h.rei...@thelounge.net) wrote:
http://www.freedesktop.org/software/systemd/man/systemd.exec.html
such error messages caused by list all sort of options
without any information when they where
Am 14.08.2014 um 14:22 schrieb Lennart Poettering:
On Sun, 27.07.14 19:53, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
On Sat, Jul 26, 2014 at 02:46:05PM +0200, Reindl Harald wrote:
after that happend a few minutes ago systemd on F19:
https://bugzilla.redhat.com/show_bug.cgi?id
Am 14.08.2014 um 14:24 schrieb Lennart Poettering:
On Sun, 27.07.14 20:04, Reindl Harald (h.rei...@thelounge.net) wrote:
but that still don't explain why ExecStopPost=/usr/bin/true or
whatever ExecStopPost solves that and if it is not supported
why systemctl don't return after the one
Am 14.08.2014 um 19:51 schrieb Lennart Poettering:
On Thu, 14.08.14 21:38, Andrei Borzenkov (arvidj...@gmail.com) wrote:
Which is what we do. Except when you specify ExecStop= which basically
tells systemd that you want to do it instead. So there you go!
Those daemons I have seen are
Am 18.08.2014 um 15:19 schrieb Lennart Poettering:
On Mon, 18.08.14 12:45, Saket Sinha (saket.sinh...@gmail.com) wrote:
I have been working on systemd recently and was referring to articles
by Lennart Poettering for the same. However, I am not able to access
the articles
hosted at the below
Am 18.08.2014 um 15:27 schrieb Lennart Poettering:
And also I would like to see the full logs always by default.
Usually after lots of searching you find the offending log entry for
the error, only to find out you forgot to pass the right command
line options to journalctl and the important
Am 05.07.2013 19:16, schrieb cac...@quantum-sci.com:
For some years I've set up reverse SSH tunnels with a script, but when the
tunnels go down they do not recover.
I'd like to start and stop the tunnels using systemd.
A typical command looks like this:
/usr/bin/ssh -f -l sleeper -i
Am 05.07.2013 21:20, schrieb cac...@quantum-sci.com:
Reindl Harald:
oneshot is plain wrong if you have a long living prcoess
below a working unit to have a remote-server's ssh on localhost:10024
RestartSec=60 because so it survives reboots of the forwarded machine with
auto reconnect
Am 11.07.2013 22:36, schrieb David Lambert:
Thanks for your quick reply. I also notice a - preceding the target for
ExecStart target. How does this work and
where is it documented. Again very difficult to search :-[
the command is allowed to fail without failing the service
it's common for
Your use of sshfs# as a FUSE type is wrong -- you must use fuse.sshfs as
the fstype instead.
this simply wrong, this line below in /etc/fstab works day
and night from FC9 to Fedora 18 as well as curlftpsfs
mounts in /etc/fstab are starting with curlftpfs#
and *both* have fuse and nothing else
Am 12.07.2013 17:54, schrieb Dave Reisner:
On Fri, Jul 12, 2013 at 05:46:37PM +0200, Reindl Harald wrote:
Your use of sshfs# as a FUSE type is wrong -- you must use fuse.sshfs as
the fstype instead.
this simply wrong, this line below in /etc/fstab works day
and night from FC9 to Fedora 18
Am 12.07.2013 17:58, schrieb cac...@quantum-sci.com:
Reindl Harald:
Your use of sshfs# as a FUSE type is wrong -- you must use fuse.sshfs as
the fstype instead.
this simply wrong, this line below in /etc/fstab works day
and night from FC9 to Fedora 18 as well as curlftpsfs
mounts in /etc
Hi
i try to secure the Apache-Webserver (mpm-prefork) as much as possible
am i right that with the following settings in the systemd-unit after the
child-process
is forked with the apache user and the capabilities are reduced as below even
a
potential root exploit would have no success?
Am 25.07.2013 20:00, schrieb Lennart Poettering:
On Sat, 20.07.13 04:06, Reindl Harald (h.rei...@thelounge.net) wrote:
Hi
i try to secure the Apache-Webserver (mpm-prefork) as much as possible
am i right that with the following settings in the systemd-unit after the
child-process
Am 26.07.2013 12:03, schrieb Kay Sievers:
man/systemd.exec.xml | 7 +++
1 file changed, 7 insertions(+)
diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml
index c0e1d86..b78f255 100644
--- a/man/systemd.exec.xml
+++ b/man/systemd.exec.xml
@@ -77,6 +77,13 @@
Am 28.07.2013 11:06, schrieb Kai Hendry:
On 26 July 2013 04:17, Lennart Poettering lenn...@poettering.net wrote:
We generally generate warnings about invalid lines and proceed. Aftre we
parsed everything we then do a couple of checks whether a unit still
makes sense with the stuff that was
Am 02.08.2013 12:01, schrieb lux-integ:
thanks for your reply
Would you care to elaborate what PID1 is please?
https://www.google.com/search?q=PID1#sclient=psy-abq=PID1+linux
http://0pointer.de/blog/projects/systemd.html
signature.asc
Description: OpenPGP digital signature
Please pass 'fsck.mode=force' on the kernel command line rather than creating
/forcefsck on the root file system
please drop this deprectaion, it is disturbing and useless
if you want a forced fsck for *whatever* reason you do *not* want
to edit the grub-config and need to remove it after pass
Am 30.09.2013 15:31, schrieb Tom Gundersen:
On Mon, Sep 30, 2013 at 3:25 PM, Muhammad Shakeel
muhammad_shak...@mentor.com wrote:
I have been trying to convert a LSB initscript of a package into
corresponding systemd service fyile. Most init scripts are simple and
translating them into
Am 16.10.2013 19:22, schrieb Warpme:
On 10/16/13 7:02 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Oct 16, 2013 at 06:18:12PM +0200, Warpme wrote:
Hi,
I want to switch init system from SysV to systemd-196.
Sys is PXE booted disk-less appliance with rootfs based on overlayfs.
Currently I
Am 17.10.2013 14:59, schrieb Warpme:
On 10/16/13 9:46 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Oct 16, 2013 at 09:19:43PM +0200, Warpme wrote:
Maybe we should disable [re]mounting / by systemd at all?
All systemd does, is call 'mount -o remount /'. I have no idea how you end
up with a
Am 22.11.2013 03:04, schrieb salil GK:
Thanks a lot David
On 22 November 2013 06:44, David Timothy Strauss da...@davidstrauss.net
mailto:da...@davidstrauss.net wrote:
On Thu, Nov 21, 2013 at 4:57 PM, salil GK gksa...@gmail.com
mailto:gksa...@gmail.com wrote:
What happens is -
and different
threads are touching each other in a unexpected way
been there, died nearly in debug it and catch data for upstream
On Nov 22, 2013 7:50 PM, Reindl Harald h.rei...@thelounge.net
mailto:h.rei...@thelounge.net wrote:
Am 22.11.2013 03:04, schrieb salil GK:
Thanks a lot David
Am 06.12.2013 12:17, schrieb Cecil Westerhof:
On 12/06/2013 11:31 AM, poma wrote:
In 7th slide - Improvements - Only necessary kernel modules
How does it actually refers to systemd?
You do not need to have modules loaded that are not used much. They can be
loaded when a program that
Am 06.12.2013 12:38, schrieb Cecil Westerhof:
On 12/06/2013 12:30 PM, Reindl Harald wrote:
In 7th slide - Improvements - Only necessary kernel modules
How does it actually refers to systemd?
You do not need to have modules loaded that are not used much. They can be
loaded when a program
Am 06.12.2013 15:36, schrieb Cecil Westerhof:
On 12/06/2013 12:43 PM, Reindl Harald wrote:
Am 06.12.2013 12:38, schrieb Cecil Westerhof:
On 12/06/2013 12:30 PM, Reindl Harald wrote:
In 7th slide - Improvements - Only necessary kernel modules
How does it actually refers to systemd?
You do
Am 11.12.2013 14:43, schrieb Cecil Westerhof:
On 12/11/2013 02:25 PM, Cecil Westerhof wrote:
You can to centralized logging with the journal too, by simply making
the journal files you want to look at accessible on the same
machine. This could be done via NFS sharing, or by copying them to a
Am 11.12.2013 22:41, schrieb Cecil Westerhof:
I tried out systemd-journal-gatewayd. But it looks like that everyone that
can
contact, can get log info. Is that true, or am I overlooking something?
as far as i remeber from older posts about it the intention is that
a) it is not on by
is it really needed to pass this messages to dmesg instead syslog
or supress them? it is disturbing in cases you distribute
dmesg over a infrastructure with more than 20 machines
[941542.003467] systemd-journald[22511]: Vacuuming done, freed 2879488 bytes
[944310.095412] systemd-journald[22511]:
Am 21.12.2013 14:44, schrieb Kay Sievers:
Trimming should be the job of the filesystem, not for a nasty cron
job. We do not want to support legacy filesystems with upstream
shipped systemd units.
doing it permanently on the fs-layer degrades all time performance
doing it in a cron job
Am 21.12.2013 15:23, schrieb Kay Sievers:
On Sat, Dec 21, 2013 at 3:11 PM, Reindl Harald h.rei...@thelounge.net wrote:
Am 21.12.2013 14:44, schrieb Kay Sievers:
Trimming should be the job of the filesystem, not for a nasty cron
job. We do not want to support legacy filesystems with upstream
Am 30.12.2013 18:53, schrieb Zbigniew Jędrzejewski-Szmek:
I found another one:
- https://bugs.freedesktop.org/show_bug.cgi?id=66912
Autocompletion does not propose template units which have some instances
enabled
may I notice this one in context of autocompletion too
Am 01.01.2014 22:13, schrieb Andrey Borzenkov:
В Ср, 01/01/2014 в 15:00 -0500, Dave Reisner пишет:
On Wed, Jan 01, 2014 at 11:43:15PM +0400, Andrey Borzenkov wrote:
systemd.special(7) suggests that network-online.target should be pulled
in by consumer. Unfortunately, that means that when
Am 02.01.2014 13:55, schrieb Tom Gundersen:
On Thu, Jan 2, 2014 at 12:56 PM, Holger Schurig holgerschu...@gmail.com
wrote:
AFAIK Mac OSX does a trick here
Yeah, and we should do the same: http://tools.ietf.org/search/rfc4436
because this explains why i sometimes see firewall logs in
the
Am 02.01.2014 16:29, schrieb Tom Gundersen: Hei Reindl,
On Thu, Jan 2, 2014 at 3:52 PM, Reindl Harald h.rei...@thelounge.net wrote:
Am 02.01.2014 13:55, schrieb Tom Gundersen:
On Thu, Jan 2, 2014 at 12:56 PM, Holger Schurig holgerschu...@gmail.com
wrote:
AFAIK Mac OSX does a trick here
Am 02.01.2014 16:41, schrieb Tom Gundersen:
On Thu, Jan 2, 2014 at 4:37 PM, Reindl Harald h.rei...@thelounge.net wrote:
the problems are that if someone comes back with his Apple notebook
this crap starts to using the old ip-address and triggering all sorts
of alarms, firewall-rules and so
Am 14.01.2014 15:03, schrieb Cristian Rodríguez:
El 14/01/14 09:52, Mark Hounschell escribió:
Well, the systemd/udev README file from 208-15.1:
yeah, one thing is what systemd upstream requires and a completely different
one is what openSUSE can/will support
or allow.
It is not just
can someone please have a look why starting with Fedora 20/RHEL7
and systemd-208 after typing systemctl reboot no longer waits
until sshd is closing the client connection resulting in a completly
frozen VT ignoring CTRL+C and waiting for KeepAlive timeout
Am 15.01.2014 03:57, schrieb Andrey Borzenkov:
В Wed, 15 Jan 2014 02:54:16 +0100
Reindl Harald h.rei...@thelounge.net пишет:
can someone please have a look why starting with Fedora 20/RHEL7
and systemd-208 after typing systemctl reboot no longer waits
until sshd is closing the client
Am 15.01.2014 16:47, schrieb Reindl Harald:
Am 15.01.2014 16:37, schrieb Holger Schurig:
Try systemctl --force reboot. The --force will kill the processes,
which (for me) closes the incoming ssh session
that indeed works
interesting question: what has changed in the latest systemd
Am 24.01.2014 16:03, schrieb Lennart Poettering:
It is our job to shutdown all services cleanly. A number of services
needs this, since they need to bring their files into a safe state
before quitting, and mark them as offline. We cannot just drop that.
Note however, that we add have
Am 24.01.2014 18:43, schrieb Lennart Poettering:
On Fri, 24.01.14 17:10, Colin Guthrie (gm...@colin.guthr.ie) wrote:
'Twas brillig, and Tom Horsley at 24/01/14 15:44 did gyre and gimble:
However, something like that can never be the default, we need to give
services the chance to shut
Am 24.01.2014 19:26, schrieb Michael Biebl:
2014/1/24 Lennart Poettering lenn...@poettering.net:
Yupp, Michal had the same idea, that's why there is the eye-of-sauron
animation in place...
Ah, good to know. That's a start.
I guess my systemd version (v204) is simply too old then?
Is
2014 18:59:56 +0100
Von: Reindl Harald h.rei...@thelounge.net
An: Lennart Poettering lenn...@poettering.net
Am 24.01.2014 18:53, schrieb Lennart Poettering:
On Fri, 24.01.14 18:45, Reindl Harald (h.rei...@thelounge.net) wrote:
However, something like that can never be the default, we need
Am 24.01.2014 19:44, schrieb Zbigniew Jędrzejewski-Szmek:
Is this animation shown irregardless of whether one has booted with
quiet or not?
With quiet the [OK] lines are not shown, so no, it only works
without quiet
one more case why the shiny graphical boot does only harm
in case of
Am 24.01.2014 20:01, schrieb Andrey Borzenkov:
В Fri, 24 Jan 2014 19:44:08 +0100
Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl пишет:
On Fri, Jan 24, 2014 at 07:26:48PM +0100, Michael Biebl wrote:
2014/1/24 Lennart Poettering lenn...@poettering.net:
On Fri, 24.01.14 18:18, Michael Biebl
Am 29.02.2012 17:16, schrieb Lennart Poettering:
On Sun, 26.02.12 19:13, Reindl Harald (h.rei...@thelounge.net) wrote:
the ExecStop is called but systemd DOES NOT wait
until it is finished leading to all virtual machines
are killed hard while systemctl stop vmware-default.service
does
Am 25.01.2014 18:09, schrieb Marcos Mello:
Koen Kooi koen at dominion.thruhere.net writes:
[snip]
To make matters worse, the cylon eye isn't displayed when you boot with
'quiet' in your kernel command line.
quiet systemd.show_status=1 shows the gracious Cylon eye
so that should be
Am 27.01.2014 12:30, schrieb Tom Horsley:
Sadly simple containers with little real world units seem to
avoid the problems. But I'm sure there will be some kind of fix for this
over the next week or so.
But my example doesn't have any units at all :-). I issue
two disable commands in a row
Am 28.01.2014 05:27, schrieb Zbigniew Jędrzejewski-Szmek:
after the timeout is reached it continues
the users problem is the silent waiting *before* the timeout
Done.
After a job has been running for more than 5s, or a failure occurs,
cylon eye will be shown. Also status will be printed
Am 04.02.2014 11:31, schrieb Rainer Krienke:
I am experiencing problems on openSuSE 13.1 systems using systemd, iff
this system uses NFS mounts for the users home directory mounted by
automount.
Regular 13.1 installations with local user home directories just work fine.
The problem is,
Am 06.02.2014 18:45, schrieb Greg KH:
On Thu, Feb 06, 2014 at 04:54:59PM +, Jóhann B. Guðmundsson wrote:
On 02/06/2014 03:39 PM, Greg KH wrote:
Right now you have to decide before loading the module how many
devices you want. And also when trying to use a device (any device),
you have
Am 11.02.2014 17:29, schrieb Andrey Borzenkov:
В Tue, 11 Feb 2014 17:20:15 +0100
Jason A. Donenfeld ja...@zx2c4.com пишет:
On Tue, Feb 11, 2014 at 5:15 PM, Dave Reisner d...@falconindy.com wrote:
I don't think there's any change needed here. The interface states:
The initrd should
1 - 100 of 1085 matches
Mail list logo
