[systemd-devel] failed to change interface name (systemd-networkd)

2015-09-23 Thread James
Hello, Hoping someone can point me in the right direction. I'm attempting to change the interface name (eth0 -> wired) on one of my servers. Here's the output from the journal: ~# journalctl --no-pager | grep -i wired Sep 23 17:11:15 vivid systemd-udevd[399]: error changing net interface name 'e

Re: [systemd-devel] failed to change interface name (systemd-networkd)

2015-10-01 Thread James
Hello, just following up to see if there were any ideas on what may be causing this. Any thoughts appreciated. On Wed, Sep 23, 2015 at 10:17 PM, James wrote: > Hello, > > Hoping someone can point me in the right direction. I'm attempting to > change the interface name (eth0 -&

Re: [systemd-devel] failed to change interface name (systemd-networkd)

2015-10-01 Thread James
here. I'm running into this issue on Ubuntu 15.04 (Vivid). If there are any pointers on how to best determine the script / root cause I'd be very much appreciative. Thank you. On Thu, Oct 1, 2015 at 2:31 PM, Kay Sievers wrote: > On Thu, Oct 1, 2015 at 7:21 PM, James wrote: >>

Re: [systemd-devel] Ordering services issue. Trying to start ptp4l in bonding setup fails as bonding appears to take a while.

2021-12-01 Thread James Feeney
e, you might simply hard-code what you want, if you are not looking for a generic solution, and all you want is bonding on a couple of interfaces. Still, when properly setup, you can individually "start" and "stop" any of the target units or network service units and get correct behavior. James

Re: [systemd-devel] Ordering services issue. Trying to start ptp4l in bonding setup fails as bonding appears to take a while.

2021-12-02 Thread James Feeney
ary Clock and Ordinary Clock client service, ptp4l. Are you having a problem with network bonding? Or a problem with your ptp4l? James

Re: [systemd-devel] Ordering services issue. Trying to start ptp4l in bonding setup fails as bonding appears to take a while.

2021-12-02 Thread James Feeney
ing been subsequently "vandalized" by a rather persistent inexperienced and arrogant user. James

[systemd-devel] systemd-journald namespace persistence

2022-02-09 Thread Roger James
How do I create a persistent systemd-journald namespace? I have a backup service that is run by a systemd timer. I would like that to use it's own namespace. I can create the namespace manually using systemctl start systemd-journald@mynamespace.service. However I cannot find a way to do that s

[systemd-devel] Unit Names and Environment File Variable Names - Inconsistent Character Sets and Shortcomings with Unit Name Specifiers

2022-04-26 Thread James Feeney
'The name of the full unit is formed by inserting the instance name between "@" and the unit type suffix'. So the complete Unit Name character set then includes also the character "@". Of course, that is the cause of the "invalid environment assignment" error. The dash "-" character, which is allowed and required in the Unit Name character set, is *not* included or allowed in the Environment File character set. Why is that? That seems like a pointless and unnecessary limitation, having an Environment File Variable Name character set *different from* the Unit Name character set. Furthermore, notice that the "escaping" name specifiers, "%P", "%J", and "%I", cannot be used with the Environment File variable names generally, and cannot be used to work-around the dash "-" character limitation, because the backslash "\" character is also required and used with systemd String Escaping in Unit Names, and is also *not* included or allowed in the Environment File Variable Name character set. So, finally, unless there is some use case that can be discovered prohibiting this, it would be best to conform the Unit Name and the Environment File Variable Name character sets, by simply expanding the Environment File Variable Name character set to include and allow those additional characters, ":", "-", ".", "\", and "@", from the Unit Name character set. James

Re: [systemd-devel] Requires and After

2019-01-02 Thread James Feeney
On 1/2/19 3:21 AM, Reindl Harald wrote: > it's > pretty obvious when i REQUIRE something that it should be there when i > get started Not only is it not "obvious" that "something should be there", it is not true. You are confusing "Requires=" and "Requisite=". Some developers and some users are

Re: [systemd-devel] Requires and After

2019-01-02 Thread James Feeney
On 1/2/19 12:50 AM, Olaf van der Spek wrote: > Activation by itself guarantees basically nothing. "Activation" guarantees activation. Activating, for instance, a service unit is quite a bit more significant than "nothing". >> Because, as far as I know, "Requisite=" is completely broken in syste

Re: [systemd-devel] Requires and After

