LVM
volumes in both the graphical interface and automated kickstart
installations. This change includes a new automatic partitioning variant as well as new options to create thin volumes in custom partitioning.
setcifsacl
and getcifsacl
.
setcifsacl
, getcifsacl
, and other related SSSD packages.
Make backups!
virsh
, virt-manager and virt-install
. qemu has an ARM emulator that works well and is actively used in the Fedora ARM effort. However libvirt and virt-manager currently have issues launching qemu-system-arm VMs, mostly by encoding x86 assumptions in the generated command line that cause qemu-system-arm
to fail to start. Changes have been made to fix this issue. More information can be found at https://fedoraproject.org/wiki/Changes/Virt_ARM_on_x86
Unauthenticated
access is initially used for all connections. This state allows all API operations that are required to complete authentication. Following a successful authentication, two more levels can be assigned: Unrestricted
, which gives full access to all API operations, and Restricted
, which allows read only access.
Layer 2
isolated network for Openstack.
http://osrg.github.com/ryu/ |
https://github.com/osrg/ryu/wiki |
http://osrg.github.com/ryu/doc/index.html |
Fedora Big Data SIG
. Find this Special Interest Group
at https://fedoraproject.org/wiki/SIGs/bigdata, your gateway to using and participating in the effort.
journald
logging serves most use cases as well as, or better than, syslogd
.
/var/log/messages
for system logs should instead use journalctl
.
new journalctl | old messages |
---|---|
journalctl | less /var/log/messages |
journalctl -f | tail -f /var/log/messages |
journalctl --unit named.service | grep named /var/log/messages |
journalctl -b | Shows logs from current boot, no simple equivalent. |
scope
and slice
.
scope
units are automatically created by systemd out of existing processes. By grouping a process and its children together, a scope unit can be used to organize processes, apply resource units, or kill a group of processes. User sessions are one example of processes contained in a scope unit.
slice
units are used to group units that manage processes into a hierarchy that allows control of resources allocated to the slice. The default slices are machine.slice, for virtual machines and containers; system.slice, for system services; and user.slice, for user sessions. These default slices are automatically populated.
Instance units
, such as getty@.service
, are spawned on demand using the template defined in their configuration file. Each type of template is given a subslice of the system slice
, and instances are contained within that slice.
.
, the root slice. Each session is further confined in a scope unit within the user's slice.
systemctl status user.slice
Loaded: loaded (/usr/lib/systemd/system/user.slice; static)
Active: active since Sun 2013-09-08 01:23:40 MDT; 18h ago
Docs: man:systemd.special(7)
CGroup: /user.slice
├─user-1000.slice
│ ├─session-21.scope
│ │ ├─9226 sshd: pete [priv]
│ │ ├─9229 sshd: pete@pts/4
│ │ ├─9230 -bash
│ │ ├─9262 sudo su -
│ │ ├─9270 su -
│ │ ├─9271 -bash
│ │ └─9509 screen -R
│ ├─session-18.scope
│ │ ├─ 7939 sshd: pete [priv]
│ │ ├─ 7942 sshd: pete@pts/0
│ │ ├─ 7943 -bash
│ │ ├─ 7982 sudo su -
│ │ ├─ 7988 su -
│ │ ├─ 7989 -bash
│ │ ├─ 8206 SCREEN
│ │ ├─ 8207 /bin/bash
│ │ ├─ 8237 /bin/bash
│ │ ├─ 8486 less NEWS
│ │ ├─ 8489 /bin/bash
│ │ └─10637 systemctl status user.slice
## truncated ##
Slice=slicename
directive in their unit configuration file. Arguments allowing resource limitation within a slice or service unit are described in man systemd.directives
. See also man systemd.slice
and man systemd.cgroup
.
journalctl
can now be used to view the logs from a specific boot. For example, to view logs from the current boot:
journalctl -b
journalctl -b -1
journalctl -b 38fd9c3303574ed38e822233457f6b77
journalctl
can reference the contents of the journal by a record identifier known as a cursor
. Similar to a git hash, the cursor
uniquely identifies a point in the journal.
--show-cursor
to a journalctl query, the last line of output will contain the cursor value:
journalctl -b -u network --show-cursor --since 15:00
Sep 08 15:37:59 localhost.localdomain network[4074]: [FAILED]
Sep 08 15:37:59 localhost.localdomain systemd[1]: network.service: control process exited, code=exited status=1
Sep 08 15:37:59 localhost.localdomain systemd[1]: Failed to start LSB: Bring up/down networking.
Sep 08 15:37:59 localhost.localdomain systemd[1]: Unit network.service entered failed state.
-- cursor: s=13497722134642a2ac1544bada0c8836;i=1120d;b=8491c05dabd3444ca122e7069b5de0a9;m=db2118a46;t=4e5e7d81c7402;x=d177768ac95df831
journalctl -c "s=13497722134642a2ac1544bada0c8836;i=1120d;b=8491c05dabd3444ca122e7069b5de0a9;m=db2118a46;t=4e5e7d81c7402;x=d177768ac95df831"
journalctl --after-cursor "s=13497722134642a2ac1544bada0c8836;i=1120d;b=8491c05dabd3444ca122e7069b5de0a9;m=db2118a46;t=4e5e7d81c7402;x=d177768ac95df831"