![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
oio11Исправление ошибки “user is not in the sudoers file. This incident will be reported” в Ubuntu
По умолчанию в Ubuntu, первая учетная запись которую вы создали в процессе установки, имеет права администратора системы. С помощью этой учетной записью, вы можете выполнять административные задачи с использованием команды “sudo”. Команда “sudo” относится к группе Super User (Супер пользователей), все пользователи в этой группе имеют права администратора для управления системой. Однако, если вы случайно удалили себя из “sudo” группы, вы не сможете ничего сделать. Вместо этого, единственное, что вы увидите, это сообщение: “user is not in the sudoers file. This incident will be reported”
1. Перезагрузите компьютер. Если Ubuntu является вашей основной и единственной операционной системой, то при загрузке системы нажмите кнопку “Shift”. На вашем мониторе должен появиться загрузчик Grub. Выберите режим восстановления и нажмите Enter.
2. В следующем диалоговом сообщении выберите “Check all file system (will exit read only mode)” (“Проверить все файловые системы ( режим только для чтения)”).
Когда увидите сообщение “Finished, press Enter”, нажмите Enter.
3. Затем выберите “Drop to root shell prompt”.
4. Запуститься командная строка. Введите:
usermod -a -G admin usernameЗамените имя пользователя “username” на ваше имя пользователя.
5. Вот и все. Теперь введите “exit” и перезагрузите систему.
В случае если вы испортили файл /etc/sudoers, выполните следующие действия:
Выше описанные шаги предполагают, что ваш etc/sudoers файл не изменялся и не поврежден. Если у вас неправильный файл /etc/sudoers. Вот что вам нужно сделать:
1. Выполните вышеупомянутые первые 3-и шага.
2. В командной строке введите:sudo cp /etc/sudoers /etc/sudoers.backup sudo nano /etc/sudoersВведите следующие строки в файл
# # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of # directly modifying this file. # # See the man page for details on how to write a sudoers file. # Defaults env_reset # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification root ALL=(ALL:ALL) ALL # Members of the admin group may gain root privileges %admin ALL=(ALL) ALL # Allow members of group sudo to execute any command %sudo ALL=(ALL:ALL) ALL #includedir /etc/sudoers.d
Нажмите “Ctrl + O”, чтобы сохранить файл и “Ctrl + X”, чтобы выйти.
3. Далее, установите права для файла sudoers:
chmod 440 /etc/sudoers4. Наконец, добавьте себя в Sudo группу:
usermod -a -G admin username5. Перезагрузите систему.
Теперь вы сможете выполнять задачи в режиме “sudo”.http://osmaster.org.ua/?p=3258
usermod - modify a user account
Synopsis
usermod [options] LOGINDescription
The usermod command modifies the system account files to reflect the changes that are specified on the command line.Options
The options which apply to the usermod command are:-a, --append
- Add the user to the supplementary group(s). Use only with the -G option.
- -c, --comment COMMENT
- The new value of the user's password file comment field. It is normally modified using the chfn(1) utility.
- -d, --home HOME_DIR
- The user's new login directory. If the -m option is given, the contents of the current home directory will be moved to the new home directory, which is created if it does not already exist.
- -e, --expiredate EXPIRE_DATE
- The date on which the user account will be disabled. The date is specified in the format YYYY-MM-DD.
- -f, --inactive INACTIVE
- The number of days after a password expires until the account is permanently disabled. A value of 0 disables the account as soon as the password has expired, and a value of -1 disables the feature.
- -g, --gid GROUP
- The group name or number of the user's new initial login group. The group must exist.
- -G, --groups GROUP1[,GROUP2,...[,GROUPN]]]
- A list of supplementary groups which the user is also a member of. Each group is separated from the next by a comma, with no intervening whitespace. The groups are subject to the same restrictions as the group given with the -g option. If the user is currently a member of a group which is not listed, the user will be removed from the group. This behaviour can be changed via the -a option, which appends the user to the current supplementary group list.
- -l, --login NEW_LOGIN
- The name of the user will be changed from LOGIN to NEW_LOGIN. Nothing else is changed. In particular, the user's home directory name should probably be changed manually to reflect the new login name.
- -L, --lock
- Lock a user's password. This puts a '!' in front of the encrypted password, effectively disabling the password. You can't use this option with -p or -U. Note: if you wish to lock the account (not only access with a password), you should also set the EXPIRE_DATE to 1.
- -m, --move-home
- Move the content of the user's home directory to the new location. This option is only valid in combination with the -d (or --home) option.
- -o, --non-unique
- When used with the -u option, this option allows to change the user ID to a non-unique value.
- -p, --password PASSWORD
- The encrypted password, as returned by crypt(3). Note: This option is not recommended because the password (or encrypted password) will be visible by users listing the processes.
You should make sure the password respects the system's password policy. - -s, --shell SHELL
- The name of the user's new login shell. Setting this field to blank causes the system to select the default login shell.
- -u, --uid UID
- The new numerical value of the user's ID. This value must be unique, unless the -o option is used. The value must be non-negative. Values between 0 and 999 are typically reserved for system accounts.
The user's mailbox, and any files which the user owns and which are located in the user's home directory will have the file user ID changed automatically.
The ownership of files outside of the user's home directory must be fixed manually. - -U, --unlock
- Unlock a user's password. This removes the '!' in front of the encrypted password. You can't use this option with -p or -L. Note: if you wish to unlock the account (not only access with a password), you should also set the EXPIRE_DATE (for example to 99999, or to the EXPIRE value from /etc/default/useradd).
- -Z, --selinux-user SEUSER
- The SELinux user for the user's login. The default is to leave this field the blank, which causes the system to select the default SELinux user.
Caveats
You must make certain that the named user is not executing any processes when this command is being executed if the user's numerical user ID, the user's name, or the user's home directory is being changed. usermod checks this on Linux, but only check if the user is logged in according to utmp on other architectures.You must change the owner of any crontab files or at jobs manually.
You must make any changes involving NIS on the NIS server.
Configuration
The following configuration variables in /etc/login.defs change the behavior of this tool:MAIL_DIR (string)
- The mail spool directory. This is needed to manipulate the mailbox when its corresponding user account is modified or deleted. If not specified, a compile-time default is used.
- MAIL_FILE (string)
- Defines the location of the users mail spool files relatively to their home directory.
- The MAIL_DIR and MAIL_FILE variables are used by useradd, usermod, and userdel to create, move, or delete the user's mail spool. If MAIL_CHECK_ENAB is set to yes, they are also used to define the MAIL environment variable.
MAX_MEMBERS_PER_GROUP (number) - Maximum members per group entry. When the maximum is reached, a new group entry (line) is started in /etc/group (with the same name, same password, and same GID). The default value is 0, meaning that there are no limits in the number of members in a group.
This feature (split group) permits to limit the length of lines in the group file. This is useful to make sure that lines for NIS groups are not larger than 1024 characters.
If you need to enforce such limit, you can use 25.
Note: split groups may not be supported by all tools (even in the Shadow toolsuite). You should not use this variable unless you really need it.
Files
/etc/group- Group account information.
- /etc/gshadow
- Secure group account information.
- /etc/passwd
- User account information.
- /etc/shadow
- Secure user account information.
| Linux / Unix Command: usermod |
NAME
usermod - Modify a user account .....http://linux.about.com/od/commands/l/blcmdl8_usermod.htm
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2012-12-08 10:00 am (UTC)# # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of # directly modifying this file. # # See the man page for details on how to write a sudoers file. # Defaults env_reset # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification root ALL=(ALL:ALL) ALL # Members of the admin group may gain root privileges %admin ALL=(ALL) ALL # Allow members of group sudo to execute any command %sudo ALL=(ALL:ALL) ALL #includedir /etc/sudoers.d} - будет "каша" <pre> </pre>
http://sudouser.com/nastrojka-sudo-v-debian-gnulinux-i-ubuntu-linux.html
http://amichurin.appspot.com/sudo.html
no subject
Date: 2012-12-08 10:53 am (UTC)Только текст файла можно редактировать под правами рута, а как быть,если root отсутствует в файле sudoers?
no subject
Date: 2012-12-08 11:44 am (UTC)разумеется через консоль, под рутом запускать DE - признак дурного тона )
...под рутом запускать DE - признак дурного тона )...
Date: 2012-12-08 12:25 pm (UTC)root у меня потерял права, вот и пришлось
выкручиваться - консоль+XFCE
no subject
Date: 2012-12-08 01:08 pm (UTC)или в файле sudoers не было рута?
... (а такое бывает?) )...
Date: 2012-12-08 01:36 pm (UTC)no subject
Date: 2012-12-08 01:38 pm (UTC)