2019-01-02 Thread James Feeney
On 1/2/19 5:38 PM, Tom H wrote: >> Some developers and some users are not native English speakers. In >> some cases, systemd terminology can be ... less than optimal, while, >> in other situations, users will simply misunderstand the conventional >> meaning of words. > You might not like how "Requ

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-05-17 Thread James Hogarth
On 15 May 2016 at 08:11, James Hogarth wrote: > > On 15 May 2016 06:32, "Andrei Borzenkov" wrote: > > > > 15.05.2016 06:36, Chris Murphy пишет: > > > On Thu, May 12, 2016 at 12:38 PM, James Hogarth < > james.hoga...@gmail.com> wrote: > > &

[systemd-devel] proposal to more precisely articulate the meaning of start and stop dependencies

2016-12-24 Thread James Feeney
oup* of unit files. Currently, systemd restricts passing unit names with "enable" template files, allowing only two parameters to be passed, to resolve template unit names. Either unit A declares "A Stops B", or unit B declares "B Stopped By A". For instance, "PartOf

[systemd-devel] Clarification on unit state meanings

2017-08-09 Thread James Forcier
here a more complete listing anywhere of what scenarios correspond to what states? If not, what's the expected behavior here? -- Thanks, James Forcier ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Reading an "ao" signature message with the sdbus c library?

2017-08-17 Thread James Johnson
Hello, Can someone please point me to the correct method for reading an "ao" signature dbus message using the sd_bus C api? I am trying to read all the network devices with the following call: result = sd_bus_get_property(m_bus, "org.freedesktop.NetworkManager",

Re: [systemd-devel] Reading an "ao" signature message with the sdbus c library?

2017-08-17 Thread James Johnson
Hello, It looks like I figured out my problem, I have to use: result = sd_bus_message_enter_container(msgCall, 'a', "o"); before I try reading the array with : result = sd_bus_message_read(msgCall, "o", &ptr); Thanks, Jimmy On Thu, Aug 17, 2017 at 1:43

[systemd-devel] Wireless mesh networks and link_carrier_gained

2018-12-17 Thread Roger James
Hello, I have been testing the uses of systemd-networkd to configure wireless mesh networks, and have encountered a problem which manifests itself as a failure to correctly configure the additional dchp options offered by the inbuilt dhcpv4 server. This is related to the following commit. h

Re: [systemd-devel] Wireless mesh networks and link_carrier_gained

2018-12-18 Thread Roger James
Hi, I will try to comply:-). I have been building forward from a raspbian stretch 232 version for my test nodes. But I should be able to switch to and ubuntu bionic system to test this. I would like to test in a fakeroot, container or stick; so I am thinking that I need look at mkosi. Any poi

Re: [systemd-devel] Requires and After

2019-01-01 Thread James Feeney
> It's about Requires and After. I think a unit in Requires should imply > that unit in After too, otherwise the requirement isn't really met. > Is there a use case for Requires but not After? Olaf, previously, on GitHub, you had said: >> I think I understand Requires and After ... and, I would

Re: [systemd-devel] Requires and After

2019-01-01 Thread James Feeney
On 1/1/19 8:33 PM, Reindl Harald wrote: > "After" is a soft dependency, if that unit isn't enabled or don#t exist > at all it don't matter > > "Requires" is a hard dependency and it makes no sense not imply ordering And then, what do you mean by "soft dependency" and "hard dependency"? It sound

[systemd-devel] socket activated services and correct dependency mapping

2015-07-24 Thread James Hogarth
d an associated that has not explicit need of the socket? Regards, James ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] socket activated services and correct dependency mapping

2015-07-24 Thread James Hogarth
On 24 July 2015 at 10:38, James Hogarth wrote: > Hi, > > I'm in the process of adding systemd native sockets to a service > (rather than using inetd compatibility) and am trying to get my head > around the proper way to configure the unit files so that the socket >

Re: [systemd-devel] socket activated services and correct dependency mapping

