> (the way I'd implement this, is not by actually teaching these
> commands individual multi-ESP support, but simply by implementing a
> single sync_esp() call or so which syncs the relavant info from
> primary to secondary ESPs correctly, and that each of these commands
> just call as last step.
On Fri, May 17, 2024, at 05:03, Alexander Gordeev wrote:
> I think it is better to have them mounted as e.g. /boot/efi and
> /boot/eficopy and make changes like this:
> 1. update /boot/efi
> 2. make sure the update is actually written to the device
> 3. update /boot/eficopy
>
> Right now I do this
On Sun, Mar 10, 2024, at 16:14, Ricardo wrote:
> On a custom systemctl service, when start service it seems starting without
> any message, but when it check by journalctl command it reporter as Failure.
>
> But if manually run service program it starts without any problem and message.
>
> The
I believe you want KeepConfiguration="static".
On Wed, Sep 13, 2023, at 18:32, Jeremy Friesner wrote:
> Hi all,
>
> I apologize for this basic question, but I haven’t been able to figure it out
> on my own.
>
> I’m working on an embedded device, which includes a little GUI that (among
> other
On Fri, Aug 4, 2023, at 18:11, Ross Boylan wrote:
> Theory: since br0 has no associated IP address when socket creation is
> attempted, the socket creation fails. If so, I need to delay socket
> startup until br0 has an IP4 address, but I'm not sure how to do
> that--or even if that is the
That's how I do it. Path units are a good solution here as they maintain loose
coupling between the cert management and consumption.
On Mon, Jul 31, 2023, at 16:56, Max Gautier wrote:
> On Mon, Jul 31, 2023 at 03:23:26PM -0500, Ian Pilcher wrote:
>> I have created service (along with an
As I use systemd more and more I find myself needing to express complex
dependencies between units. While systemd provides many 'building blocks' which
can be combined to satisfy the requirements, determining which blocks to use,
and the pros/cons of each combination, is non-trivial.
On Thu, Mar 30, 2023, at 09:35, f...@igh.de wrote:
> [Match]
> name = eth0
> SSID = my-wifi
>
> would that mean, that "my-wifi" must be accessible via that interface
> (AND logic) or could that mean we configure "eth0" while "my-wifi" is
> visible on any interface (OR logic)? I had
On Wed, Feb 15, 2023, at 05:31, Aditya Sharma wrote:
> We were thinking of an approach where we keep on serving the last known good
> FQDNs even after the TTL has expired (only when we are unable to communicate
> with the resolvers). For that, we need to intercept the DNS calls and
> maintain
On Tue, Feb 14, 2023, at 04:04, Aditya Sharma wrote:
> Hi Kevin,
>
> *If what you mean is that you want to serve 'stale' records from a cache when
> their TTLs have expired and the authoritative servers which provided them are
> not reachable, that's something that a number of existing
On Mon, Feb 13, 2023, at 05:38, Aditya Sharma wrote:
> Hi All,
>
> We needed help in understanding how systemd-resolved service can be extended
> to cache DNS responses to protect against DNS server failures.
> We were planning to maintain a cache so that we can override negative
> responses
On Tue, Jan 10, 2023, at 06:47, Markus Rathgeb wrote:
>
> How can I declare test2 unit section to ensure it works as expected by me?
>
There are lots of StackOverflow posts about this... it's not as easy as it
seems, so don't feel concerned that your attempt did not work :-)
If you are using a
I've just setup a new system running Debian Bookworm, so it has the
Debian systemd 251.4-3 packages installed. There's a bonded network
interface setup with systemd-networkd.
During boot, networkd attempts to send a router solicitation but fails
with "No buffer space available". I don't know why
On Thu, Sep 22, 2022 at 12:21 PM Kevin P. Fleming wrote:
> For now I will use an OCF-style resource agent (fancy shell script)
> which uses 'networkctl' to do the work, but later I'll consider making
> something more 'native'. My primary motivation for having a 'native'
> RA is reduc
On Thu, Sep 22, 2022 at 9:45 AM Lennart Poettering
wrote:
>
> On Mi, 21.09.22 06:48, Kevin P. Fleming (ke...@km6g.us) wrote:
>
> > When the D-Bus API for systemd-networkd was added there were
> > indications that it could be used for bringing links up and down.
> > How
When the D-Bus API for systemd-networkd was added there were
indications that it could be used for bringing links up and down.
However, when I review the API docs at:
https://www.freedesktop.org/software/systemd/man/org.freedesktop.network1.html#
I don't see any methods for doing those
On Mon, Sep 5, 2022 at 1:45 PM Arian van Putten
wrote:
>
> Just thinking out loud here but aren't RA messages are sent as link local
> multicast messages? How can it send them if you disable link local addressing?
Yes, this. There's no benefit to disabling link-local addressing, and
doing so
On Tue, Aug 9, 2022 at 12:43 PM Thomas Archambault
wrote:
> One obvious issue is the non-zero return from an ioctl call with the
> BTRFS_IOC_SUBVOL_CREATE arg at line 410, in the snippet below from my
> RHEL9.0 strace capture; this is occurring right after the initial blast
> of debug log
On Sat, Jul 30, 2022 at 8:45 AM Chris Murphy wrote:
>
>
>
> On Thu, Jul 28, 2022, at 6:50 AM, Kevin P. Fleming wrote:
> > I've got two systems that report a failure (exit code 1) every time
> > systemd-gpt-auto-generator is run. There are a small number of reports
>
Thanks! I hadn't paid any attention to that issue since I'm not using
btrfs, but it seems that the root cause is the same.
On Thu, Jul 28, 2022 at 9:31 AM Lennart Poettering
wrote:
>
> On Do, 28.07.22 07:40, Kevin P. Fleming (ke...@km6g.us) wrote:
>
> > Thanks for that, it did
ctory)
close(4)
So it's trying to open() /sys/dev/block/0:0, but my system does not
have that device file. The only files in /sys/dev/block are 8:0
through 8:3.
On Thu, Jul 28, 2022 at 7:17 AM Mantas Mikulėnas wrote:
>
> On Thu, Jul 28, 2022 at 1:51 PM Kevin P. Fleming wrote:
>>
>
I've got two systems that report a failure (exit code 1) every time
systemd-gpt-auto-generator is run. There are a small number of reports
of this affecting other users too:
https://bugs.archlinux.org/task/73168
This *may* be related to the use of ZFS, although I've got a
half-dozen systems
After using nspawn for a couple of years I finally realized that I
wasn't getting the PrivateUsersChown behavior that I expected, and
looked into it.
I'm using systemd 247 on Debian, which has the standard nspawn
template service unit file which includes '-U' (and
'--settings=override').
On Wed, Jun 15, 2022 at 5:03 PM Barry wrote:
> To be robust why not make the services recover from network issues?
> Then you do not need to care about the routes.
> Of course you will need to know if services have outages.
>
> Even if a route was working at some point what do you do if the route
s for systemd-networkd, and then once more for
> nss_myhostname...)
>
> On Wed, Jun 15, 2022, 14:32 Kevin P. Fleming wrote:
>>
>> I've got a number of systems that use BIRD to learn the routes
>> available on their networks, and as a result some services on those
>> systems at
I've got a number of systems that use BIRD to learn the routes
available on their networks, and as a result some services on those
systems attempt to start up before the routes have been learned. If
those services attempt to make network connections (even just DNS
queries), they will fail, and
This sort of behavior has been a long-standing desire of many systemd
users, and you can find probably thousands of blog/forum/SO posts
about it. As Andrei said, the names of the dependencies in systemd
units might appear to be the behavior you want, but they aren't.
If you have a situation where
Is this just a Debian (and derivatives) feature, or more common?
I just spent nearly an hour trying to figure out why the link file
changes I'd made on a system were not working properly, and this was
the cause. I even ran 'networkctl status' on an interface that should
no longer exist, and it
wrote:
>
> On 24/01/2022 11:08, Kevin P. Fleming wrote:
> > According to 'man systemd.unit' it goes in the '[Unit]' section, like
> > all other dependency statements.
>
> Thank you very much. The usual problem of "where's the docu I'm looking
> for?" :-)
>
>
According to 'man systemd.unit' it goes in the '[Unit]' section, like
all other dependency statements.
On Sun, Jan 23, 2022 at 3:15 PM Wols Lists wrote:
>
> On 23/01/2022 19:44, Andrei Borzenkov wrote:
> > Where dependency to /home comes from? It is not in your unit file.
>
> If it thinks my
On my two systems that are running systemd 249.5-1 (Debian sid
packages), I see this message in the journal once for each network
interface that systemd-networkd manages:
Could not drop routing policy rule: No such file or directory
I don't have any routing policies configured on the systems, so
You might consider having systemd itself create the listening sockets
and then pass them into the service; if you did that, then systemd
would already know the port number that was allocated for the socket.
On Mon, Jun 14, 2021 at 9:17 PM John Ioannidis wrote:
>
> I have an instanced service
It's fairly simple to add a one-shot service unit to use 'hwclock' to
read from the RTC and set the kernel's real-time clock. I do this on
my RPis which use modules for their RTCs.
On Mon, Mar 1, 2021 at 9:02 AM Michał Zegan wrote:
>
> Someone should really find a way to make it cooperate well
Agreed, I run timesyncd on 20+ machines on a bunch of VLANs that are
all IPv6-enabled with RAs being used, and have not seen this symptom.
On Thu, Feb 11, 2021 at 11:23 AM Mantas Mikulėnas wrote:
>
> On Thu, Feb 11, 2021 at 6:07 PM Ede Wolf wrote:
>>
>> Thanks. Indeed, stopping radvd made these
packages aren't at fault, and then adding
more debugging output in the necessary places.
On Sun, Jan 24, 2021 at 10:14 AM Kevin P. Fleming wrote:
>
> I've got three systems which host nspawn-based containers, using
> networkd for network configuration on both the host and inside the
>
I've got three systems which host nspawn-based containers, using
networkd for network configuration on both the host and inside the
containers. All of the systems are running Debian systemd packages
(some version 241 (buster) and some 247.2 (bullseye)). The behavior
has been seen with kernels 5.4,
While I can't comment on the specifics of configuring systemd-networkd
to use ports through DSA (although the linked GitHub issue shows that
it can be done), I really doubt you are going to be able to
successfully bond any group of such ports, because they all have the
same MAC address. In your
If you are using NetworkManager to manage your links, then you need to
convince it to stop providing the DNS resolver information. You can't
use a systemd-networkd file to override this, as networkd is not
managing the links.
On Thu, Sep 24, 2020 at 11:10 AM Roman Odaisky wrote:
>
> Hi,
>
> >
In your network configuration for the faulty link you can just set
"UseDNS=no" in the 'DHCPv4' section and then resolved will not even
try to use those resolvers.
On Thu, Sep 24, 2020 at 7:45 AM Roman Odaisky wrote:
>
> Hi,
>
> I have the following resolved configuration:
>
> [Resolve]
>
On Tue, Sep 8, 2020 at 7:12 AM Reindl Harald wrote:
> your playground is in
> /etc/systemd/system/fake-hwclock.service.d/myoverrides.conf
>
> and yes that is important so that you don#t have to redo your changes
> after each and every update and way better than cloning the whole
> unit-file in
On Mon, Sep 7, 2020 at 11:58 AM Lennart Poettering
wrote:
> Not sure I can parse this. Both timers and services are units in
> systemd. You can enable timer units, and you can enable service units,
> it all depends on what you put in their [Install] section. Sometimes
> it makes sense to add an
On Mon, Sep 7, 2020 at 4:41 AM Ulrich Windl
wrote:
> I can't remember, but very recently I read that you can add an RTC to
> raspberries via GPIO. Ah, I think I read it in the SLES15 SP2 deployment
> guide.
It's typically done via I2C; there are quite inexpensive DS-1307
modules that plug onto
On Mon, Sep 7, 2020 at 4:22 AM Reindl Harald wrote:
> a timer is the same trigger as "enable" and get startet as part of the
> boot process
>
> * letsencrypt.timer
> * letsencrypt.service
>
> letsencrypt.service don't even have a [Install] section and can't be
> enabled at all
'disabling' a
On Sat, Sep 5, 2020 at 9:50 AM Michael Chapman wrote:
> Since the instance name for this unit is used to derive a configuration
> filename, a simple solution here would be to use:
>
> ConditionPathExists=/etc/openvpn/client/%i.conf
>
> in the unit. Or, if you want the start job to fail when
It's a general issue with templated unit files; I've had this happen
as well, and could not figure out why the service had failed to start.
It was because I had mistyped the instance name. As best I can tell
systemd doesn't have any mechanism to restrict the instance names
which can be used for a
I've run into similar issues and resorted to adding battery-backed
RTCs to my RPis in order to ensure that the kernel's clock would be
set to something 'reasonable' very early in the boot process (although
it's still not ideal since the RTC drivers are loaded as modules so
the kernel's code for
Ahh, you're right. I do not 'enable' my timer-activated service units,
since 'enable' just processes the WantedBy/similar specifications to
create symlinks.
On Mon, Aug 31, 2020 at 4:50 PM Konstantin Ryabitsev
wrote:
>
> On Mon, Aug 31, 2020 at 04:49:32PM -0400, Kevin P. Fleming wrote:
&
Yes, to get the instance-named symlink created.
On Mon, Aug 31, 2020 at 4:36 PM Konstantin Ryabitsev
wrote:
>
> On Mon, Aug 31, 2020 at 04:20:13PM -0400, Kevin P. Fleming wrote:
> > Did you also create an instance of the timer with the same instance
> > suffix? I've got a con
Did you also create an instance of the timer with the same instance
suffix? I've got a configuration working like that and it works fine.
If you don't want to do that, you can explicitly configure the name of
the service to be triggered (in the timer unit) instead of relying on
the timer/service
On Fri, Jun 26, 2020 at 3:39 AM Ede Wolf wrote:
>
> > I do this today using a drop-in, because environment variables can be
> > set there as well. It works very well, exactly as you describe. There
> > is a template service unit file, and a drop-in directory for each
> > instance which contains a
On Thu, Jun 25, 2020 at 4:04 PM Ede Wolf wrote:
> This way I would only have to take care of _one_ external file to get
> another instance of service foo up and running. Copy the file, change
> the few options for the unit as well as for the service in ONE place,
> startup the template. Ultra
Normally you'd set instance-specific variables using an override file
for the unit. You could easily put just 'User' and 'LimitMEMLOCK' in
the override file and leave the rest of the service settings in the
main unit file, with no need for an environment variable file at all.
On Thu, Jun 25, 2020
Do you have a udev 'persistent network device name' rules file in
/etc/udev/rules.d? Many distributions install such a rules file by
default, and this renames the interfaces to 'standard' names.
On Fri, May 22, 2020 at 3:47 AM Ede Wolf wrote:
>
> Hello,
>
> I am trying to enable temporary and/or
You have to accept RAs from upstream, unless you have a static route
to the ISP's gateway. DHCPv6 does not provide routing information,
only end-node addressing information, so with RAs ignored you won't
have a default route out of your network.
This is probably the largest, and most surprising,
What does 'update the system' mean for you?
On Fri, Apr 17, 2020 at 6:10 AM www wrote:
>
>
> I mean that this configuration can be preserved, even after I update the
> system, this function can be saved.
>
> thanks，
> Byron
>
>
>
>
> At 2020-04-17 18:06:15
e if I close it alone every time. So when I need it start
> every time, this function is off.
>
>
> thanks,
> Byron
>
>
>
>
>
> At 2020-04-16 18:28:30, "Kevin P. Fleming" wrote:
> >There is no need to modify systemd.
> >
> >$ systemctl dis
I have a working-well configuration using PowerDNS Recursive Resolver
(running locally in my network, not provided by my ISP or anyone
upstream).
On Thu, Apr 16, 2020 at 12:46 PM Fabian Bernhard Pack
wrote:
>
> Hi,
>
> I've been slowly integrating systemd-resolved more and more into my
> setups,
There is no need to modify systemd.
$ systemctl disable systemd-timesyncd
That command will stop the systemd-timesyncd service from being
started. It may also be necessary to mask it:
$ systemctl mask systemd-timesyncd
On Thu, Apr 16, 2020 at 6:22 AM www wrote:
>
> Dear all，
>
> I want to ask
'git grep 32' would be more effective :-)
On Wed, Apr 15, 2020 at 4:50 PM Andy Pieters wrote:
>
> On Wed, 15 Apr 2020 at 21:46, Tarun Chinmai Sekar wrote:
> >
> > Hello Lennart,
> > Thank you for the quick response. I'd love to submit a PR to increase the
> > limit. Can you please point me to
Yes, I agree with you there.
On the other part I imagine there may be some way to trigger a service
to be run when a prefix on a link is being taken out of service.
On Mon, Apr 13, 2020 at 11:51 AM Tobias Brink wrote:
>
> "Kevin P. Fleming" writes:
>
> > This i
This is a bit tricky, since RAs and prefix delegation are not really
related. What you have described is proper behavior on the 'upstream'
link side; when networkd sees the RA with the new prefix, and the
lifetime of the old prefix set to zero, it properly adjusts that link
to use the new prefix.
Dorian: Please find a French-language support forum or mailing list
for Fedora Linux. They'll be glad to help you, and will be able to
address your questions in the Fedora system.
On Tue, Apr 7, 2020 at 6:08 PM Dave Howorth wrote:
>
> I'm not sure why Lennart hasn't stepped in to moderate yet,
The simple service unit I posted later in the thread (which invokes
hwclock) works great for me.
On Tue, Mar 31, 2020 at 1:29 PM Michał Zegan wrote:
>
> I have used the embedded term unfortunately, but it seems to affect at
> least some devices like raspberry pi, odroid c2, like sbc's.
>
> W
Input files for systemd-networkd are not systemd unit files, so
there's a good chance that the rules for finding and processing them
are much simpler. That would explain why template/instance files don't
work.
The manpage for systemd.network does indicate that files will be
loaded from
--hctosys --utc
[Install]
WantedBy=basic.target
On Thu, Mar 12, 2020 at 7:26 PM Dave Howorth wrote:
>
> On Thu, 12 Mar 2020 17:35:16 -0400
> "Kevin P. Fleming" wrote:
> > Thanks, I agree. I could some up with something which ran timedatectl
> > to set the system tim
part
of systemd to read the RTC, or they expect some other service/tool to
do it.
On Thu, Mar 12, 2020 at 2:02 PM Mike Gilbert wrote:
>
> On Thu, Mar 12, 2020 at 7:13 AM Kevin P. Fleming wrote:
> > Prior to systemd, with the 'hwclock' package installed, a udev rule
> > wou
I've got some Debian Buster systems (so using the Debian systemd
package 241-7), which have battery-backed RTCs. However the driver for
these RTCs is loaded as a module, not built into the kernel. As a
result the kernel's feature of reading the RTC to set the system clock
is not available.
Prior
67 matches
Mail list logo
