summaryrefslogtreecommitdiffstats
path: root/man/rules (unfollow)
Commit message (Collapse)AuthorFilesLines
2020-03-29sd-bus: Add sd_bus_slot_get_current_* docsDaan De Meyer1-2/+5
2020-03-29README.md: add repology badgeTopi Miettinen1-1/+2
Show downstream usage for various versions of systemd.
2020-03-29basic: Fix capability_ambient_set_apply for kernels < 4.3Kevin Kuehler1-0/+4
https://github.com/systemd/systemd/pull/14133 made capability_ambient_set_apply() acquire capabilities that were explicitly asked for and drop all others. This change means the function is called even with an empty capability set, opening up a code path for users without ambient capabilities to call this function. This function will error with EINVAL out on kernels < 4.3 because PR_CAP_AMBIENT is not understood. This turns capability_ambient_set_apply() into a noop for kernels < 4.3 Fixes https://github.com/systemd/systemd/issues/15225
2020-03-28device: don't emit PropetiesChanged needlesslyMichal Sekletár1-3/+0
Functions called from device_setup_unit() already make sure that unit is enqueued in case it is a new unit or properties exported on the bus have changed. This should prevent unnecessary DBus wakeups and associated DBus traffic when device_setup_unit() was called while reparsing /proc/self/mountinfo due to the mountinfo notifications. Note that we parse /proc/self/mountinfo quite often on the busy systems (e.g. k8s container hosts) but majority of the time mounts didn't change, only some mount got added. Thus we don't need to generate PropertiesChanged for devices associated with the mounts that didn't change. Thanks to Renaud Métrich <rmetrich@redhat.com> for debugging the problem and providing draft version of the patch.
2020-03-28device: make sure we emit PropertiesChanged signal once we set sysfsMichal Sekletár1-0/+2
2020-03-28Add a device to 60-sensor.hwdb 24bisquitz1-0/+4
Adding support for a Dell Venue 8 Pro tablet. Rotation was off by 90° to the left initially, the proposed change fixes the issue on my device.
2020-03-28sd-journal: remove the dead code and actually fix #14695Michal Sekletár1-4/+3
journal_file_fstat() returns an error if we call it on already unlinked journal file and hence we never reach remove_file_real() which is the entire point. I must have made some mistake while testing the fix that got me thinking the issue is gone while opposite was true. Fixes #14695
2020-03-28networkctl: Add support to display DHCP pop3 serversSusant Sahani1-1/+6
2020-03-28sd-network: Add support to emit and receive pop3 server informationSusant Sahani2-0/+7
2020-03-28DHCP: Add support to emit and retrieve POP3 serverSusant Sahani8-9/+168
2020-03-28libsystemd-network: DHCP add support to emit and retrive DHCP POP3 serverSusant Sahani7-2/+71