2015-07-25 Thread James Hogarth
On 24 Jul 2015 11:55, "Dimitri John Ledkov" wrote: > > On 24 July 2015 at 10:38, James Hogarth wrote: > > I want a user to be able to systemctl start sslh and use listening > > addresses in /etc/sslh.cfg as always (so I'm reluctant to put a > > straight So

[systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-18 Thread James Hogarth
acut cmdline coming later than the hibernate generator wouldn't be a problem. Cheers, James ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-18 Thread James Hogarth
On 19 Apr 2016 04:53, "Andrei Borzenkov" wrote: > > 19.04.2016 01:19, James Hogarth пишет: > > Hi all, > > > > There's been some discussion today about the impact of > > https://bugzilla.redhat.com/show_bug.cgi?id=1206936 and where the prob

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-19 Thread James Hogarth
On 19 Apr 2016 08:05, "Andrei Borzenkov" wrote: > > On Tue, Apr 19, 2016 at 9:45 AM, James Hogarth wrote: > > > > > Seeing as systemd decides the swap to hibernate to in the first place, can't > > No, it does not. Device to hibernate to is set by prev

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-20 Thread James Hogarth
On 20 Apr 2016 05:47, "Chris Murphy" wrote: > > On Tue, Apr 19, 2016 at 4:10 AM, Lennart Poettering > wrote: > > > > > So what precisely are you proposing? That we actively search for the > > swap partition in the hibernate-resume generator? > > I t

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-20 Thread James Hogarth
On 20 April 2016 at 10:20, Lennart Poettering wrote: > On Wed, 20.04.16 08:00, James Hogarth (james.hoga...@gmail.com) wrote: > > > Regardless of how the hibernate generator might potentially be changed to > > attempt to locate a valid swap partition with hibernate data, or

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-05-02 Thread James Hogarth
On 24 Apr 2016 21:31, "poma" wrote: > > On 20.04.2016 22:42, Chris Murphy wrote: > > On Wed, Apr 20, 2016 at 1:50 PM, Tobias Hunger wrote: > > [...] > > > Anyway, the most complete solution for BIOS, UEFI, and UEFI Secure > > Boot systems, is fast startups as possible (which helps all kinds of >

Re: [systemd-devel] when/where was support for assigning "ethX" names removed?

2016-05-12 Thread James Hogarth
> > On 12 May 2016 18:28, "Chris Friesen" wrote: > > > > Hi, > > > > Could someone point me to the commit that removed support for assigning "ethX" names based on MAC addresses? > > > > Alternately, can someone suggest a way to get equivalent behaviour (the ability to set "ethX" names based on MAC

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-05-12 Thread James Hogarth
On 2 May 2016 18:58, "James Hogarth" wrote: > > > On 24 Apr 2016 21:31, "poma" wrote: > > > > On 20.04.2016 22:42, Chris Murphy wrote: > > > On Wed, Apr 20, 2016 at 1:50 PM, Tobias Hunger < tobias.hun...@gmail.com> wrote: > > > &g

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-05-15 Thread James Hogarth
On 15 May 2016 06:32, "Andrei Borzenkov" wrote: > > 15.05.2016 06:36, Chris Murphy пишет: > > On Thu, May 12, 2016 at 12:38 PM, James Hogarth wrote: > >> > >> On 2 May 2016 18:58, "James Hogarth" wrote: > >>> > >>> &g

Re: [systemd-devel] gentoo openrc

2010-08-09 Thread James Cloos
ight provide useful clues. At worst one could integrate code from something like dash(1) to parse the scripts and build up the depend graph. (Writing from memory of discussions promoting openrc over baselayout-1, I haven't looked at the openrc code in a *long* time) -JimC --

Re: [systemd-devel] gentoo openrc

2010-08-10 Thread James Cloos
gt; tree. I have to agree with avoiding bloat. A closer look shows that you were most likely on the right track. (init.d/net.lo may make the heaviest usage of bashisms.) -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 ___ systemd-devel mai

Re: [systemd-devel] 'tasks' as first-order objects?

2010-08-13 Thread James May
"notfound" >> unnecessarily requires more brain cycles than "found" and "!found" would >> have. >> I have to stop and check I'm doing what I think I'm doing every time I come >> across it. I also have the same problem with UIs t

[systemd-devel] Possible systemd segfault switching from 216 to 219 in fedora upgrade

2015-03-05 Thread James Hogarth
the crash along with coredumps that have been generated on the bug. These tests were carried out with enforcing=0 at the kernel command line so I'm reasonably confident the bug is not SELinux related. Cheers, James ___ systemd-devel mailing lis

Re: [systemd-devel] Possible systemd segfault switching from 216 to 219 in fedora upgrade

2015-03-05 Thread James Hogarth
On 5 March 2015 at 15:10, Lennart Poettering wrote: > > > Right before switch rooting systemd will kill all remaining processes > of the initrd, including the strace, hence the strace logs aren't that > useful either, they end before the transition. > > Please boot with "systemd.log_level=debug sy

Re: [systemd-devel] Possible systemd segfault switching from 216 to 219 in fedora upgrade

2015-03-05 Thread James Hogarth
On 5 March 2015 at 17:07, James Hogarth wrote: > On 5 March 2015 at 15:10, Lennart Poettering wrote: >> >> >> Right before switch rooting systemd will kill all remaining processes >> of the initrd, including the strace, hence the strace logs aren't that >&

Re: [systemd-devel] Possible systemd segfault switching from 216 to 219 in fedora upgrade

2015-03-09 Thread James Hogarth
On 8 March 2015 at 22:32, Lennart Poettering wrote: > On Thu, 05.03.15 22:07, James Hogarth (james.hoga...@gmail.com) wrote: > >> > Tried to put together a reduced testcase via a yum installroot style >> > container to switch-root into to see what that behaviour is like an

[systemd-devel] Systemd-nspawn -- Unable to initialize virtual ethernet connection

2014-09-19 Thread James Lott
t@utility01 ~]# pacman -Q systemd systemd 216-3 I'm happy to run any additional tests or provide any additional information needed to help try to reproduce. Thanks in advance for any help! -- James Lott ___ systemd-devel mailing list systemd-de

[systemd-devel] systemd-networkd -- Unable to create VLAN device

2014-09-19 Thread James Lott
Hello again! I've been eager to play with networking features, in case you couldn't tell ;) This patricular issue seems separate from my first one though, so I thought it would be best to discuss separately. I am trying to use systemd-networkd to essentially replace vconfig. I am using eth0 as

Re: [systemd-devel] systemd-networkd -- Unable to create VLAN device

2014-09-19 Thread James Lott
Holy smokes, that did it! Many thanks for taking time out of your day to help me find my silly mistake :) On Friday 19 September 2014 22:51:41 Tom Gundersen wrote: > On Fri, Sep 19, 2014 at 6:59 PM, James Lott wrote: > > Hello again! > > > > I've been eager to play wi

Re: [systemd-devel] Systemd-nspawn -- Unable to initialize virtual ethernet connection

2014-09-19 Thread James Lott
be? I want to make sure I keep my eyes peeled for it! On Friday 19 September 2014 23:04:40 Tom Gundersen wrote: > On Fri, Sep 19, 2014 at 6:37 PM, James Lott wrote: > > I am trying to setup and play around with some of the private networking > > features of systemd, and one of the

[systemd-devel] Systemd-networkd -- Cannot acquire DHCP lease on bridge interface

2014-09-24 Thread James Lott
Hello! With some help from the kind people on this list, I was able to get my basic network interfaces up and runnign with systemd-networkd. Now I've moved on to playing with some slightly more complex setups, and have run into some issues that as far as I can tell may be bugs (but I'm not quit

Re: [systemd-devel] Systemd-networkd -- Cannot acquire DHCP lease on bridge interface

2014-09-24 Thread James Lott
service is included in that email as well). On Wednesday 24 September 2014 22:44:17 Leonid Isaev wrote: > Hi, > > On Wed, Sep 24, 2014 at 07:16:03PM -0700, James Lott wrote: > > However, when I try to acquire a dhcp lease through the bridge > > interface, I am unable to do so

[systemd-devel] Systemd-nspawn -- Canot add interface to container

2014-09-24 Thread James Lott
Hello again! I'm having another issue with private networking in systemd-nspawn. This one I'm not so certain is a bug, but probably some kind of mistake on my part. Base on my reading of the systemd-nspawn man page though, I can't figure out what the problem is. Basically, all I'm tring to do i

Re: [systemd-devel] Systemd-nspawn -- Canot add interface to container

2014-09-25 Thread James Lott
884 1128 pts/3S+ 09:15 0:00 systemd- nspawn --private-network [root@host01 lanvpn]# ip netns list [root@host01 lanvpn]# Any nudges in the right direction are welcome, and appreciated! On Thursday 25 September 2014 10:21:16 Marcel Holtmann wrote: > Hi James, > > > I'm h

Re: [systemd-devel] Systemd-nspawn -- Canot add interface to container

2014-09-25 Thread James Lott
that? On Thursday 25 September 2014 20:11:56 Mantas Mikulėnas wrote: > On Thu, Sep 25, 2014 at 7:49 PM, James Lott wrote: > > Hi Marcel, > > > > Thanks for the help pointing that one out! With your guidance I was able > > to > > figure out that I'll need

Re: [systemd-devel] Systemd-nspawn -- Canot add interface to container

2014-09-25 Thread James Lott
>> On Thu, Sep 25, 2014 at 10:40:42AM -0700, James Lott wrote: >> Hi Mantas, >> >> Thanks for the clarification. The first thing I tried actually was using the >> PID >> of the systemd-nspawn instance, like so >> >> [root@host01 lanvpn]# ps aux | g

Re: [systemd-devel] Systemd-networkd -- Cannot acquire DHCP lease on bridge interface

2014-09-25 Thread James Lott
ent solution. I guess that's what I get for living life on the edge ;) On Thursday 25 September 2014 18:23:47 Leonid Isaev wrote: > Hi, > > On Wed, Sep 24, 2014 at 08:14:55PM -0700, James Lott wrote: > > Hello, > > > > There is no .network file for the br

Re: [systemd-devel] Systemd-nspawn -- Canot add interface to container

2014-09-25 Thread James Lott
to be coordinating the movement of this interface within a service file, so I don't need to do it manually when starting the container... but I suppose I can write an ExecStartPost script which can manage this. Thanks again for all your help! On Thursday 25 September 2014 16:25:02 James

Re: [systemd-devel] Systemd-nspawn -- Canot add interface to container

2014-09-26 Thread James Lott
/net/eth0 lrwxrwxrwx 1 root root 0 Dec 31 1969 eth1 -> ../../devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.0/net/eth1 On Thursday 25 September 2014 17:05:34 James Lott wrote: > Shame on me for not spending more time trying to figure this out before > responding. Please

Re: [systemd-devel] Systemd-nspawn -- Canot add interface to container

2014-09-27 Thread James Lott
t. > On Sep 26, 2014, at 4:28 PM, James Lott wrote: > > Hello again! > > Once again, thanks for all the help with getting my wireless interface moved > into the container! Now I just have one more interface I'm having trouble > with. I can't seem to move my et

[systemd-devel] Systemd-nspawn: Cannot create tun device in container

2014-10-03 Thread James Lott
Hello, list! In some work I've been doing with systemd-nspawn containers, I've been trying to connect one of my containers to an openvpn network. This conteiner is being run with the --network-bridge flag to setup its networking, so according to the documentation, should retain CAP_NET_ADMIN ca

[systemd-devel] Systemd-nspawn: cannot add interfaces with --network-interface flag

2014-10-03 Thread James Lott
Hello, A little bit back I wrote in about having some difficulties adding network devices to containers. With some help from the list, I figured out how to add my network devices to an already running container using 'iw phy' and 'ip link'. However, I have not yet successfully added an interfa

Re: [systemd-devel] Systemd-nspawn: Cannot create tun device in container

2014-10-07 Thread James Lott
Does anyone have any feedback on this thread? If it's not possible for a container to create its own /dev/net/tun device (or use the host system's), I'll just move on to finding a less preferable solution. > On Oct 3, 2014, at 10:46 AM, James Lott wrote: > > Hello,

Re: [systemd-devel] Systemd-nspawn: Cannot create tun device in container

2014-10-09 Thread James Lott
process as it attempts to setup the connection. Please let me know if there's anything else I can provide to be helpful, and thanks again for the help! On Wednesday 08 October 2014 15:59:03 you wrote: > On Fri, Oct 3, 2014 at 7:46 PM, James Lott wrote: > > Hello, list! > > > &

Re: [systemd-devel] Systemd-nspawn: cannot add interfaces with --network-interface flag

2014-10-09 Thread James Lott
14:08:07 Lennart Poettering wrote: > On Fri, 03.10.14 10:58, James Lott (ja...@lottspot.com) wrote: > > Hello, > > > > A little bit back I wrote in about having some difficulties adding network > > devices to containers. With some help from the list, I figured out how to

Re: [systemd-devel] Systemd-nspawn: cannot add interfaces with --network-interface flag

2014-10-09 Thread James Lott
Whoops.. Meant to send the message: Installing the latest systemd from git fixed this issue. Thanks again for pointing that out! On Thursday 09 October 2014 15:14:18 James Lott wrote: > Hi Lennart! > > Thanks for your response! I observed this issue on Arch Linux ARM running > s

Re: [systemd-devel] Systemd-nspawn: Cannot create tun device in container

2014-10-09 Thread James Lott
:12:02 you wrote: > On Fri, Oct 10, 2014 at 12:13 AM, James Lott wrote: > > Trying to start up an openvpn connection yields the following error: > > > > Thu Oct 9 15:01:52 2014 ERROR: Cannot open TUN/TAP dev /dev/net/tun: > > Operation not permitted (errno=1) >

Re: [systemd-devel] Systemd-nspawn: Cannot create tun device in container

2014-10-11 Thread James Lott
Everything works great now, thanks for all of your help! > On Oct 10, 2014, at 2:13 AM, Lennart Poettering > wrote: > >> On Thu, 09.10.14 23:53, James Lott (ja...@lottspot.com) wrote: >> >> I am using a setup which retains the CAP_NET_ADMIN capability inside t

Re: [systemd-devel] [PATCH] netns: unix: only allow to find out unix socket in same net namespace

2013-08-25 Thread James Bottomley
se it doesn't serve, the hoster usually has separate container hosting (for a higher price, of course). James ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] [PATCH] netns: unix: only allow to find out unix socket in same net namespace

2013-08-25 Thread James Bottomley
On Sun, 2013-08-25 at 19:37 +0200, Kay Sievers wrote: > On Sun, Aug 25, 2013 at 7:16 PM, James Bottomley > wrote: > > On Wed, 2013-08-21 at 11:51 +0200, Kay Sievers wrote: > >> On Wed, Aug 21, 2013 at 9:22 AM, Gao feng wrote: > >> > On 08/21/2013 03:06 PM, Eric W

Re: [systemd-devel] [PATCH] netns: unix: only allow to find out unix socket in same net namespace

2013-08-25 Thread James Bottomley
On Mon, 2013-08-26 at 09:06 +0800, Gao feng wrote: > On 08/26/2013 02:16 AM, James Bottomley wrote: > > On Sun, 2013-08-25 at 19:37 +0200, Kay Sievers wrote: > >> On Sun, Aug 25, 2013 at 7:16 PM, James Bottomley > >> wrote: > >>> On Wed, 2013-08-21 at 11:51

Re: [systemd-devel] [PATCH] netns: unix: only allow to find out unix socket in same net namespace

2013-08-25 Thread James Bottomley
On Mon, 2013-08-26 at 11:35 +0800, Gao feng wrote: > On 08/26/2013 11:19 AM, James Bottomley wrote: > > Yes, we are discussing this problem in this whole thread. I wasn't really watching that bit, since the problem looks solved to me. I was just reacting against the unfortunate

Re: [systemd-devel] Small tool to spawn programs in graphical sessions from non-graphical ones

2013-09-01 Thread James May
/their/ > session on :0. > > ...sometimes I think Xorg should start at :1 instead, and reserve :0 > for annoying cronjobs and services that have DISPLAY=":0" hardcoded, > to remind everyone that they're using a multi-

Re: [systemd-devel] On(Resume|suspend|hibernate) in unit files?

2013-03-03 Thread James May
On 1 March 2013 07:24, Cristian Rodríguez wrote: > Having this confessed non-ideal ReloadOnResume ,StopOnSuspend in unit > files etc will make extremely easy to avoid relying on either pm-utils > hooks or those new in /usr/lib/systemd/systemd-sleep and having to patch > buggy software, most likel

[systemd-devel] shell / systemd config files

2013-05-20 Thread James Buren
Files such as /etc/machine-info have an incompatibility with systemd in regards to how it writes and/or parses them. Take the following sample: PRETTY_HOSTNAME="\'\"\$\`\\" Systemd will translate this to: '"$`\ However, the shells bash and dash will translate this to: \'"$`\ So, it appears to b

[systemd-devel] For a "device" unit, what is the trigger source of an associated service unit "Enqueue" and "Replace" state in the systemd state engine?

2025-02-10 Thread James Feeney
I am chasing a bug in the systemd response to the initiation of an ethernet interface "device" unit by the kernel. When an ethernet interface "device" unit is initiated by the kernel, systemd will Start an associated service unit in response, but will subsquently "Enqueue" that same already run

Re: [systemd-devel] For a "device" unit, what is the trigger source of an associated service unit "Enqueue" and "Replace" state in the systemd state engine?

2025-02-14 Thread James Feeney
On Thu, 2025-02-13 at 22:07 +0100, Lennart Poettering wrote: > On Mo, 10.02.25 19:09, James Feeney (ja...@nurealm.net) wrote: > > > > > > systemd[1]: Got message type=method_call sender=n/a > > destination=org.freedesktop.systemd1 path=/org/freedesk

Re: [systemd-devel] Designing a scheduler interface

2011-01-14 Thread Scott James Remnant
Hi Daniel, Thanks for getting in touch. On Thu, Jan 13, 2011 at 5:29 PM, Daniel Poelzleithner wrote: > What is currently unknown on the other hand is the current active X > window in use. This could be done by connecting tho X and reacting to > events there, but I think a cleaner approach would

Re: [systemd-devel] use /run instead of /dev/.run

2011-03-28 Thread Scott James Remnant
Ludwig Nussel wrote: > mount --bind /var/run /mnt > mount /var > mount -M /mnt /var/run > This doesn't work. It means there is a period during boot where /var/run suddenly vanishes (when mount the separate /var). You have to do: mount DEV_OF_VAR /mnt mount --bind /var/run /mnt/run mount -M /mnt

Re: [systemd-devel] "udevadm settle" and "init"

2011-03-31 Thread Scott James Remnant
There is, of course, one use for "settle"; I like to have a "monitor" running during boot that creates /var/log/udev - settle is as good a command as any to kill monitor when it's done. On Thu, Mar 31, 2011 at 11:35 AM, Kay Sievers wrote: > Hey, > > the underlying problem described below, is in n

[systemd-devel] Parallel startup with sockets and without killing the machine?

2011-05-09 Thread Scott James Remnant
Hey, I've been reading through the documentation on systemd and the Mailing List Archives and have had some questions, so I figured I'd post them here. These might be fairly complicated or unusual cases, and there may be no good answers now, and maybe no good answers ever, but I'd still like to get

