1
0
mirror of https://github.com/systemd/systemd.git synced 2024-11-14 15:21:37 +03:00
systemd/.gitignore

278 lines
4.3 KiB
Plaintext
Raw Normal View History

*.a
*.cache
*.html
*.la
*.lo
*.log
*.o
*.plist
*.pyc
*.stamp
*.swp
*.trs
*~
.config.args
.deps/
.dirstamp
.libs/
2014-07-07 12:04:33 +04:00
/*.gcda
/*.gcno
/*.tar.bz2
/*.tar.gz
/*.tar.xz
/Makefile
/TAGS
/accelerometer
/ata_id
/bootctl
/build-aux
/busctl
/cdrom_id
/collect
/coredumpctl
/coverage/
/defined
/exported
/exported-*
/gtk-doc.make
/hostnamectl
/install-tree
/journalctl
/libsystemd-*.c
/libtool
/localectl
/loginctl
/machinectl
/mtd_probe
/networkctl
/scsi_id
/systemadm
/systemctl
/systemd
/systemd-ac-power
/systemd-activate
2013-02-14 02:51:12 +04:00
/systemd-analyze
/systemd-ask-password
/systemd-backlight
/systemd-binfmt
2013-01-08 03:49:39 +04:00
/systemd-bootchart
/systemd-bus-proxyd
/systemd-cat
/systemd-cgls
/systemd-cgroups-agent
/systemd-cgtop
/systemd-consoled
/systemd-coredump
/systemd-cryptsetup
/systemd-cryptsetup-generator
/systemd-dbus1-generator
/systemd-debug-generator
/systemd-delta
/systemd-detect-virt
/systemd-efi-boot-generator
/systemd-escape
/systemd-evcat
/systemd-firstboot
/systemd-fsck
/systemd-fstab-generator
/systemd-getty-generator
/systemd-gnome-ask-password-agent
/systemd-gpt-auto-generator
/systemd-hibernate-resume
/systemd-hibernate-resume-generator
/systemd-hostnamed
/systemd-hwdb
/systemd-import
/systemd-importd
/systemd-inhibit
/systemd-initctl
/systemd-journal-gatewayd
2014-03-26 02:05:52 +04:00
/systemd-journal-remote
/systemd-journal-upload
/systemd-journald
/systemd-kmsg-syslogd
/systemd-localed
/systemd-logind
/systemd-machine-id-commit
2014-06-19 18:13:36 +04:00
/systemd-machine-id-setup
/systemd-machined
/systemd-modeset
/systemd-modules-load
/systemd-networkd
2014-03-01 16:39:14 +04:00
/systemd-networkd-wait-online
/systemd-notify
/systemd-nspawn
/systemd-path
/systemd-quotacheck
/systemd-random-seed
/systemd-rc-local-generator
/systemd-remount-api-vfs
/systemd-remount-fs
/systemd-reply-password
2014-07-17 00:55:23 +04:00
/systemd-resolve-host
/systemd-resolved
/systemd-rfkill
/systemd-run
/systemd-shutdown
/systemd-shutdownd
/systemd-sleep
/systemd-socket-proxyd
/systemd-stdio-bridge
/systemd-subterm
/systemd-sysctl
/systemd-system-update-generator
sysusers: add minimal tool to reconstruct /etc/passwd and /etc/group from static files systemd-sysusers is a tool to reconstruct /etc/passwd and /etc/group from static definition files that take a lot of inspiration from tmpfiles snippets. These snippets should carry information about system users only. To make sure it is not misused for normal users these snippets only allow configuring UID and gecos field for each user, but do not allow configuration of the home directory or shell, which is necessary for real login users. The purpose of this tool is to enable state-less systems that can populate /etc with the minimal files necessary, solely from static data in /usr. systemd-sysuser is additive only, and will never override existing users. This tool will create these files directly, and not via some user database abtsraction layer. This is appropriate as this tool is supposed to run really early at boot, and is only useful for creating system users, and system users cannot be stored in remote databases anyway. The tool is also useful to be invoked from RPM scriptlets, instead of useradd. This allows moving from imperative user descriptions in RPM to declarative descriptions. The UID/GID for a user/group to be created can either be chosen dynamic, or fixed, or be read from the owner of a file in the file system, in order to support reconstructing the correct IDs for files that shall be owned by them. This also adds a minimal user definition file, that should be sufficient for most basic systems. Distributions are expected to patch these files and augment the contents, for example with fixed UIDs for the users where that's necessary.
2014-06-13 00:54:02 +04:00
/systemd-sysusers
/systemd-sysv-generator
/systemd-timedated
2014-04-28 16:45:42 +04:00
/systemd-timesyncd
/systemd-tmpfiles
/systemd-tty-ask-password-agent
/systemd-uaccess
/systemd-udevd
/systemd-update-done
/systemd-update-utmp
/systemd-user-sessions
/systemd-vconsole-setup
/tags
2014-02-22 02:21:26 +04:00
/test-architecture
2014-06-22 16:53:24 +04:00
/test-async
shared: add generic IPC barrier The "Barrier" object is a simple inter-process barrier implementation. It allows placing synchronization points and waiting for the other side to reach it. Additionally, it has an abortion-mechanism as second-layer synchronization to send abortion-events asynchronously to the other side. The API is usually used to synchronize processes during fork(). However, it can be extended to pass state through execve() so you could synchronize beyond execve(). Usually, it's used like this (error-handling replaced by assert() for simplicity): Barrier b; r = barrier_init(&b); assert_se(r >= 0); pid = fork(); assert_se(pid >= 0); if (pid == 0) { barrier_set_role(&b, BARRIER_CHILD); ...do child post-setup... if (CHILD_SETUP_FAILED) exit(1); ...child setup done... barrier_place(&b); if (!barrier_sync(&b)) { /* parent setup failed */ exit(1); } barrier_destroy(&b); /* redundant as execve() and exit() imply this */ /* parent & child setup successful */ execve(...); } barrier_set_role(&b, BARRIER_PARENT); ...do parent post-setup... if (PARENT_SETUP_FAILED) { barrier_abort(&b); /* send abortion event */ barrier_wait_abortion(&b); /* wait for child to abort (exit() implies abortion) */ barrier_destroy(&b); ...bail out... } ...parent setup done... barrier_place(&b); if (!barrier_sync(&b)) { ...child setup failed... ; barrier_destroy(&b); ...bail out... } barrier_destroy(&b); ...child setup successfull... This is the most basic API. Using barrier_place() to place barriers and barrier_sync() to perform a full synchronization between both processes. barrier_abort() places an abortion barrier which superceeds any other barriers, exit() (or barrier_destroy()) places an abortion-barrier that queues behind existing barriers (thus *not* replacing existing barriers unlike barrier_abort()). This example uses hard-synchronization with wait_abortion(), sync() and friends. These are all optional. Barriers are highly dynamic and can be used for one-way synchronization or even no synchronization at all (postponing it for later). The sync() call performs a full two-way synchronization. The API is documented and should be fairly self-explanatory. A test-suite shows some special semantics regarding abortion, wait_next() and exit(). Internally, barriers use two eventfds and a pipe. The pipe is used to detect exit()s of the remote side as eventfds do not allow that. The eventfds are used to place barriers, one for each side. Barriers itself are numbered, but the numbers are reused once both sides reached the same barrier, thus you cannot address barriers by the index. Moreover, the numbering is implicit and we only store a counter. This makes the implementation itself very lightweight, which is probably negligible considering that we need 3 FDs for a barrier.. Last but not least: This barrier implementation is quite heavy. It's definitely not meant for fast IPC synchronization. However, it's very easy to use. And given the *HUGE* overhead of fork(), the barrier-overhead should be negligible.
2014-07-10 17:25:47 +04:00
/test-barrier
/test-boot-timestamp
/test-btrfs
/test-bus-chat
2014-06-19 18:13:36 +04:00
/test-bus-cleanup
/test-bus-creds
/test-bus-error
/test-bus-gvariant
/test-bus-introspect
2013-04-12 02:26:12 +04:00
/test-bus-kernel
/test-bus-kernel-benchmark
/test-bus-kernel-bloom
/test-bus-marshal
/test-bus-match
/test-bus-objects
/test-bus-policy
2013-03-30 18:30:23 +04:00
/test-bus-server
/test-bus-signature
/test-bus-zero-copy
/test-calendarspec
/test-cap-list
/test-capability
/test-catalog
/test-cgroup
/test-cgroup-mask
/test-cgroup-util
2014-06-24 22:42:29 +04:00
/test-compress
/test-compress-benchmark
/test-condition
/test-conf-files
2014-10-30 00:28:50 +03:00
/test-copy
/test-coredump-vacuum
/test-daemon
/test-date
/test-device-nodes
2013-12-13 05:43:35 +04:00
/test-dhcp-client
/test-dhcp-option
2014-06-19 18:13:36 +04:00
/test-dhcp-server
2014-06-19 18:57:10 +04:00
/test-dhcp6-client
/test-dns-domain
/test-ellipsize
/test-engine
/test-env-replace
/test-event
/test-execute
2014-06-15 00:10:45 +04:00
/test-fdset
/test-fileio
/test-fstab-util
/test-fw-util
/test-hashmap
/test-hostname
/test-icmp6-rs
/test-id128
/test-inhibit
/test-install
/test-ipcrm
2014-04-28 16:45:42 +04:00
/test-ipv4ll
/test-job-type
/test-journal
/test-journal-enum
/test-journal-flush
/test-journal-init
/test-journal-interleaving
/test-journal-match
/test-journal-send
/test-journal-stream
/test-journal-syslog
/test-journal-verify
2014-12-16 00:26:56 +03:00
/test-json
/test-libsystemd-sym*
/test-libudev
/test-libudev-sym*
2013-06-26 15:43:16 +04:00
/test-list
2014-12-23 23:34:55 +03:00
/test-lldp
/test-local-addresses
/test-locale-util
/test-log
/test-login
/test-login-shared
/test-login-tables
/test-loopback
/test-machine-tables
/test-mmap-cache
2013-10-23 22:10:02 +04:00
/test-namespace
/test-network
/test-network-tables
/test-ns
/test-path
/test-path-lookup
2013-03-30 18:06:51 +04:00
/test-path-util
/test-pppoe
/test-prioq
/test-pty
/test-qcow2
/test-ratelimit
/test-replace-var
2014-06-19 18:13:36 +04:00
/test-resolve
/test-ring
/test-rtnl
2014-06-19 18:13:36 +04:00
/test-rtnl-manual
/test-sched-prio
2014-10-02 01:22:02 +04:00
/test-set
/test-sigbus
/test-sleep
2014-06-15 00:10:44 +04:00
/test-socket-util
2014-05-16 22:14:23 +04:00
/test-ssd
2013-02-09 04:39:44 +04:00
/test-strbuf
/test-strip-tab-ansi
/test-strv
/test-strxcpyx
/test-tables
/test-term-page
/test-term-parser
/test-time
/test-tmpfiles
/test-udev
/test-uid-range
/test-unaligned
/test-unifont
/test-unit-file
/test-unit-name
/test-utf8
/test-util
/test-verbs
/test-watchdog
/test-xml
/timedatectl
/udevadm
/undefined
/v4l_id
2010-02-03 16:21:48 +03:00
Makefile.in
__pycache__/
2010-02-03 16:21:48 +03:00
aclocal.m4
config.h
config.h.in
config.log
config.status
configure
stamp-*