Sponsored Content
Operating Systems Solaris "! bad user (root)" in cron log Post 302456129 by mikejordan on Thursday 23rd of September 2010 09:31:29 AM
Old 09-23-2010
I have 2 quick suggestions:
First, Was the cron daemon running? Do a ps -ef|grep. Of course if it is running now, maybe it wasn't running then.
Second, I've never seen that error, but I noticed the "rc=1". Was the system in single user mode? Just wondered.
 

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
TH-CMD(1)							Triggerhappy daemon							 TH-CMD(1)

NAME
th-cmd -- triggerhappy commander SYNOPSIS
th-cmd --socket <socket> [--passfd] [--tag <foo>] [--clear|--enable|--disable|--mode <mode>|--quit|--udev|--add <devices...>|--remove <devices...>] DESCRIPTION
This program is used to issue commands to a running triggerhappy daemon. It utilizes an unix domain socket bound by the daemon. OPTIONS
--socket socket The socket file opened by the running triggerhappy daemon instance. --add <devices...> Instruct the running daemon to open the input devices specified on the command line --remove <devices...> Remove specified devices from the running daemon. --clear Remove all devices from the running daemon. --udev Deduce operation and device name from udev environment (for use in udev rules). --disable Disable the execution of triggers. --enable Re-enable the execution of triggers. --mode <newmode> Change the mode of the triggerhappy daemon to <newmode>. If no new mode is specified, the daemon switches to default mode. --quit Terminate the triggerhappy daemon. --passfd Instead of instructing the daemon to open the device, open the device and pass the file descriptor to the daemon. This allows the adding of new devices to a daemon having dropped its privileges, however the th-cmd process must have access to the device file. --grab Grab the device; the triggerhappy daemon will try to get exclusive access to the device, other applications will not receive the events emitted by it. --tag foo Label the added device with the tag <foo>; this can be used to limit the scope of event handlers to a subset of input devices. AUTHOR
Stefan Tomanek <stefan.tomanek+th@wertarbyte.de> 0.3.4 2011-05-10 TH-CMD(1)
All times are GMT -4. The time now is 07:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy