I finally got everything working. Here is what I did to fix the problem:
adduser systemd-network root
adduser systemd-resolve root
adduser bind root
find /etc -type d -exec chmod 755 {} +
I don’t know who does this on a full linux image. I’m posting it here for the
next person who has this
I should have added that I am building a very stripped down image. These are
the Debian packages that are being installed:
linux-image-6.2.0 - locally built
firmware-imx-epdc - locally built
firmware-imx-sdma - locally built
firmware-imx-vpu - locally built
firmware-realtek - locally built
for local packages (not my
choice). This has been a very steep learning experience and I’m sure I have
more tweaking to do.
I’m having a problem with systemd on startup. System-networkd fails to run
with the following error:
● systemd-networkd.service - Network Service
Loaded: loaded
Hi Michal,
Found the issue, posting here to close this thread (and possibly help
someone who might land in this situation!)
The daemon which had issues with rate-limit, was invoking some
`systemctl stop/start `
commands in its initialization! (probably this has some unwanted side effects?)
If I
Hi Michal,
>> systemctl show $UNIT | grep -E
>> "StartLimit.*|InactiveExitTimestamp|ActiveEnterTimestamp"
This is the output from unit show :
InactiveExitTimestamp=Thu 2022-07-14 21:19:16 IST
InactiveExitTimestampMonotonic=3181663063
ActiveEnterTimestamp=Thu 2022-07-14 21:19:16 IST
Acti
Hi Michal,
>Does your service crash later than the demo service terminates?
Demo services work fine, the actual service is quite heavy and takes
time to startup.
> you may not reach the sufficient fail rate for start limit to kick
I didn't get this part. Say the daemon takes 60s to startup and cr
Hello,
I am on Ubuntu 18.04 (systemd version 237), I have been trying to get
service rate limiting to work, but not getting it right!
I checked/tested many examples with the same directives that I use in
my service files, they all work well (for e.g.)
cat < /usr/local/bin/myservice.sh
#!/usr/bin/
. I think
> that's too little though for the random seed, because if the random
> seed is not kept it's entirely useless. There is no need to keep a
> random seed in the file system if it would be flushed out on each
> boot...
>
> /var/lib/ otoh sounds much more appropriate
Hey,
I've been working on my small seedrng utility, which is more or less
the same thing as systemd-random-seed.service, with a few unimportant
design differences here and there. As I'd worked with
systemd-random-seed.service quite a bit before, its choices comprised
much of my me
about what to support in systemd? They'd not use our stuff
> >> anyway, so why bother?
>
> There's probably also a big minority of users (like me) who may be
> pro-systemd, but run a systemd-hostile distro for reasons that are
> nothing to do with systemd ...
>
> &
For several years now, I've been enjoying the fact that the
systemd-networkd DHCP server seems to do the right thing, but a question
has arisen, and I'm getting results that I can't explain.
Basically, the embedded system we've assembled has a WAN interface and
one or mo
I wasn't clear what I meant about processing of the .network file. With
Ethernet or Wi-Fi (using iwd), when the link comes up, systemd-networkd
does the Right Thing and starts network services on the interface,
running a DHCP client or setting up static address(es), routes, etc., as
spec
the below. If I manually assign the
IPv4 address to the interface and set up the route, I'm able to send
traffic to and from other nodes. I haven't yet looked into how
ModemManager communicates this info to NetworkManager or how things like
a change of address are handled. As I see
dress info in concert with
ModemManager, or do I have to force NetworkManager to play nicely with
systemd-networkd?
--
Bruce A. Johnson | Firmware Engineer
Blue Ridge Networks, Inc.
14120 Parke Long Court Suite 103 | Chantilly, VA 20151
Main: 1.800.722.1168 | Direct: 703-633
ostly broken and various Google results
indicate that there is no response to e-mails. I have, just now, tried
to submit a patch by following the guide for the PCI IDs, from which the
USB IDs site was copied. I could not register in any way, so I suspect
my e-mail will be dropped.
Is there any b
On 22/04/2021 16:14, Bruce A. Johnson wrote:
I'm still trying to get an explanation of why having a valid DHCP
address is not in itself good enough.
Correction: I'm still trying to get an explanation from my requirements
person :facepalm:
Bruce A. Johnson | Firmware Engineer
I'm still trying to get an explanation of why having a valid DHCP
address is not in itself good enough. The only reason I've been able to
see is that after the lease is issued, and before the time comes to
refresh the lease, there could be a communication failure somewhere
between
Silvio, thanks for the suggestion. I'm not concerned with keeping the
lease forever; the system actually experiences a topology change as it's
switched from one network to another, and I can catch that from the DBus
events that occur. The problem we're trying to solve is
Is there a correct way to obtain information about the DHCP lease
received by systemd-networkd's DHCP client functionality? It was easy
enough to find SERVER_ADDRESS in /var/run/systemd/netif/leases/4, but
there is a big fat warning stamped at the top of the file:
# This is private dat
What are the state of things and the plan for the future with respect to
iwd and systemd-networkd? A couple of years ago, I put together a
satisfactory solution for my project in OpenEmbedded/Yocto using
systemd-networkd to manage the IP connections and wpa_supplicant to
manage the underlying Wi
Reading this discussion about VT220, I'm wondering why that was the
choice and not VT100 (which was also monochrome). And I'm straining my
memory to recall what it was that we had back then that made the VT100
seem so slick and futuristic.
Bruce A. Johnson | Firmware Engineer
Blue Ridg
have this line anyway? /run is
> writable by default, and I don't see anything which would restrict
> that. ProtectSystem level "true" does not affect /run.
I was specifying /run/rl-web/tmp as being a read-write directory because
I needed the user account that the web servi
I'm trying to figure out how to resolve these errors that are preventing
one of my services from running, and I'm kind of at a loss. Systemd is
stumbling over a read-write directory that needs to be created for the
service.
> Jun 04 09:44:03 url-000db95361f2 systemd[3819]: rl-web.se
Hi Andrei,
> > echo "..." >> /var/log/my-.log
> >
>
> It is not clear where you are using this command. In one of scripts that
> are part of unit definition? In some other script that is run outside of
> running unit? In interactive shell session?
This command is called from the shell script w
Hello,
I am on Ubuntu 18.04.2, and I have systemd version 237. I have some common tasks
which need to happen prestart and poststop which I have moved to a
script. All unit
files look like:
StandardOutput=file:/var/log/my-.log
ExecStartPre=/path/to/helper.sh -t prestart -u
Joerg,
I'm not anything near an expert, but perhaps you could try "PartOf=..."
in the Unit section for the dependent service. I'll be interested in
hearing others' opinion of this idea. But, really, a missing service
file shouldn't get out the door.
Bruce A. Johnson
Is there a directive I can put into a .network or .link file to disable
IPv6 for certain interfaces? I'm trying to prevent the multicast
listener broadcast that goes out when an interface first connects.
Thanks!
--
Bruce A. Johnson | Firmware Engineer
Blue Ridge Networks, Inc.
14120 Parke
htforward and better than wpa_supplicant, but systemd-networkd has
also been straightforward and easy for me to work with. I'd like iwd to
"just work", too.
I'm no deep thinker on the subject of networking, but here you have my
two cents' worth.
Bruce A. Johnson | Firmware E
Is there any way to tell systemd-networkd to use one .network file or
another depending on which SSID the Wi-Fi interface is connected to?
I've been working for a while on a router-like project that has a WAN
interface which normally gets its IP address by DHCP but can be
configured to
I didn't see your in-line comments at first. I'm not part of the systemd
development team (I'm just a "consumer", trying to give back), so I
don't feel comfortable advising you to open a ticket, but I would at
this point if I were you. I'll add a few more comment
Mantas seems to be correct that I was giving you a bum steer about
putting the DHCP=Yes into 25-wireless.network. I haven't used bonding
before, either. So please consider advice from someone who actually
knows what he/she's doing in preference to anything I suggest.
Have a look at h
Doron,
I don't see any mention of DHCP in your wireless network definition, so
I'm dubious that your system has made any attempt at getting an IP
address on wlp2s0. Try adding /DHCP=yes/ to the /[Network]/ section of
25-wireless.network.
I haven't done a wireless setup with s
On 03/20/2018 12:57 AM, Peter A. Bigot wrote:
On 03/19/2018 04:17 PM, Lennart Poettering wrote:
Would be great if you could rework it accordingly and submit it as PR.
https://github.com/systemd/systemd/pull/8494
I've addressed most of the review comments but before pushing a new
ve
On 03/19/2018 04:17 PM, Lennart Poettering wrote:
On So, 18.03.18 20:45, Peter A. Bigot (p...@pabigot.com) wrote:
Like others I'd like to use systemd to defer starting a service until the
system time has been set accurately. Previous approaches to resolving issue
#5097 don't seem t
Like others I'd like to use systemd to defer starting a service until
the system time has been set accurately. Previous approaches to
resolving issue #5097 don't seem to be going anywhere.
https://github.com/pabigot/timesyncwait has my proposed solution: a
standalone service t
My problem seems to be a bug in ethtool-util.c's set_slinksettings().
The base parameters were not being copied into the ethtool_link_settings
request, so they were all zero and ioctl didn't like that. I've pasted
the patch below. Please let me know if there is anything else I ne
I've been trying for a few days to figure out how to set Ethernet speed
and mode using a .link file, and I can't figure out what I'm doing
wrong. I've got a renamed interface ("eth2" -> "en01"), and ethtool
allows me to change it with no problem,
On Tue, Jun 2, 2015 at 1:06 PM, David Herrmann wrote:
> Regarding the final github address: David Strauss kindly offered the
> 'systemd' user to us. Hence, we hope to move the repository to
> github.com/systemd/systemd this week. Sorry for the confusion, I hope
> we can settle all this this week.
Hi,
A French documentation was written about systemd :
http://lea-linux.org/documentations/Systemd
I still think you should cut systemadm entirely out. Unfortunately it's not
only unstable, but also there's little hope of it improving.
Zbyszek
Done. Thanks !
it just showed localhost's journal.
How could i see logs from both localhost and remote in realtime?
Arch Linux
systemd 219-5
Thanks.
--
a
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
t; It is already secured by openvpn tunnel. So I tried with normal http
> settings. Services are launched successfully. There is nothing happening
> in journal. Also there is nothing in /var/log/journal/remote/ .
>
> Also I tried example from man page.
>
> ~~~
> $ ll /tmp/jjj
Hey Lennart & Folks,
I've been watching the commits come in for timesyncd. I saw recently you're
restoring the time from file timestamps, just so something is decently
recent. Neat.
I thought I'd share a problem I had with another init system with regards
to NTP and D
Upstream KDE patch is here:
https://projects.kde.org/projects/kde/kde-workspace/repository/revisions/7584a63924620bac3bd87277c11cdb8cdb5018b1/diff/powerdevil/daemon/backends/upower/powerdevilupowerbackend.cpp?format=diff
___
systemd-devel mailing list
sys
FYI to others experiencing weirdness, the Version api function changed
between 208 and 209:
in 208:
zx2c4@thinkpad ~ $ sudo qdbus --system org.freedesktop.systemd1
/org/freedesktop/systemd1 org.freedesktop.systemd1.Manager.Version
systemd 208
in 209 and 210:
zx2c4@thinkpad ~ $ sudo qdbus --syst
configuration syntax is a bit inconsistent. Which is
better? Should things change?
Jason
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
what we want to 'just work'.
Then those other packages and utilities should be responsible for
starting systemd-networkd, either with a Requires/After, or via
another API for starting it. But keeping it running when there's no
use makes little sense. The whole idea of the dependen
ting networking solutions, but we want them to apply in the very
> special circumstances that we know are safe (in a nspawn container, on
> a device we create ourselves with a specific purpose).
>
But in the case of nspawn using it, then nspawn should start it.
Otherwise if nobody is
To clarify things:
1. Arch's script deals with 80-net-setup-link.rules
2. freedesktop.org wiki followed suit and added that suggestion
3. Others have said elsewhere that the proper way to do this is
actually to override 99-default.link instead.
4. Gentoo went with number 3.
Now:
5. Can numbers 1
On Fri, Feb 21, 2014 at 5:03 PM, Tom Gundersen wrote:
> We'd have to look in all the possible folders, and there may (and due
> to 99-deafult.link, always will) be files there, so we don't really
> have a reasonable test. When we start shipping some default .network
> files
It doesn't make any sense to symlink this unit file into /etc when the
unit file itself isn't even installed, with --disable-networkd. This
moves the GENERAL_ALIASES logic into the right "if" block.
---
Makefile.am | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff
On Fri, Feb 21, 2014 at 4:19 PM, Lennart Poettering
wrote:
>
> Well, ultimately it's up the distributions to decide what they want to
> enable and what not.
True, but this requires manual patching and fixing up of `make
install`, which is a bummer.
> I think networkd
workd, they'll write config files,
which means they're also in a position to type "systemctl enable
systemd-networkd". It doesn't make any sense to enable this by default
during install, since by default it doesn't serve any function. It's
simply a waste of resour
---
configure.ac | 1 +
1 file changed, 1 insertion(+)
diff --git a/configure.ac b/configure.ac
index 80c1449..8943c96 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1150,6 +1150,7 @@ AC_MSG_RESULT([
hostnamed: ${have_hostnamed}
timedated
On Fri, Feb 21, 2014 at 2:08 PM, Tom Gundersen wrote:
> I'll just apply this patch and
> add the /etc symlink in a follow-up.
I appreciate merging my patch, so now administrators can disable it in
a sane way (without having to use mask). But still, why enable it by
default? I thought
built in networking, then it is simple enough to enable. But by default,
it doesn't make sense to waste resources running this when no networks
are configured with it.
---
Makefile.am | 3 ---
units/systemd-networkd.service.in | 3 +++
2 files changed, 3 insertions(+), 3 d
Hi folks,
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?
Jason
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://l
Hey guys,
This commit caught me by surprise:
http://git.zx2c4.com/systemd/commit/?id=daeb71a36a98834664e4d95773a3629b746f4db8
It wasn't in the NEWS or the mailing list post for 209, so when
updating I encountered a bit of unexpected behavior. I see that I can
disable persistent names
Hey guys,
Thought I'd put this discussion upstream. At the moment at Gentoo [1],
we're considering building without the compat-libs, but still with
installing the pkg-config files, so that most out of date packages will
work with a rebuild without having to patch the build system, an
deletions(-)
diff --git a/src/libsystemd/sd-rtnl/rtnl-util.c
b/src/libsystemd/sd-rtnl/rtnl-util.c
index ec1a92e..3bdb4f6 100644
--- a/src/libsystemd/sd-rtnl/rtnl-util.c
+++ b/src/libsystemd/sd-rtnl/rtnl-util.c
@@ -42,7 +42,7 @@ int rtnl_set_link_name(sd_rtnl *rtnl, int ifindex, const char
*name
Ever since the seccomp trick, this is no longer an issue.
---
README | 7 ---
1 file changed, 7 deletions(-)
diff --git a/README b/README
index b918132..df04cc9 100644
--- a/README
+++ b/README
@@ -83,13 +83,6 @@ REQUIREMENTS:
CONFIG_EFI_VARS
CONFIG_EFI_PARTITION
---
kdbus.txt | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/kdbus.txt b/kdbus.txt
index a3d806b..de36672 100644
--- a/kdbus.txt
+++ b/kdbus.txt
@@ -6,7 +6,7 @@ all communication between processes take place over special
character device
changed, 9 insertions(+), 11 deletions(-)
diff --git a/TODO b/TODO
index e74aa7e..63f3f7e 100644
--- a/TODO
+++ b/TODO
@@ -29,8 +29,6 @@ Preparation for 209:
* Review new libraries
-* libsystemd-journal returns the object created as first param in
sd_journal_new(), sd_bus_new() and suchlike as last
man/systemctl.xml | 4
man/systemd-analyze.xml | 4
man/timedatectl.xml | 4
src/shared/pager.c | 19 ++-
8 files changed, 42 insertions(+), 5 deletions(-)
diff --git a/man/journalctl.xml b/man/journalctl.xml
index 3b05e80..18a1b9e 100644
--- a
This allows customization of the arguments used by less. The main
motivation is that some folks might not like having --no-init on every
invocation of less.
---
If you'd like me to update some documentation, let me know what
files I should edit, and I'll send a v2.
src/shared/pa
On Tue, Feb 11, 2014 at 6:40 PM, Lennart Poettering
wrote:
>
> I think adding support for $SYSTEMD_LESS which is copied to $LESS right
> before invoking less would be a good choice, since it would allow people
> to override whatever systemd tries to set.
So something along
this...
My drivers are compiled into my kernel, and the kernel is on the same
drive (though a different partition) as the one that's going to be
cryptsetup'd. Things work super well and super simply. It's very
minimal. As far as I can see with my particular setup, there are no
potenti
> On Tue, Feb 11, 2014 at 5:25 PM, Lennart Poettering
> wrote:
> Hmm, so how do you wait for the LUKS device to show up? You need
> something like udev around, which uses /run...
> And AFAIR the DM userspace does keep some runtime state around, and that
> one probably wants to pass over to the ho
On Tue, Feb 11, 2014 at 6:25 PM, Colin Guthrie wrote:
> As has been mentioned elsewhere on this thread, there are a number of
> "gotchas" and corner cases, that this mechanism solved, even in the
> cases of things "working".
In my case, I'm just using devtmpfs
f an initrd, I just use cryptsetup, which AFAIK, isn't a
storage daemon but rather reads the LUKS header, determines the key,
and calls the ioctl to get it mapped. In this case, all the 'state'
remains in the kernel, and thus doesn't require /run.
___
On Tue, Feb 11, 2014 at 5:15 PM, Dave Reisner wrote:
> I don't think there's any change needed here. The interface states:
>
> "The initrd should mount /run as a tmpfs".
> And sure enough, this isn't a requirement, but there's many valid
> reason
On Tue, Feb 11, 2014 at 5:01 PM, Dave Reisner wrote:
> Strange name. I can't find one thing which I find "better" about this
> project compared to the more well-known initramfs creation tools.
I'd appreciate it if you kept the antagonism to a minimum. It adds
nothing t
On Tue, Feb 11, 2014 at 5:01 PM, Dave Reisner wrote:
> systemd is already capable of setting up /run on its own:
>
> http://cgit.freedesktop.org/systemd/systemd/tree/src/core/mount-setup.c#n69
You appear to be right.
In that case should the spec [1] be amended to remove this requirement?
[1] ht
Hey folks,
I'm using better-initramfs [1], a very small and minimal initrd that
has been working very well for me. In switching to systemd, I found it
necessary to have the initrd mount "/run" as tmpfs, according to the
specs [2]. I made a little patch for better-initramfs, and now
On Tue, Feb 11, 2014 at 7:09 AM, Andrey Borzenkov wrote:
> Should not it simply respect existing LESS value? Or, for that matter,
> SYSTEMD_LESS if someone thinks of a good reason to have different
> settings?
Yes, one way would be to look at LESS from the environment, and prefer
th
I use konsole. It has a nice feature that when the scrollbars have been
disabled -- like in the case of a full-console app like vim or less --
it makes the mouse wheel send up and down key strokes, so that
scrolling happens. It's really nice. I open up less, and then I can
scroll through it
Hi folks,
I hope this is the right list to ask about udev. I've got a lenovo usb
keyboard with a trackpoint on it -- essentially an external replica of
the classic thinkpad keyboard. The trackpoint by default isn't very
sensitive, so I've got a udev rule that applies the settings
Hi folks,
Forgive me in advance if the underlying reasonings behind these
questions are a bit naive...
Will kdbus make use of polkit? If partially so, will it be feasible to
have a normal desktop system with systemd+kdbus that does not require
polkit? Will polkit play a smaller role going
Hi folks,
Forgive me in advance if the underlying reasonings behind these
questions are a bit naive...
Will kdbus make use of polkit? If partially so, will it be feasible to
have a normal desktop system with systemd+kdbus that does not require
polkit? Will polkit play a smaller role going
Perfect, thanks!
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
I'd like to have a rule that does this:
zx2c4@thinkpad /etc/udev/rules.d $ cat 90-hotkeys.rules
DRIVER=="thinkpad_acpi", ATTR{hotkey_mask}=ATTR{hotkey_recommended_mask}
Unfortunately, it "doesn't work."
This works:
zx2c4@thinkpad /etc/udev/rules.d $ cat 90-hotkey
Hi systemd experts,
I have a question about the dependence of user and system session. At system
session, there is a service which need to be started after X(user session).
At first I added "After=xorg.target" at this service, but It is said that the
dependence of cross session is no
moving to the mailing list:
On 03/26/2013 09:04 PM, Lennart Poettering wrote:
On 26.03.2013 19:21, David Marlin wrote:
I am trying to make the serial console automatically log in a user on
boot. I tried modifying:
/lib/systemd/system/serial-getty@.service
/lib/ is package manager
Hi, I'm using kernel 3.0.1 and systemd, the boot process hangs. I am
booting from an SD Card using the BeagleBoard.
I am passing "systemd.log_target=kmsg systemd.log_level=debug" in my
boot arguments but I don't see any debug messages.
Could anyone help me out? Thanks
Starting udev Coldplug all
83 matches
Mail list logo