08-08-2013
Any output would go to /var/log/test.log, not /var/log/dummy.txt. Is that where you are checking?
Also, in this case errors, would to the job owner's email (usaually).
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I cannot seem to get this text file to format. Its as if the awk statement is being treated as a simple cat command.
I manned awk and it was very confusing. I viewed previous posts on this board and I got the same results as with the
the awk command statement shown here. Please help.
... (6 Replies)
Discussion started by: tekline
6 Replies
2. UNIX for Advanced & Expert Users
I created a file in /u01/oradata directory as cronjb.ksh which contains following script
30 12 * * * /export/home/oracle/u01/oradata/rman.ksh
'/export/home/oracle' is my root directory. I then moved cronjb.ksh file to my '/export/home/oracle' directory. i typed crontab cronjb.ksh. However my... (8 Replies)
Discussion started by: manna
8 Replies
3. Solaris
I am trying to schedule a job via cronjob. Not sure what the problem is. below is my script and the error.
45 10 * * * /u01/app/oracle/jpark/sched_exp_mis.sh
Error received.
Your "cron" job on tama
/u01/app/oracle/jpark/sched_exp_mis.sh
produced the following output:
... (19 Replies)
Discussion started by: mrx1350
19 Replies
4. Solaris
Hi All , I have a cron jobs
that is not working while put inside cron.
But on executing from manually, it works fine,
Pl anyone find if there is anything wrong in the script.
30 22 * * 1-5 cd /home/ab90737/introscope/util/bin; ./batchgenerateReport.pl ../config/reps.config >... (1 Reply)
Discussion started by: jegaraman
1 Replies
5. Shell Programming and Scripting
Hi freinds,
My problem is I have a script which is used for our office work...
in that with my userid i can append the LOGFILE with the output which i get while running the script..
for this i use the below command
output >> $LOGFILE
but with the same script my colleague is... (6 Replies)
Discussion started by: smarty86
6 Replies
6. Shell Programming and Scripting
Hi
Iam running below script on one text file.
usr/xpg4/bin/awk 'BEGIN {print "IP HOST_NAME SUB "}
/IP IS/ {IP=$3}
/local/ {HOST=$1}
/PPPoE/ {SUB=$3 ;print IP, HOST, SUB}
' /Scripts/sub_report_$FILE>/Scripts/sub_final_report_.txt
the output is coming as below
IPHOST_NAME SUB ... (16 Replies)
Discussion started by: surender reddy
16 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I am trying to run a script through crontab but it doesn't run. The script sends an email of the logfile created.When I reun through command line it works perfectly but doesn't send any email through cron. There are othe jobs in cron wich runs perfectly.
Please let me know if I am doing... (3 Replies)
Discussion started by: Rossdba
3 Replies
8. Shell Programming and Scripting
Hi;
Here is the output from crontab -l:
2,7,12,17,22,27,32,37,42,47,52,57 * * * * /var/tmp/gcsw/jmap_samples/jmap_script.sh > /var/tmp/gcsw/jmap_samples/histo_`date '+%Y%m%d%H%M'`.txtWhen I manually run the line: /var/tmp/gcsw/jmap_samples/jmap_script.sh >... (2 Replies)
Discussion started by: gc_sw
2 Replies
9. UNIX for Dummies Questions & Answers
Dear All,
I created a small script to get the CPU, GIS usage etc automatically. However when i run this script manually its working , but when i run through cronjob i am not getting any output.
Can anyone please help me on this. I am using SuseLinux.
Thank you in advance.
#!/bin/sh
{... (2 Replies)
Discussion started by: Nitin Kapoor
2 Replies
10. Shell Programming and Scripting
Hi,
Can anyone help me on my PHP cron not working, but when i do the manual it work.
# manual run working
/usr/local/bin/php /root/dev/test.php
# crontab not working
55 8 * * * /usr/local/bin/php /root/dev/test.php
Thank in advances
Regards,
FSPalero
Please use CODE tags as... (2 Replies)
Discussion started by: fspalero
2 Replies
WHO(1) BSD General Commands Manual WHO(1)
NAME
who -- display who is on the system
SYNOPSIS
who [-abHmqsTu] [am I] [file]
DESCRIPTION
The who utility displays information about currently logged in users. By default, this includes the login name, tty name, date and time of
login and remote hostname if not local.
The options are as follows:
-a Equivalent to -bTu, with the exception that output is not restricted to the time and date of the last system reboot.
-b Write the time and date of the last system reboot.
-H Write column headings above the output.
-m Show information about the terminal attached to standard input only.
-q ``Quick mode'': List the names and number of logged in users in columns. All other command line options are ignored.
-s Show the name, line and time fields only. This is the default.
-T Indicate whether each user is accepting messages. One of the following characters is written:
+ User is accepting messages.
- User is not accepting messages.
? An error occurred.
-u Show idle time for each user in hours and minutes as hh:mm, '.' if the user has been idle less than a minute, and ``old'' if the user
has been idle more than 24 hours.
am I Equivalent to -m.
By default, who gathers information from the file /var/run/utx.active. An alternate file may be specified which is usually /var/log/utx.log
(or /var/log/utx.log.[0-6] depending on site policy as utx.log can grow quite large and daily versions may or may not be kept around after
compression by ac(8)). The utx.log file contains a record of every login, logout, crash, shutdown and date change since utx.log was last
truncated or created.
If /var/log/utx.log is being used as the file, the user name may be empty or one of the special characters '|', '}' and '~'. Logouts produce
an output line without any user name. For more information on the special characters, see getutxent(3).
ENVIRONMENT
The COLUMNS, LANG, LC_ALL and LC_TIME environment variables affect the execution of who as described in environ(7).
FILES
/var/run/utx.active
/var/log/utx.log
/var/log/utx.log.[0-6]
EXIT STATUS
The who utility exits 0 on success, and >0 if an error occurs.
SEE ALSO
last(1), users(1), w(1), getutxent(3)
STANDARDS
The who utility conforms to IEEE Std 1003.1-2001 (``POSIX.1'').
HISTORY
A who command appeared in Version 1 AT&T UNIX.
BSD
February 11, 2012 BSD