Re: [systemd-devel] systemd and intltool

[Jan Synacek]

Michael Biebl  writes:

> 2015-10-07 14:43 GMT+02:00 Jan Synacek :
>> Lennart Poettering  writes:
>
>>> Happy to take a patch that removes the intltool hookup if it replaces
>>> it with the right gettext hookup instead.
>>
>> I have investigated this a bit... AFAIK, gettext cannot be directly used
>> to parse and merge translations into XML files. However, a simple python
>> script instead of intltools should be enough for systemd's needs. I'll
>> investigate further and possibly submit a pull request.
>
> Afaiu, the plan is not to teach gettext about all different XML
> formats, but use itstool for that.

I didn't suggest that.

> https://mail.gnome.org/archives/desktop-devel-list/2015-October/msg0.html
>
> That's still work in progress, so maybe we just have to wait a little
> until this is sorted out.

I have tried itstool and works just fine.

@Lennart: Happy to take a patch to replace intltool with itstool?

-- 
Jan Synacek
Software Engineer, Red Hat


signature.asc
Description: PGP signature
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] [PATCH] Kernel mac address assignment to VLAN NETDEV

[O Neill, David M]

The creation of a VLAN netdev device, as seen in the 'ip link' command, is
done without specifying a mac address.
The kernel determines the mac address for the VLAN NETDEV, which should be
the parent mac address.

This patch fixes this behavior and the resulting delivery of DHCP Offers to
the VLAN NETDEV.

Technical Contributors
Rami Rosen 
Szczerbik, PrzemyslawX 

Signed-off-by: David O Neill 

---
 src/network/networkd-netdev.c | 11 ---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/src/network/networkd-netdev.c b/src/network/networkd-netdev.c
