| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, if a unit file is enabled from outside of the search path,
and that unit has an alias, then the symlink ends up pointing outside of
the search path too. For example:
$ cat /tmp/a.service
[Service]
ExecStart=sleep infinity
[Install]
Alias=b.service
WantedBy=multi-user.target
$ systemctl enable /tmp/a.service
Created symlink /etc/systemd/system/a.service → /tmp/a.service.
Created symlink /etc/systemd/system/b.service → /tmp/a.service.
Created symlink /etc/systemd/system/multi-user.target.wants/a.service → /tmp/a.service.
This then means the alias is treated as a separate unit:
$ systemctl start a.service
$ sudo systemctl status a
● a.service
Loaded: loaded (/etc/systemd/system/a.service; enabled; preset: enabled)
Active: active (running) since Fri 2024-03-15 15:17:49 EDT; 9s ago
Main PID: 769593 (sleep)
Tasks: 1 (limit: 18898)
Memory: 220.0K
CPU: 5ms
CGroup: /system.slice/a.service
└─769593 sleep infinity
Mar 15 15:17:49 six systemd[1]: Started a.service.
$ sudo systemctl status b
○ b.service
Loaded: loaded (/etc/systemd/system/b.service; alias)
Active: inactive (dead)
To fix this, make sure the alias uses a target that is inside the search
path. Since the unit file itself is outside of the search path, a
symlink inside the search path will have been created already. Hence,
just point the alias symlink to that recently created symlink.
|
|\
| |
| | |
network: pin file descriptor of persistent storage
|
| |
| |
| |
| |
| |
| | |
This also drop the support of /run/systemd/netif/persistent-storage-ready,
as the file is anyway removed when networkd is stopped.
Let's use $SYSTEMD_NETWORK_PERSISTENT_STORAGE_READY=1 instead on testing.
|
|/ |
|
| |
|
|
|
|
|
|
| |
If both $ARTIFACT_DIRECTORY and $SPLIT_TEST_LOGS are set, split the
output from each test into a separate log file, so we don't have to load
one ginormous log file when checking the results.
|
| |
|
|\
| |
| | |
dhcp-server: save bound leases to persistent storage, and load it on start
|
| | |
|
| | |
|
| |
| |
| |
| | |
Addresses https://github.com/systemd/systemd/pull/30021#issuecomment-1971090682.
|
| |
| |
| |
| |
| | |
This also renames several variables, and replace RuntimeError with
assert.
|
| |
| |
| |
| |
| |
| |
| |
| | |
In automated QA environments there may be tests that are known to fail,
and being able to skip them is useful to remove known failures from the
test log.
Signed-off-by: Ross Burton <ross.burton@arm.com>
|
|/
|
|
|
|
|
| |
When reading test logs manually it is a lot easier when the tests are
sorted by name rather than by disk order.
Signed-off-by: Ross Burton <ross.burton@arm.com>
|
|
|
|
|
| |
Now that we have an address, hostname, and service resolve, at the last
kind of resovler we expose over D-Bus also to Varlink.
|
|\
| |
| | |
resolved: proxy upstream local requests to our stub with DO bit set
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
dig question with DNSSEC on will now be proxied upstream, i.e. to the
test knot server. This leads to different results, but the result isn't
tha tinteresting since we don't want to test knot, but resolved. Hence
comment this test.
There seems to be something wrong with the test though, as the upstream
server refused recursion, but if so it is not suitable as an upstream
server really, as resolved can only be client to a recursive resolver.
|
|/
|
|
|
|
|
|
| |
As explained in [0] the 'hosts' database uses deprecated
gethostbyname2() which uses AF_INET6 instead of AF_UNSPEC for IPv6
lookups which is broken and makes the test fail with disabled IPv6.
[0] https://github.com/systemd/systemd/pull/28136#issuecomment-1974901039
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
sulogin from the latest util-linux started falling back to vt102 instead
of linux, which makes screen sad (because we install only the linux
terminfo into the test image) and expect trips over the unexpected
warning. Let's just explicitly set TERM=linux before invoking screen to
avoid this.
+ make -C TEST-69-SHUTDOWN setup run
...
INFO:test-shutdown:log in and start screen
root
root
Last login: Sun Mar 3 13:19:31 from 18.191.105.60
-bash-5.2# screen
screen
Cannot find terminfo entry for 'vt102'.
-bash-5.2# ERROR:test-shutdown:Timeout exceeded.
|
|\
| |
| | |
udev: follow-ups for RPS setting
|
| |
| |
| |
| |
| |
| |
| |
| | |
Otherwise, even if the interface is available, the requested config may
not be applied to the interface yet.
This also merges multiple tests for RPS setting. Hopefully the
performance of the test is improved.
|
| | |
|
|/
|
|
| |
Addresses https://github.com/systemd/systemd/pull/31583#discussion_r1509880349.
|
|
|
|
|
| |
(these are explicit tests, on top of the existing machinectl tests that
are now chainload importctl)
|
|
|
|
|
| |
A follow up for 8fddb50fd4de43993c4906baf19dae89ff8a021b, which mirrors
the change also in test 74.
|
| |
|
|\
| |
| | |
netdev: bond - add support for peer_notif_delay
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
sshd.service on Debian uses RuntimeDirectory=sshd, without which sshd
complains:
[ 4065.834904] sshd[711]: Missing privilege separation directory: /run/sshd
[ 4065.835785] systemd[1]: mysshserver@0-127.0.0.1:4711-127.0.0.1:58232.service: Deactivated successfully.
[ 4065.836433] testsuite-46.sh[708]: kex_exchange_identification: read: Connection reset by peer
[ 4065.836433] testsuite-46.sh[708]: Connection reset by 127.0.0.1 port 4711
Resolves: #31518
|
| |
| |
| |
| | |
Addresses: https://github.com/systemd/systemd/issues/31518#issuecomment-1968295678
|
| |
| |
| |
| |
| | |
This should make the test faster, especially on machines without
acceleration.
|
| | |
|
|\ \
| | |
| | | |
semaphore: set upstream build profile and set default branch to debian/master
|
| | |
| | |
| | |
| | | |
the CI to a new version
|
| | | |
|
|\ \ \
| |_|/
|/| | |
udevd: Add ReceivePacketSteeringCPUMask for systemd.link
|
| | | |
|
| |/
|/|
| |
| | |
Follow-up for a663ddc04e43a9234e00e47aed98bf2bbeb1573a.
|
|\ \
| | |
| | |
| | |
| | | |
keszybz/small-cleanups-after-review-of-stable-batch
Small cleanups after review of stable batch
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
`c->cpu_sched_reset_on_fork` is serialized using
`exec-context-cpu-sched-reset-on-fork` and
`exec-context-cpu-scheduling-reset-on-fork`. Let's keep only the second one, to
serialize the value only if `cpu_sched_set` is true.
|
| | |
| | |
| | |
| | |
| | | |
I do not see `route` being exercised anywhere else, everything seems
to be on `ip route` already.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
By default socat open a separate r/w channel for each specified address,
and terminates the connection after .5s from receiving EOF on _either_
side. And since one side of that connection is an empty stdin, we reach
that EOF pretty quickly. Let's avoid this by using socat in
"reversed unidirectional" mode, where the first address is used only for
writing, and the second one is used only for reading.
Addresses:
- https://github.com/systemd/systemd/issues/31500
- https://github.com/systemd/systemd/issues/31493
Follow-up for 3456c89ac26.
|
|\ \
| |/
|/| |
systemd-sysext: Implement optional mutability for extensions
|
| | |
|
| |
| |
| |
| |
| |
| | |
The follow-up commit will refactor some code in systemd-sysext, so add some
tests to make sure that things didn't break. The tests will be later extended
with cases for new features added.
|
|\ \
| | |
| | | |
Restore docs urls
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 5e8ff010a1436d33bbf3c108335af6e0b4ff7a2a.
This broke all the URLs, we can't have that. (And actually, we probably don't
_want_ to make the change either. It's nicer to have all the pages in one
directory, so one doesn't have to figure out to which collection the page
belongs.)
|