'Twas brillig, and Zbigniew Jędrzejewski-Szmek at 10/07/14 17:58 did
gyre and gimble:
> On Thu, Jul 10, 2014 at 04:18:15PM +0100, Colin Guthrie wrote:
>>> I don't use RPM, but having your system's user policy consist of
>>> running useradd in a pre-installation script seems... sub-optimal.
>>
>> I
Currently syslog socket is not correctly verified if is in connected state.
This results in sending messages to a socket that is not connected which is
not allowed.
In this patch the socket is correctly checked. If the socket is not connected
forwarding to syslog is disabled.
This patch causes ab
On Fri, 11.07.14 09:52, Piotr Wilczek (p.wilc...@samsung.com) wrote:
> Currently syslog socket is not correctly verified if is in connected state.
> This results in sending messages to a socket that is not connected which is
> not allowed.
>
> In this patch the socket is correctly checked. If the
> -Original Message-
> From: Lennart Poettering [mailto:lenn...@poettering.net]
> Sent: Friday, July 11, 2014 12:44 PM
> To: Piotr Wilczek
> Cc: systemd-devel@lists.freedesktop.org; Kyungmin Park; Lukasz
> Stelmach; Juho Son; Bartlomiej Zolnierkiewicz
> Subject: Re: [systemd-devel] [PATCH]
On Fri, 11.07.14 13:02, Piotr Wilczek (p.wilc...@samsung.com) wrote:
> > B) Now, as a shortcut we use the same sock actually, via sendto() to
> > also pass data to /run/systemd/journal/syslog, which is where a
> > secondary syslog server should listen on, which will then also receieve
> > the data
On Thu, Jul 10, 2014 at 10:39:29PM +0200, Lennart Poettering wrote:
> Makes sense, commit!
Done.
> (Also needs man page update I figure...)
That was more work than the code change ;)
Zbyszek
___
systemd-devel mailing list
systemd-devel@lists.freedesktop
It is already in nodist_systemunit_DATA and if it is
shipped, it contains the hardcoded path to systemctl
which will cause it to fail to start when
rootprefix != prefix and rootbindir != bindir.
---
Makefile.am | 1 -
1 file changed, 1 deletion(-)
diff --git a/Makefile.am b/Makefile.am
index f934
gcc does not define WORDS_BIGENDIAN for big-endian PowerPC. It defines
__BIG_ENDIAN__ instead. So also check for __BIG_ENDIAN__ to determine if
the system is big-endian.
---
src/shared/architecture.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/shared/architecture.h
This avoids errors like this, when the paths are already there with the
correct permissions and owner:
chmod(/var/spool) failed: Read-only file system
---
src/tmpfiles/tmpfiles.c | 36 +---
1 file changed, 21 insertions(+), 15 deletions(-)
diff --git a/src/tmpfile
On Fri, Jul 11, 2014 at 12:01:19AM +, "Jóhann B. Guðmundsson" wrote:
> I had already submitted new patch with deployment "[PATCH] Add
> DEPLOYMENT to hostnamectl" which Zbyszek had suggested and you
> agreed to and FYI this has nothing to with trying to standardize
> anything it's about bringin
On Thu, Jul 10, 2014 at 11:18:20PM -0500, Kurt von Laven wrote:
> Hello folks,
>
> Apologies if anybody is getting this message twice; I originally posted on
> d...@lists.freedesktop.org and was directed here.
>
> I am attempting to listen to the SessionRemoved signal from the login
> manager
On Fri, 11.07.14 15:04, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
> gcc does not define WORDS_BIGENDIAN for big-endian PowerPC. It defines
> __BIG_ENDIAN__ instead. So also check for __BIG_ENDIAN__ to determine if
> the system is big-endian.
Hmm, the sources currently use three different
On Fri, 11 Jul 2014 15:27:56 +0200
Lennart Poettering wrote:
> On Fri, 11.07.14 15:04, Michael Olbrich (m.olbr...@pengutronix.de)
> wrote:
>
> > gcc does not define WORDS_BIGENDIAN for big-endian PowerPC. It
> > defines __BIG_ENDIAN__ instead. So also check for __BIG_ENDIAN__ to
> > determine if
On Fri, 11.07.14 15:43, Dan Horák (d...@danny.cz) wrote:
> > Hmm, the sources currently use three different ways to detect
> > endianess:
> >
> > 1) WORDS_BIGENDIAN (which appears to be an autoconf thing actually,
> >enabled via AC_C_BIGENDIAN, which we never call currently)
> > 2) __BTYE_ORD
On Fri, Jul 11, 2014 at 03:27:56PM +0200, Lennart Poettering wrote:
> On Fri, 11.07.14 15:04, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
>
> > gcc does not define WORDS_BIGENDIAN for big-endian PowerPC. It defines
> > __BIG_ENDIAN__ instead. So also check for __BIG_ENDIAN__ to determine if
On Fri, Jul 11, 2014 at 04:01:32PM +0200, Lennart Poettering wrote:
> On Fri, 11.07.14 15:43, Dan Horák (d...@danny.cz) wrote:
> > > Hmm, the sources currently use three different ways to detect
> > > endianess:
> > >
> > > 1) WORDS_BIGENDIAN (which appears to be an autoconf thing actually,
> > >
On Fri, 11.07.14 16:10, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
> It compiles again for me. But i noticed, that endian.h is not explicitly
> included. Are you sure that it's always included indirectly?
Oh, indeed! Fxied now!
Lennart
--
Lennart Poettering, Red Hat
Thank you Mantas and Djalal for improving my mental model.
On Fri, Jul 11, 2014 at 1:14 AM, Mantas Mikulėnas wrote:
> On Fri, Jul 11, 2014 at 7:18 AM, Kurt von Laven wrote:
>
>> Hello folks,
>>
>> Apologies if anybody is getting this message twice; I originally posted
>> on d...@lists.freedesk
Hi,
networkd on systemd v215 starts churning after printing the error in the
subject. The issue is present on git master.
Config:
# /etc/systemd/network/dhcp.network
[Match]
Name=bond0
[Network]
Description=DHCPv4 client
DHCP=true
# /etc/systemd/network/ethernet.link
[Match]
Driver=r8169
P
These files are specially labeled on SELinux systems, and we need to
preserve that label.
---
src/shared/label.c | 25 +
src/shared/label.h | 1 +
src/sysusers/sysusers.c | 11 ++-
3 files changed, 36 insertions(+), 1 deletion(-)
From 715e1ff352601d841fc
On Fri, Jul 11, 2014, at 06:05 AM, Michael Olbrich wrote:
> This avoids errors like this, when the paths are already there with the
> correct permissions and owner:
>
> chmod(/var/spool) failed: Read-only file system
I'd say we should avoid running systemd-tmpfiles if the filesystem is
read onl
On Fri, Jul 11, 2014 at 02:26:13PM -0700, Colin Walters wrote:
>
>
> On Fri, Jul 11, 2014, at 06:05 AM, Michael Olbrich wrote:
> > This avoids errors like this, when the paths are already there with the
> > correct permissions and owner:
> >
> > chmod(/var/spool) failed: Read-only file system
>
On Fri, Jul 11, 2014, at 03:04 PM, Dave Reisner wrote:
> No way. This precludes tmpfiles from creating directories in /run.
Yeah that suggestion would break other stuff too, ignore it.
This does get into the ostree commit I linked to though; we could just
have systemd mount /var as a tmpfs if t
On Fri, Jul 11, 2014 at 02:37:36PM +0200, Jon Severinsson wrote:
> It is already in nodist_systemunit_DATA and if it is
> shipped, it contains the hardcoded path to systemctl
> which will cause it to fail to start when
> rootprefix != prefix and rootbindir != bindir.
Applied.
Zbyszek
_
On Mon, Jul 07, 2014 at 11:18:38AM -0700, Filipe Brandenburger wrote:
> +Zbigniew who committed the original patch.
>
> On Fri, Jul 4, 2014 at 11:43 AM, Mike Gilbert wrote:
> > This reverts commit 0c26bfc3d21fdb3963f1248c237e2f1a33b5566d.
Applied.
Zbyszek
> Notice that the current client code should be ok with the server
> ignoring the broadcast flag, and just accept either broadcast or
> unicast packages.
agreed
>Hm, if I read the DHCP spec correctly it requires the networks to deal
>with broadcast packets, as NAK is always sent as broadcast, so
26 matches
Mail list logo