[systemd-devel] device units rely on udev rules?

2011-05-09 Thread Scott James Remnant
Another question I wasn't able to find an answer to in the documentation I've read so far. The use of device units seems to very much rely on udevd running on the system, and not only that, udev rules having been parsed for the device and a systemd tag "set" in the udevdb. udev obviously starts af

[systemd-devel] Communicating need

2011-05-09 Thread Scott James Remnant
Thanks for your answers so far, I haven't had a chance to fully read and digest them yet, but will do so before replying on those threads (if I even need to, it's likely your responses are complete in of themselves). My third question is about communicating need; for this I'd like to outline a use

Re: [systemd-devel] Parallel startup with sockets and without killing the machine?

2011-05-09 Thread Scott James Remnant
Thanks for the reply! On Mon, May 9, 2011 at 11:04 AM, Lennart Poettering wrote: > On Mon, 09.05.11 09:10, Scott James Remnant (sc...@netsplit.com) wrote: > > > This seems to assume that it's a free cost to start a service or process > and > > have it block on a socke

Re: [systemd-devel] Parallel startup with sockets and without killing the machine?

2011-05-09 Thread Scott James Remnant
On Mon, May 9, 2011 at 12:16 PM, Gustavo Sverzut Barbieri < barbi...@profusion.mobi> wrote: > >> Well, right now let's make clear that Firefox/Chromium or other X clients >> won't be started by systemd as they are user session applications, and >> systemd itself will just deal with system context

Re: [systemd-devel] Parallel startup with sockets and without killing the machine?

2011-05-10 Thread Scott James Remnant
On Tue, May 10, 2011 at 7:41 AM, Gustavo Sverzut Barbieri < barbi...@profusion.mobi> wrote: > I'm not following all the user-session discussion, but AFAIU this > management will be done by the same code, but not same process (it's not > PID1). PAM (or another entity that has a role in the login/lo

Re: [systemd-devel] Parallel startup with sockets and without killing the machine?

2011-05-12 Thread Scott James Remnant
On Tue, May 10, 2011 at 9:39 AM, Lennart Poettering wrote: > Note that you need to delay execution of user code after the base system > is set up anyway, in order to ensure that the right perms are set on the > volatile and other directories. That means having a single transaction > for both user

Re: [systemd-devel] device units rely on udev rules?

2011-05-12 Thread Scott James Remnant
On Mon, May 9, 2011 at 12:43 PM, Lennart Poettering wrote: > > This means there are a large number of devices already known to the > kernel > > at the point that systemd starts, especially if you build the drivers > into > > the kernel for those devices. It's possible to get going straight away >

Re: [systemd-devel] Communicating need

2011-05-12 Thread Scott James Remnant
On Mon, May 9, 2011 at 4:32 PM, Lennart Poettering wrote: > On Mon, 09.05.11 13:13, Scott James Remnant (sc...@netsplit.com) wrote: > > > The System Daemon seems to be where systemd is much more clever; a > Bluetooth > > device unit would "want" the System Daemon

Re: [systemd-devel] Communicating need

2011-05-12 Thread Scott James Remnant
On Thu, May 12, 2011 at 6:59 PM, Gustavo Sverzut Barbieri < barbi...@profusion.mobi> wrote: > > Well, maybe you didn't get the activation part or you're trolling :-) > > Neither... > As I said in my mail about the bluetooth part, the problem with kernel > modules is that "you don't know what's in

Re: [systemd-devel] Communicating need

2011-05-16 Thread Scott James Remnant
On Mon, May 16, 2011 at 2:23 PM, Lennart Poettering wrote: > Our entire userspace bootup takes <1s here on an older X300. I think > nobody expects that the mouse reacts any quicker than that. > > Your "older X300" is probably rather more powerful than a single-core Atom CPU. > But as mentioned e

Re: [systemd-devel] Communicating need

2011-05-16 Thread Scott James Remnant
On Mon, May 16, 2011 at 2:46 PM, Lennart Poettering wrote: > > It takes about 5-6s for udev to run input_id on the keyboard + touchpad, > and > > thus for them to be available to X. > > How come this takes so long? > > Does this actually delay X? Nromally X should be fine without kbd/mouse > and t

[systemd-devel] generators, private /tmp

2024-11-19 Thread James Muir (jamesmui)
using, say, an environment variable or a config file setting. Is that correct? Thanks, -James M

Re: [systemd-devel] generators, private /tmp

2024-11-20 Thread James Muir (jamesmui)
config setting? I see the condition !MANAGER_IS_TEST_RUN(m) guards the flag FORK_PRIVATE_TMP but that seems to be just for testing. -James M

Re: [systemd-devel] generators, private /tmp

