From Fedora Project Wiki

(Wheel group and administrative users)
(Administrator users: Mention the programs sysadmins might actually know about instead of "usermode")
Line 14: Line 14:
 
* sudo, using their password
 
* sudo, using their password
 
* authorize for various administrative tasks using PolicyKit with their own password
 
* authorize for various administrative tasks using PolicyKit with their own password
* authorize for various administrative tools using usermod with their own password
+
* authorize for various administrative tools using consolehelper/userhelper 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.
 
This is implemented via the 'wheel' group. Users can be added to the administrative group in the GNOME User Accounts panel, or in firstboot.

Revision as of 17:06, 5 April 2011

DocsProject Header docTeam1.png
Note.png
Beat is open
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.

Administrator users

Fedora 15 introduces the concept of an administrator group. 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 consolehelper/userhelper 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.