system and session manager

Edit Package systemd

systemd is a system and session manager for Linux, compatible with SysV and LSB init scripts. systemd provides aggressive parallelization capabilities, uses socket and D-Bus activation for starting services, offers on-demand starting of daemons, keeps track of processes using Linux cgroups, supports snapshotting and restoring of the system state, maintains mount and automount points and implements an elaborate transactional dependency-based service control logic. It can work as a drop-in replacement for sysvinit.

Refresh
Refresh
Source Files
Filename Size Changed
after-local.service 0000000497 497 Bytes
baselibs.conf 0000000194 194 Bytes
fix-machines-subvol-for-rollbacks.sh 0000003080 3.01 KB
kbd-model-map.legacy 0000000891 891 Bytes
libgcrypt.m4 0000004727 4.62 KB
macros.systemd.upstream 0000002735 2.67 KB
nss-myhostname-config 0000000534 534 Bytes
pre_checkin.sh 0000000624 624 Bytes
systemd-228.tar.xz 0002866192 2.73 MB
systemd-mini-rpmlintrc 0000001711 1.67 KB
systemd-mini.changes 0000335213 327 KB
systemd-mini.spec 0000044581 43.5 KB
systemd-rpmlintrc 0000001711 1.67 KB
systemd-sysv-convert 0000004202 4.1 KB
systemd-sysv-install 0000000987 987 Bytes
systemd.changes 0000335213 327 KB
systemd.spec 0000044384 43.3 KB
udev-remount-tmpfs 0000000431 431 Bytes
Revision 959 (latest revision is 1514)
Thomas Blume's avatar Thomas Blume (tsaupe) accepted request 437403 from Franck Bui's avatar Franck Bui (fbui) (revision 959)
- Own a couple of directories even if they don't belong to systemd
  otherwise the build system will complain.
  Some directories (owned by others packages) are simply used by
  systemd to ship some scripts or config files to customize others
  *optional* components. Since thos components are not build required
  by systemd those directories are not owned by any packages and the
  BS complains...

- Import commit
  15ea716 journal-remote: change owner of /var/log/journal/remote and create /var/lib/systemd/journal-upload (bsc#1006372)
  

- %sysusers_create and %tmpfiles_create must be called in %post
  Calling %pre is broken since the respective conf files are not yet
  installed.

- %{_libexecdir}/{tmpfiles.d,sysusers.d}/systemd-remote.conf are
   part of systemd-journal-remote package (only).

- systemd-journal-{gatewayd,remote,upload} units are only part of
  "systemd-journal-remote" package.
  So exclude them from the main package.

- Import commit a1c145e6ad6588555dca64402f9103fb1e02b1a0
  7f34037 man: explain that *KeyIgnoreInhibited only apply to a subset of locks
  df5798b Revert "logind: really handle *KeyIgnoreInhibited options in logind.conf" (bsc#1001790 bsc#1005404)
  f79fee7 Revert "kbd-model-map: add more mappings offered by Yast"
  3760c10 manager: tighten incoming notification message checks
  d6efd71 core: only warn on short reads on signal fd
  6eebd91 manager: be stricter with incomining notifications, warn properly about too large ones
Comments 6

Anonymous User's avatar

This comment has been deleted


Franck Bui's avatar

Fix submitted. Thanks for the report, but please next time use BZ for this instead.


Bernd Wachter's avatar

I never managed to log in to the suse bugzilla (and just verified that I still can't get there). The account setup for suse infrastructure is a huge mess, usually I just fix issues or do my own workaround just so I don't have to deal with that. In this case preparing a proper fix would've been too much effort for me, so next best thing was leaving a comment and hoping someone notices, latest when other people start complaining that something is broken...


Илья Индиго's avatar

Thanks, I just caught this bug too today. Well at least it was updated NOT remotely, otherwise the server would be down.


Stefan Brüns's avatar

On Leap 15.1/SLE15SP1, suse-module-tools and systemd(-mini) are inconsistent, conflicting sg.conf.

Can someone either - enable build of systemd(-mini) on Leap 15.1/SLE15SP1 or - disable build of suse-module-tools and purge the binaries from the repo


Rarmi n's avatar

Systemd homed and oomd have been in use in other distros for quite some time. Either together in one package or separated like with OpenMandriva. I'd argue that they would be stable enough for everyone using openSUSE Tumbleweed. Perhaps they can soon be included in the base package. Or as separate packages for when people choose to install them.

I don't know if its considered stable yet for tumbleweed. this is just a suggestion.

openSUSE Build Service is sponsored by