From Fedora Project Wiki
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
* One effect of this is that users who had configured custom sets of services to start in runlevel 2 or 4 will need to configure a new custom target. Quickstart on creating a new target is here: https://fedoraproject.org/wiki/Shttps://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet#Runlevels.2Ftargets#Runlevels.2Ftargets Might want to ask Lennart if there's a systemd man page/documentation online that's better to point people to. | * One effect of this is that users who had configured custom sets of services to start in runlevel 2 or 4 will need to configure a new custom target. Quickstart on creating a new target is here: https://fedoraproject.org/wiki/Shttps://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet#Runlevels.2Ftargets#Runlevels.2Ftargets Might want to ask Lennart if there's a systemd man page/documentation online that's better to point people to. | ||
* The [[SysVinit to Systemd Cheatsheet]] has some useful equivalents for system administrators making the transition. | * The [[SysVinit to Systemd Cheatsheet]] has some useful equivalents for system administrators making the transition. | ||
== Wheel group and administrative users == | |||
Fedora 15 introduces the concept of an administrative group for users. Users who are in this group are able to: | |||
* sudo, using their password | |||
* authorize for various administrative tasks using PolicyKit with their own password | |||
* authorize for various administrative tools using usermod with their own password | |||
This is implemented via the 'wheel' group. Users can be added to the administrative group in the GNOME User Accounts panel, or in firstboot. | |||
== Bacula == | == Bacula == | ||
Revision as of 16:49, 5 April 2011
Beat is open
This beat is now ready to have Fedora 25 content added by the beat writer
This beat is now ready to have Fedora 25 content added by the beat writer
init system
The init system has been changed to systemd.
- One effect of this is that users who had configured custom sets of services to start in runlevel 2 or 4 will need to configure a new custom target. Quickstart on creating a new target is here: https://fedoraproject.org/wiki/Shttps://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet#Runlevels.2Ftargets#Runlevels.2Ftargets Might want to ask Lennart if there's a systemd man page/documentation online that's better to point people to.
- The SysVinit to Systemd Cheatsheet has some useful equivalents for system administrators making the transition.
Wheel group and administrative users
Fedora 15 introduces the concept of an administrative group for users. Users who are in this group are able to:
- sudo, using their password
- authorize for various administrative tasks using PolicyKit with their own password
- authorize for various administrative tools using usermod with their own password
This is implemented via the 'wheel' group. Users can be added to the administrative group in the GNOME User Accounts panel, or in firstboot.
Bacula
Bacula director and storage daemons are now running as bacula user by default. Director's log file has moved to /var/log/bacula directory.
Default user can be changed in /etc/sysconfig/bacula-* files.
When upgrading please make sure that bacula has permissions to access configuration files, log files and database.