2024-11-26 Thread James Muir (jamesmui)
gt; > > Thanks for your reply. > > > > Is my second statement also correct? > > > > i.e. is there no way to prevent mounting a private /tmp when executing > > generators using something like an environment variable or config setting? > > There is none. I am considering preparing a patch that makes it configurable via system.conf. e.g., "GeneratorsUsePrivateTmp=yes" Would a contribution like that be welcome? -James M

[systemd-devel] systemd-bootchart, switch-root breakage

2025-01-03 Thread James Muir (jamesmui)
/ time-of-use issue in the code -- it checks that the proc filesystem is available, but then when it goes to read /proc/schedstat the file is not there (ENOENT). Has anyone else come across these? Should I open github issues? I can try creating a PR to fix issue 2. Thanks, -James M

Re: [systemd-devel] switch-root, init, SIGHUP

2025-01-21 Thread James Muir (jamesmui)
pen). Unfortunately, the switch-root operation somehow causes /proc/schedstat to become inaccessible, so systemd-bootchart is broken with "rdinit=" as well. -James M

[systemd-devel] switch-root, init, SIGHUP

2025-01-17 Thread James Muir (jamesmui)
sent when init-jm is invoked using “rdinit”. Thanks, -James M

Re: [systemd-devel] switch-root, init, SIGHUP

2025-01-20 Thread James Muir (jamesmui)
ignore_proc()). Also, my process does not have a controlling tty (it is being invoked using the “init” kernel param). There is no tty shown when I view its details using ps, and I also don’t see any ttys when I do “ls -l /proc//fd”. Any other suggestions? Maybe I should open a github issue for this. -James M

Re: [systemd-devel] switch-root, init, SIGHUP

2025-01-20 Thread James Muir (jamesmui)
way), then you will hit this SIGHUP (and bootchart exits when it receives SIGHUP, so this breaks it). That appears to have been not working for a while (e.g. it does not work with systemd v251). There is an strace log here: https://github.com/systemd/systemd-bootchart/issues/58 -James M

Re: [systemd-devel] switch-root, init, SIGHUP

2025-01-20 Thread James Muir (jamesmui)
t; > > Note that we'll also possibly reinitialize the tty on switch root, > > > maybe your tool has the tty open and gets a SIGHUP because of that. > > > > Brian M also suggested that might be the cause, but I don't see any > > ttys when I do "ls -l /proc//fd". > > it's not so much about that, but about which ctty your process has. There is no controlling tty listed in the output of "ps". -James M

Re: [systemd-devel] systemd-bootchart, switch-root breakage

2025-01-14 Thread James Muir (jamesmui)
> **1. systemd-bootchart stops too early** > > According to "man systemd-bootchart", the recommended way to invoke bootchart > is via a kernel parameter: > > init=/usr/lib/systemd/systemd-bootchart > > That parameter causes systemd-bootchart to be executed as the new init > process when we swit

Re: [systemd-devel] systemd-bootchart, switch-root breakage

2025-01-15 Thread James Muir (jamesmui)
> Isn't systemd-bootchart, like, dead? Last release is nine years old or so. The last release of systemd-bootchart, v235, was done in November 2023: https://github.com/systemd/systemd-bootchart/tags There hasn’t been much activity lately, but I wouldn’t call it dead (there are a few PRs open th

Re: [systemd-devel] systemd-bootchart, switch-root breakage

2025-01-15 Thread James Muir (jamesmui)
> I opened https://github.com/systemd/systemd-bootchart/issues/58 to track > this. Could someone explain why systemd-bootchart is being sent SIGHUP? Changing systemd-bootchart to ignore that signal isn’t difficult, but I would like to understand why PID 1 is sending it. Note that systemd-boot

[systemd-devel] systemd-tmpfiles, unsafe path transitions

2025-03-26 Thread James Muir (jamesmui)
is there a way I can change the ownership systemd-tmpfiles sees? Thanks, -James M

Re: [systemd-devel] systemd-tmpfiles, unsafe path transitions

2025-03-27 Thread James Muir (jamesmui)
> > Is there a conf option or an environment variable I can use to disable the > > unsafe path transition check? > > No there is not. It's a security hole what you are doing there... > > > Failing that, is there a way I can change the ownership systemd-tmpfiles > > sees? > > Why not just fix the

Re: [systemd-devel] systemd-tty-ask-password-agent, new warning

2025-07-08 Thread James Muir (jamesmui)
(v255.10). The following commit adds a log statement to exec-util,c and that is why it has appeared: https://github.com/systemd/systemd-stable/commit/76fe6ebee8 Any comment on my other question: is systemd-tty-ask-password an optional component? -James M

  1   2   >