Sponsored Content
Operating Systems Solaris "! bad user (root)" in cron log Post 302456171 by res0nat0r on Thursday 23rd of September 2010 10:53:36 AM
Old 09-23-2010
Every time this has happened to me at my work place, it is because the account in question has been either locked or the account is aged. This shouldn't be happening to root, but I'd check out the actual account setup to make sure that it is still proper.
 

9 More Discussions You Might Find Interesting

1. HP-UX

Creating a "semi" root user? Is it possible?

Hello All, I work as a system admin at a company of about 600 users on a HP-UX server. We have an IT department of about 15. My problem is that we give out the root password to the majority of them, they are phone support techs, as they need to get in to kill processes and setup users and... (4 Replies)
Discussion started by: Setan
4 Replies

2. Solaris

sendmail "root... User address required." error

I'm running sendmail (8.13.8+Sun/8.13.8/Submit) solaris 10. When I send mail to root at the command line (whether I use a full-qualified address or just root), I get the error message root... User address required. Sending mail to root (either at the command line or in a cron job),... (10 Replies)
Discussion started by: csgonan
10 Replies

3. UNIX for Dummies Questions & Answers

Possible to give non root user sudo to "crontab -l"

Does anyone know if this is possible? I want to give some users access to root's crontab but only with a read privilege. Is this possible to do or can only root or people with full root sudo view root's cron? (4 Replies)
Discussion started by: LordJezoX
4 Replies

4. Shell Programming and Scripting

read -p "prompt text" foo say "read: bad option(s)" in Bourne-Shell

Hallo, i need a Prompting read in my script: read -p "Enter your command: " command But i always get this Error: -p: is not an identifier When I run these in c-shell i get this error /usr/bin/read: read: bad option(s) How can I use a Prompt in the read command? (9 Replies)
Discussion started by: wiseguy
9 Replies

5. Red Hat

error"warning: user owen does not exist - using root"?

I am trying to install openmotif22-2.2.3-18.src.rpm, after I typed in " rpm -i openmotif22-2.2.3-18.src.rpm" the following message comes out: warning: user owen does not exist - using root warning: group owen does not exist - using root I am install openmotif under root account. Do... (2 Replies)
Discussion started by: fishwater00
2 Replies

6. Red Hat

/var/log/messages error "kernel: RPC: bad TCP reclen"

Hi, I am seeing the following errors in my environment, not sure why is it happening, any ideas? Thanks. kernel: RPC: bad TCP reclen 0x73746174 (non-terminal ) Dec 17 02:14:48 kernel: RPC: bad TCP reclen 0x63480000 (large) Dec 17 02:14:48 kernel: RPC: bad TCP reclen 0x633f0000 (large) Dec... (5 Replies)
Discussion started by: amarlinux
5 Replies

7. AIX

Change "root" to "root.admin" in outgoing e-mails

Our AIX servers send e-mails which have the "from" address set to "root@company.com" for our root user ("C{M}company.com" in /etc/sendmail.cf). The problem is that when bad e-mails are sent out or rejected by remote servers, they are being returned and delivered to e-mail box of "Mary Root". ... (2 Replies)
Discussion started by: kah00na
2 Replies

8. Shell Programming and Scripting

Root running a script calling to scp using user "xyz" is not authenticating!

Close duplicate thread. (0 Replies)
Discussion started by: denissi
0 Replies

9. UNIX for Beginners Questions & Answers

How to run root level command , if user has "su -" permission in sudoers provided?

I am looking t run root level command on multiple servers, but all servers have only "su - " permission available in sudoers. please help me if any way that I can run command using help of "su -" My script for hosts in `cat hosts.txt`; do echo "###########################Server Name-... (5 Replies)
Discussion started by: yash_message
5 Replies
pam_sm_acct_mgmt(3)					     Library Functions Manual					       pam_sm_acct_mgmt(3)

NAME
pam_sm_acct_mgmt() - service provider implementation for pam_acct_mgmt SYNOPSIS
[flag]... file... [library]... DESCRIPTION
In response to a call to pam_acct_mgmt(3), the PAM framework calls from the modules listed in the pam.conf(4) file. The account management provider supplies the back-end functionality for this interface function. The applications should not call this API directly. The function, determines whether the current user's account and password are valid. This includes checking for password and account expi- ration, valid log-in times, etc. The user in question is specified by a prior call to and is referenced by the authentication handle, pamh, which is passed as the first argument to The following flags may be set in the flags field: The account management service should not generate any messages. The account management service should return if the user has a null authentication token. The argc argument represents the number of module options passed in from the configuration file pam.conf(4). argv specifies the module options, which are interpreted and processed by the account management service. Please refer to the specific module man pages for the var- ious available options. If an unknown option is passed to the module, an error should be logged through syslog(3C) and the option ignored. If an account management module determines that the user password has aged or expired, it should save this information as state in the authentication handle, pamh, using uses this information to determine which passwords have expired. APPLICATION USAGE
Refer to pam(3) for information on thread-safety of PAM interfaces. RETURN VALUE
If there are no restrictions to logging in, is returned. The following error values may also be returned upon error: User not known to underlying authentication module. New authentication token required. User account has expired. User denied access to account at this time. Ignore underlying account module regardless of whether the control flag is or User account has been disabled (trusted mode only). Terminal has been disabled (trusted mode only). User is not authorized for terminal access (trusted mode only). Wrong time to login (trusted mode only). WARNINGS
HP-UX 11i Version 3 is the last release to support trusted systems functionality. SEE ALSO
pam(3), pam_acct_mgmt(3), syslog(3C), pam.conf(4). pam_sm_acct_mgmt(3)
All times are GMT -4. The time now is 07:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy