summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2013-11-20bus: bump serial number counter when sending already sealed messagesLennart Poettering
2013-11-20bus: sd_bus_error_setxyz calls should always return the error as errno style ↵Lennart Poettering
negative int
2013-11-20libudev: always return NULL in _unref() APIsLennart Poettering
Returning anything else but NULL would suggest the caller's reference might still be valid, but it isn't, because the caller just invoked _unref() after all. This turns the return value into a typesafe shortcut that allows unreffing and resetting a reference in one line. In contrast to solutions for this which take a pointer to a pointer to accomplish the same this solution is just syntactic sugar the developer can make use of but doesn't have to, and this is particularly useful when immediately unreffing objects returned by function calls.
2013-11-20libudev: always return valid negative error codes on API functionsLennart Poettering
2013-11-20calendar: support 'yearly' and 'annually' names the same way as cronLennart Poettering
2013-11-20hwclock: modernizationsLennart Poettering
2013-11-20macro: add _unlikely_() to assert_return()Lennart Poettering
As the name indicates assert_return() is really just for assertions, i.e. where it's a programming error if the assertion does not hold. Hence it is safe to add _unlikely_() decorators for the expression to check.
2013-11-20macro: change assert_cc() so that it can appear outside of functionsLennart Poettering
2013-11-20include: make direct includion of _sd-common.h harderLennart Poettering
2013-11-20install: use const where we canLennart Poettering
2013-11-20conf-parser: don't leak section namesTom Gundersen
If we encounter an unknown section, we must free the previous section before clearing the pointer.
2013-11-20event: clear pending-state when re-arming timersDavid Herrmann
If a timer fires and is marked pending, but an application re-arms it before it is dispatched, we now clear the pending state. This fixes a bug where an application arms a timer, which fires and is marked pending. But before it is dispatched, the application loses interest in it and disables it. Now if the timer is re-armed and re-enabled later, it will be immediately dispatched as it is still marked pending. This behavior is unexpected, so avoid it by clearing pending state when re-arming timers. Note that applications have no way to clear pending state themselves, so there's no current workaround.
2013-11-20bus: fix error-path in bus_map_all_properties()David Herrmann
We shouldn't return positive integers on errors. Fix the typo by removing the negation.
2013-11-20bus/rtnl: silence clang warningsThomas Hindoe Paaboel Andersen
2013-11-19networkd: make sure Links and Networks are freedTom Gundersen
2013-11-19keymap: Add Toshiba Satellite U940Jose Ignacio Naranjo
Signed-off-by: Martin Pitt <martinpitt@gnome.org>
2013-11-18localed: match converted keymaps before legacyZbigniew Jędrzejewski-Szmek
Before, X11 keymap fr-pc105-oss would be converted to fr, even though fr-oss exists. Now, if /usr/lib/kbd/keymaps/xkb/<layout>[-<variant>].map[.gz] exists, <layout>[-<variant>] will be used as the console keymap, falling back to the legacy mappings otherwise. % sudo localectl set-x11-keymap pl pc105 % localectl System Locale: LANG=en_US.UTF-8 VC Keymap: pl (was pl2 before) X11 Layout: pl X11 Model: pc105 % sudo localectl set-x11-keymap fr pc105 oss % localectl System Locale: LANG=en_US.UTF-8 VC Keymap: fr-oss (was fr before) X11 Layout: fr X11 Model: pc105 X11 Variant: oss % sudo localectl set-x11-keymap fr pc105 % localectl System Locale: LANG=en_US.UTF-8 VC Keymap: fr X11 Layout: fr X11 Model: pc105 % sudo localectl set-x11-keymap gb % localectl System Locale: LANG=en_US.UTF-8 VC Keymap: gb (was uk before) X11 Layout: gb
2013-11-18localed: use _cleanup_Zbigniew Jędrzejewski-Szmek
2013-11-18Remove duplicate includesKarel Zak
2013-11-18use #pragma once instead of foo*foo define guardsShawn Landden
2013-11-18remove unused variablesThomas Hindoe Paaboel Andersen
2013-11-18bus: TIMESTAMP is optional kdbus metadata now, NAMES are always addedKay Sievers
2013-11-17core/socket: fix SO_REUSEPORTShawn Landden
2013-11-17core/socket: use _cleanup_free_Shawn Landden
2013-11-17networkd: make all calls asyncTom Gundersen
2013-11-17networkd: store netmask and mac address explicitlyTom Gundersen
2013-11-17bus: CREDS and NAMES are optional kdbus metadata nowKay Sievers
2013-11-17catalog: add French translationSylvain Plantefeve
2013-11-16tmpfiles: adjust excludes for the new per-service private dirsZbigniew Jędrzejewski-Szmek
In d8c9d3a (systemd: use unit name in PrivateTmp directories) I forgot to update the tmpfiles config.
2013-11-16Fix RemainAfterExit services keeping a hold on consoleOlivier Brunel
When a service exits succesfully and has RemainAfterExit set, its hold on the console (in m->n_on_console) wasn't released since the unit state didn't change.
2013-11-16po: add French translationSylvain Plantefeve
2013-11-15bash-completion: journalctl --fileZbigniew Jędrzejewski-Szmek
2013-11-15random-seed: improve debugging messages a bitZbigniew Jędrzejewski-Szmek
2013-11-15fstab-generator: use RequiresOverridable for fsck unitsZbigniew Jędrzejewski-Szmek
This allows the user to disable fsck's by masking. If fsck fails, emergency target is started, the user might mount the unit using mount and disable fsck by masking the unit. In this case, .mount will be active because the mount is detect through /proc/self/mountinfo, but systemd-fsck@.service will still be in failed mode. This results in a funny situation where $ systemctl show -p ActiveState local-fs.target yyy.mount ActiveState=active ActiveState=active $ sudo systemctl start local-fs.target [sudo] password for test: Failed to start local-fs.target: Unit systemd-fsck@xxx.service is masked.
2013-11-15core: some more _cleanup_free_Zbigniew Jędrzejewski-Szmek
2013-11-15fsck,fstab-generator: be lenient about missing fsck.<type>Zbigniew Jędrzejewski-Szmek
If fstab contains 1 for passno, treat this as an error, but only warn briefly. If fstab doesn't contain this information, don't complain at all. Patch is complicated a bit by the fact that we might have the fstype specified in fstab or on /proc/cmdline, in which case we can check if we have the appropriate fsck tool, or not specified, or specified as auto, in which case we have to look and check the type of the filesystem ourselves. It cannot be done before the device appears, so it is too early in the generator phase, and it must be done directly in fsck service.
2013-11-15fsck: modernizationZbigniew Jędrzejewski-Szmek
2013-11-15ycm_extra_conf: include src/systemd for headersDave Reisner
2013-11-15build: use printf to generate symbol testsDave Reisner
echo is basically unportable, so use printf instead.
2013-11-15build-sys: don't mix dynamic and static libsTom Gundersen
2013-11-14rtnl: add event loop integrationTom Gundersen
2013-11-14bus: typoTom Gundersen
Fix a couple of 'void' that should have been 'sd_bus'.
2013-11-14loopback-setup: move to rtnlTom Gundersen
This should be equivalent to the old behavior.
2013-11-14rtnl: add call_async and call_async_cancelTom Gundersen
They work in the same way as the sd-bus equivalents.
2013-11-14Update TODOZbigniew Jędrzejewski-Szmek
2013-11-13Fix possible lack of status messages on shutdown/rebootOlivier Brunel
Since 31a7eb86 the output on console can be disabled to avoid colliding with gettys. However, it could also lead to a lack of messages during shutdown/reboot.
2013-11-13Only disable output on console during boot if neededOlivier Brunel
If there are no more jobs on console, no need/we shouldn't disable output.
2013-11-13Resolve /dev/console to the active tty instead of just "tty0"Olivier Brunel
When resolving /dev/console one would often get "tty0" meaning the active VT. Resolving to the actual tty (e.g. "tty1") will notably help on boot when determining whether or not PID1 can output to the console.
2013-11-13zsh-completion: add bootctlMarko Myllynen
2013-11-13man: add bootctl(8)Marko Myllynen
https://bugzilla.redhat.com/show_bug.cgi?id=1014303
generated by cgit v1.2.3-54-g00ecf (git 2.45.2) at 2024-11-19 00:45:21 +0000