index 6949b40..2c1dd9e 100644
--- a/src/network/networkd-netdev.c
+++ b/src/network/networkd-netdev.c
@@ -647,9 +647,14 @@ static int netdev_load_one(Manager *manager, const char
*filename) {
 return log_oom();
 
 if (!netdev->mac) {
-r = netdev_get_mac(netdev->ifname, >mac);
-if (r < 0)
-return log_error_errno(r, "Failed to generate
predictable MAC address for %s: %m", netdev->ifname);
+/* do not generate mac for VLAN netdev, allow kernel to
assign mac (parent mac) */
+if(netdev->kind != NETDEV_KIND_VLAN) {
+r = netdev_get_mac(netdev->ifname, >mac);
+if (r < 0)
+return log_error_errno(r, "Failed to
generate predictable MAC address for %s: %m", netdev->ifname);
+} else {
+log_debug_netdev(netdev, "Skipping generating MAC
address for vlan netdev");
+}
 }
 
 r = hashmap_put(netdev->manager->netdevs, netdev->ifname, netdev);
--
1.8.2



smime.p7s
Description: S/MIME cryptographic signature
--
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare

This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient(s). Any review or distribution by others is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender and delete all copies.

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] journalctl --list-boots fails

[Lars Noschinski]

[please CC me on answers]

Hi,

today I had to deal with my machine crashing a lot. This seems to have
corrupted some journal data, as journalctl cannot lists the boots anymore:

$ sudo journalctl --list-boots
Failed to determine boots: No data available

It was working fine earlier this morning. The log data itself seems to
be still readable (that is, "journalctl -b-" gives plausible
results). What can I do to to fix this issue?

This is is systemd 226 from Debian.

  -- Lars

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Secret machine-id for RFC 7217 stable addresses

[Tom Gundersen]

Hi Lubomir,

Sorry not to have responded to this earlier, but as I was just
reminded of this, here are my take:

On Mon, Sep 7, 2015 at 7:49 PM, Lubomir Rintel  wrote:
> the RFC 7217 specifies an algorithm for generating an IPv6 host address
> that stays stable in a particular network but changes when the machine
> enters another network to prevent tracking [1]. It works by hashing a
> tuple of various parameters one of which is "secret_key" -- a secret
> value specific to a particular machine.
>
> [1] https://tools.ietf.org/html/rfc7217#section-5
>
> This sounds a bit like machine-id, unfortunately given it's world
> readable and available via DBus (and possibly on a network?) it doesn'tseem 
> to be secret enough.
>
> I'm wondering if it would make sense to reuse some of the tooling?
> Would it make sense to extend systemd-machine-id-setup(1) to generate
> one more identifier or maybe add another tool to set up the secret id?

A priori, it would perhaps have been nice to consider the real
machine-id on disk to be "secret", and only ever expose a hash of it,
but that ship has sailed I'm afraid. We could of course introduce a
second machine-id as you propose, but before doing that I'd like to
fully understand if that really solves the problem.

If I understand correctly, most of the point of RFC7217 is achieved
even if the secret key is known. The important point is to have a good
hashing function, and in that case knowing the secret key will not let
you discover any of the other parameters (which are the ones you
really want to hide).

Moreover, if the point is privacy, if an attacker has access (in some
way) to the machine-id, there is no point in him going after the
interface identifier as he can already identify the client.

Given those two facts, might it not be sufficient to use the
machine-id as the secret key after all? Or am I missing something?

Cheers,

Tom
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Add ambient capability support to execution environment config?

[Andy Lutomirski]

For non-root services, getting Capabilities= and CapabilityBoundingSet= to
do anything useful is rather tricky.  Would it make sense to add
AmbientCapabilities= to set ambient (and, implicitly, inheritable)
capabilities, which will be available in Linux 4.3?

Alternatively, there could be a boolean option to change the meaning of
Capabilities so that it uses ambient capabilities instead of whatever it
currently does.

--Andy
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] changed property value in signal

[Pradeepa Kumar]

Thanks for reply.

I am writing a monitoring application to start, stop and monitor service
state.

I am looking for way to know when service stoppped or failed so that i can
take some action in my monitoring app.

I am listening to PropertiesChanged signal and query ActiveState. This does
not work always.
Some times, unit is unloaded before I query the ActiveState. What is the
solution for this

Do we get new values of property along with PropertiesChanged signal in new
version of systemd?
if yes in which version this feature was added ?

What is the solution to achieve my requirement ?



On Fri, Jul 3, 2015 at 3:35 PM, Lennart Poettering 
wrote:

> On Fri, 03.07.15 15:12, Pradeepa Kumar (cdprade...@gmail.com) wrote:
>
> > On Fri, Jul 3, 2015 at 2:12 PM, Lennart Poettering <
> lenn...@poettering.net>
> > wrote:
> >
> > > On Thu, 02.07.15 10:18, Pradeepa Kumar (cdprade...@gmail.com) wrote:
> > >
> > > > hi
> > > > I am new to systemd.
> > > > I am using systemd 208, libdbus-1-3_1.4.18-1ubuntu1.4_i386.deb
> > > > I am to monitor unit stop/failure in my application .
> > > > So I am subscribing to propertiesChanged signal and paring SubState.
> > > > The propertieschanged message contains a dictionary and invalidated
> list
> > > > of properties.
> > > > But the dictionary is empty(which is supposed to contain new value of
> > > > changed properties), so i am left with querying new values of the
> changed
> > > > property from list of invalidated properties list.
> > > >
> > > > - please let me know how do i get new values in the signal msg
> > > >   itself
> > >
> > > you don't. We just invalidate the props, you have to query them
> > > aftwards yourself, to determine the n value.
> >
> >  Prad>>  But in online, i see some example of dbus-monitor command where
> > output has a dictionary- which contains properties and new values.
> > I want same output. how do i get that??
>
> You don't... It's up to the service to decide which properties it
> just invalidates and which ones it sends along.
>
> > > We take the liberty to invalidate some props and send the full value
> > > of others along. it's not considered api really which prop gets which
> > > behaviour...
> >
> > Prad>> I did not understand this comment
> > Can you please explain
>
> It's up to the service (in this case systemd) to choose which props it
> sends PropertiesChanged signals for, and if it decides to do so,
> for which it sends invalidation and for which it sends the full value
> along.
>
> Lennart
>
> --
> Lennart Poettering, Red Hat
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] How to get notified on service state change

[Pradeepa Kumar]

Hi systemd-experts,

I am writing a daemon which starts, stops and monitor services and I am
using dbus to interface with systemd. I send messages on dbus to start or
stop the service and this is working well. I want to achieve the following:



1) Monitor service exit using the systemd dbus interface.

2) Monitor when the service has entered a failed state



I am trying to understand what is the right mechanism to implement this
using the systemd dbus interface, I have tried a few things clearly I don’t
understand how this works, any help greatly appreciated.



I am looking for way to know when service stopped or failed so that i can
take some action in my monitoring app.

I am listening to PropertiesChanged signal and query ActiveState property
to get new value. This does not work always.
Some times, unit is unloaded before I query the ActiveState.
Do we get new values of property along with PropertiesChanged signal in new
version of systemd?
if yes in which version this feature was added ?
What is the best way to achieve my requirement ?

Appreciate your help on above queries



Thanks

Prashant
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel