SymbX/systemd

T

Lennart Poettering aea529e5b2 core: don't dispatch load queue when setting Slice= for transient units

Let's be more careful when setting up the Slice= property of transient units:
let's use manager_load_unit_prepare() instead of manager_load_unit(), so that
the load queue isn't dispatched right away, because our own transient unit is
in it, and we don#t want to have it loaded until we finished initializing it.

2016-04-22 17:30:08 +02:00

.github/ISSUE_TEMPLATE: Use a list for submission type so that it appears as a checkbox

2016-02-26 09:54:30 +11:00

editors: only extend line width to 119 for C and XML files

2016-02-10 12:29:32 +01:00

tree-wide: remove useless NULLs from strjoina

2016-04-13 08:56:44 -04:00

docs: add .gitignore

2015-07-06 17:47:38 +02:00

…

hwdb: add trust illuminated mouse gxt 152 (#3085 )

2016-04-21 16:27:56 -04:00

build-sys: Perform flag tests in context to existing flags

2016-02-06 14:57:46 +01:00

treewide: fix typos (#3092 )

2016-04-22 14:18:05 +02:00

network: turn on LLDP tx+rx for the default container network configuration

2016-02-21 20:58:59 +01:00

po/zh_CN: attempt to refresh zh_CN translation

2016-03-01 20:40:18 -07:00

Mark nbd as inactive until connected (#2422 )

2016-04-18 16:29:10 +02:00

shell-completion

zsh-completion: remove non-portable uses of \s in awk (#3063 )

2016-04-19 00:23:01 -04:00

core: don't dispatch load queue when setting Slice= for transient units

2016-04-22 17:30:08 +02:00

coredump: honour RLIMIT_CORE when saving/processing coredumps

2016-02-10 16:08:32 +01:00

…

remove bus-proxyd

2016-02-12 19:10:01 +01:00

tests: don't rely on the host's systemd-nspawn, don't register test machine (#3023 )

2016-04-13 09:57:06 -04:00

build-sys: allow references to wheel group to be omitted

2016-02-17 23:47:23 -05:00

Remove systemd-bootchart

2016-02-23 13:30:09 +01:00

tmp.mount.hm4: After swap.target (#3087 )

2016-04-22 14:21:30 +02:00

login: support user-bus on dbus1

2015-08-31 18:12:37 +02:00

.dir-locals.el

editors: only extend line width to 119 for C and XML files

2016-02-10 12:29:32 +01:00

.editorconfig

editors: only extend line width to 119 for C and XML files

2016-02-10 12:29:32 +01:00

.gitattributes

…

.gitignore

basic: remove rbtree code, it's unused

2016-04-12 13:43:32 +02:00

.mailmap

NEWS: add more stuff, and reorder things a bit

2015-11-13 13:59:50 +01:00

.travis.yml

remove gudev and gtk-doc

2015-06-03 00:22:53 +02:00

.vimrc

editors: only extend line width to 119 for C and XML files

2016-02-10 12:29:32 +01:00

.ycm_extra_conf.py

…

autogen.sh

build-sys: drop libsystemd-{id128,daemon,login,journal}.so compat libs

2016-02-13 11:57:14 +01:00

CODING_STYLE

update CODING_STYLE a bit

2016-04-12 13:43:31 +02:00

configure.ac

build-sys: add --without-kill-user-processes configure option

2016-04-21 00:21:32 -04:00

DISTRO_PORTING

build-sys: warn if people don't change the default NTP servers when building systemd

2015-07-11 14:24:29 -03:00

LICENSE.GPL2

…

LICENSE.LGPL2.1

…

Makefile-man.am

Merge pull request #2944 from keszybz/man-coredump-sysctl

2016-04-06 10:49:52 +02:00

Makefile.am

Merge pull request #3005 from keszybz/kill-user-proceses

2016-04-21 12:29:36 +02:00

NEWS

tree-wide: use mdash instead of a two minuses

2016-04-21 23:00:13 -04:00

README

README: document that we only support util-linux built with --enable-libmount-force-mountinfo

2016-04-12 13:43:33 +02:00

README.md

github: CONTRIBUTING.md moved, let's fix the link to it

2016-02-22 23:23:06 +01:00

TODO

tree-wide: use mdash instead of a two minuses

2016-04-21 23:00:13 -04:00

README.md

systemd - System and Service Manager

Details

General information about systemd can be found in the systemd Wiki.

Information about build requirements are provided in the README file.

Consult our NEWS file for information about what's new in the most recent systemd versions.

Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.

When preparing patches for systemd, please follow our Coding Style Guidelines.

If you are looking for support, please contact our mailing list or join our IRC channel.