summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2013-10-25bus: disable debug output in test-bus-kernel-benchmarkKay Sievers
2013-10-24catalog: remove links to non-existent wiki pagesZbigniew Jędrzejewski-Szmek
AFAIK, we don't have even one page with message explanations. If/when we add them, we can add links. https://bugzilla.redhat.com/show_bug.cgi?id=1017161
2013-10-22systemd: use unit name in PrivateTmp directoriesZbigniew Jędrzejewski-Szmek
Unit name is used whole in the directory name, so that the unit name can be easily extracted from it, e.g. "/tmp/systemd-abcd.service-DEDBIF1". https://bugzilla.redhat.com/show_bug.cgi?id=957439
2013-10-22inhibit: port to sd-busTom Gundersen
2013-10-22analyze: systemd-analyze.c -> analyze.cKay Sievers
2013-10-22bus: NULL signatures are OK tooLennart Poettering
2013-10-22bus: only if the user tries to read over the end of an array we should ↵Lennart Poettering
handle this as EOF
2013-10-22localed: port from libdbus to libsystemd-busKay Sievers
2013-10-21socket-proxyd: Fix-up from previous change to avoid looping on errors.David Strauss
2013-10-22bus: avoid 'bool' storage when retrieving 'b' from the messageKay Sievers
Just use an unsigned int as a bool type to avoid issues in the public message reading API; sizeof(bool) == 1, but the code copies 4 bytes at the pointers destination.
2013-10-21socket-proxyd: Use ONESHOT to behave properly with multiple accept() processes.David Strauss
2013-10-21man: avoid the use of sudo in examplesJan Engelhardt
sudo is not the first-class tool on all distros. Just require any superuser shell.
2013-10-21man: wording and grammar updatesJan Engelhardt
This is a recurring submission and includes corrections to various issue spotted.
2013-10-21sd-event: EPOLLONESHOT only disables event reporting after an event. The fd ↵David Strauss
is still registered.
2013-10-21shell-completion: dump has moved to systemd-analyzeZbigniew Jędrzejewski-Szmek
Rename NO_OPTION to STANDALONE for consistency with other files.
2013-10-21analyze: set white backgoundThomas Hindoe Paaboel Andersen
In programs like eog and gimp the transparant background did not look very good. https://bugs.freedesktop.org/show_bug.cgi?id=70720
2013-10-21build-sys: sync printed defaults with "c" optionKay Sievers
2013-10-21silent a few more gcc warningsKay Sievers
2013-10-21build-sys: disable _FORTIFY_SOURCE for -Og builds for nowKay Sievers
Older gcc versions throw things like: In file included from /usr/include/fcntl.h:302:0, from ../src/core/execute.c:25: In function 'open', inlined from 'open_null_as' at ../src/core/execute.c:196:12: /usr/include/bits/fcntl2.h:50:24: error: call to '__open_missing_mode' declared with attribute error: open with O_CREAT in second argument needs 3 arguments __open_missing_mode ();
2013-10-21build-sys: use -Og instead of -O0 to catch warningsKay Sievers
$ touch src/core/dbus.c; make CFLAGS=-O0 make --no-print-directory all-recursive Making all in . CC src/core/libsystemd_core_la-dbus.lo CCLD libsystemd-core.la $ touch src/core/dbus.c; make CFLAGS=-Og make --no-print-directory all-recursive Making all in . CC src/core/libsystemd_core_la-dbus.lo src/core/dbus.c: In function 'init_registered_system_bus': src/core/dbus.c:798:18: warning: 'id' may be used uninitialized in this function [-Wmaybe-uninitialized] dbus_free(id); ^ CCLD libsystemd-core.la -Og Optimize debugging experience. -Og enables optimizations that do not interfere with debugging. It should be the optimization level of choice for the standard edit-compile-debug cycle, offering a reasonable level of optimization while maintaining fast compilation and a good debugging experience.
2013-10-21rules: remove pointless MODE= settingsKay Sievers
Changing the default MODE= for the group accessi, but not specifying a GROUP= does not provide anything. It disables the default logic that the mode switches to 0660 as soon as a GROUP= is specifed, which make custom rules uneccesarily complicated. https://bugs.freedesktop.org/show_bug.cgi?id=70665
2013-10-20socket-proxyd(1): fix references to non-existant filesDave Reisner
socket.target -> sockets.target /usr/bin/systemd-socket-proxyd -> /usr/lib/systemd/systemd-socket-proxyd
2013-10-21bus: initialize variable, now that we might skip debug loggingKay Sievers
2013-10-21bus: remove static introspection file exportKay Sievers
2013-10-21bus: allow to specify NULL as an empty string to addKay Sievers
2013-10-20log: Fix previous commit to use correct levelColin Walters
2013-10-20log: avoid calling the logging functions for log levels above the current ↵Kay Sievers
maximum Messages with log levels above the current maximum log level will be dropped inside log_meta(). But to be able to call the function, all parameters for the function need to be provided. This can easily get expensive, if values need to be calculated or functions are used in parameters. Avoid all useless work by checking inside the macro, before we look at any parameters passed to the logging functions.
2013-10-20build-sys: unify foo_CFLAGS = usage and add explaining commentsKay Sievers
Always add the default AM_CFLAGS first. If variables are used in conditionals, the default assignment of AM variables is disabled, even when the conditional is not in use; foo_CFLAGS = $(AM_CFLAGS) is needed, even when it looks like a no-op.
2013-10-20Revert "build-sys: move journalctl CFLAGS= to one line"Colin Walters
This reverts commit e5d5aa1d0f4e143f12f5e00ca072547369d37e53; it breaks if !HAVE_QRENCODE since then we aren't using $(AM_CFLAGS) for journalctl.
2013-10-20vimrc: disable -fdiagnostics-color outputKay Sievers
2013-10-19socket-proxyd: Remove datagram research TODO. This proxy will not work with ↵David Strauss
them.
2013-10-19socket-proxyd: Comment and log text cleanup.David Strauss
* Standardize on "nonblocking" spelling, per Linux man pages. * Clarify that the nonblocking sockets are never in a "blocking" or "unblocked" state, just a "would block" or "ready" state.
2013-10-20man: systemd-fstab-generator - remove <term>Kay Sievers
Element term in namespace '' encountered in para, but no template matches.
2013-10-20hwdb: updateKay Sievers
2013-10-20socket-proxyd: initialize variable used in error code pathKay Sievers
2013-10-20build-sys: move journalctl CFLAGS= to one lineKay Sievers
2013-10-19trivial: rfkill - don't include util.h twiceTom Gundersen
2013-10-19trivial: rfkill: It's util.h, not utils.hColin Walters
How about we actually run make locally before pushing, eh?
2013-10-19man: fix typos in backlight/rfkill pageTom Gundersen
/me must learn to also test manpage changes
2013-10-19TODO: updateTom Gundersen
2013-10-19udev-builtin: uaccess - inherit logging form udevTom Gundersen
Not that it makes a difference in this builtin, but otherwise /etc/udev/udev.conf is not respected.
2013-10-19fsck-root: only run when requested in fstabTom Gundersen
fsck-root is redundant in case an initrd is used, or in case the rootfs is never remounted 'rw', so the new default is the correct behavior for most users. For the rest, they should enable it in fstab.
2013-10-19efi-boot-generator: hookup to fsckTom Gundersen
2013-10-19mount/service: drop FsckPassNo supportTom Gundersen
We now treat passno as boleans in the generators, and don't need this any more. fsck itself is able to sequentialize checks on the same local media, so in the common case the ordering is redundant. It is still possible to force an order by using .d fragments, in case that is desired.
2013-10-19Remove FsckPassNo from systemd-fsck-root.serviceThomas Bächler
2013-10-19gpt-auto-generator: Generate explicit dependencies on systemd-fsck@.service ↵Thomas Bächler
instead of using FsckPassNo [tomegun: check for OOM]
2013-10-19fstab-generator: Generate explicit dependencies on systemd-fsck@.service ↵Thomas Bächler
instead of using FsckPassNo [tomegun: * order all fsck instances after fsck-root * check for OOM * added notes in the manpages]
2013-10-19fstab-generator: When parsing the root= cmdline option, set FsckPassNo to 1Thomas Bächler
[tomegun: without this we would never fsck the rootfs if it was directly mounted 'rw' from the initrd. We now risk fsck'ing it twice in the case it is mounted 'ro', so that should be addressed in a separate patch.]
2013-10-19kerne-command-line: introduce option 'systemd.restore_state'Tom Gundersen
When set to 0 this will stop tools like the backlight and rfkill tools to restore state from previous boot. This is useful in case the stored state is bogus to the extent that it is preventing you from resetting it (e.g., the backlight settings cause the screen to be off on boot on a system where the backlight can not be adjusted directly from the keyboard).
2013-10-19TODO: add some fsck itemsTom Gundersen