Visit Our UNIX and Linux User Community


Top output to textfile not working in cronjob


 
Thread Tools Search this Thread
Operating Systems Linux Ubuntu Top output to textfile not working in cronjob
# 8  
Old 08-08-2013
Hi again,
I've no idea what actually made it work but i tried a ton of stuff including both of your suggestions so something obviously did the trick. I'm grateful for your assistance, and if i find out the specific reason why it now works i'll post it here for somebody else in the future.

Previous Thread | Next Thread
Test Your Knowledge in Computers #906
Difficulty: Easy
A Unix shell repeatedly prints a prompt, waits for a command line on stdin, and then carries out some action, as directed by the contents of the command line.
True or False?

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

PHP cronjob not working but manual working

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

2. UNIX for Dummies Questions & Answers

Top Command Output is not coming via Cronjob

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

3. Shell Programming and Scripting

Cronjob is NOT working

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

4. UNIX for Dummies Questions & Answers

Cronjob not working

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

5. Shell Programming and Scripting

Script to get required output from textfile

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

6. Shell Programming and Scripting

Regarding overwriting the textfile with output what we get!

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

7. Solaris

cronjob not working

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

8. Solaris

cronjob not working

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

9. UNIX for Advanced & Expert Users

cronjob not working

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

10. UNIX for Advanced & Expert Users

formatting textfile inside ksh script using awk not working

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
METCHE(8)						      System Manager's Manual							 METCHE(8)

NAME
metche - reducing root bus factor SYNOPSIS
metche [-h VSERVER] report (stable|testing|unstable)-YYYYMMDDHHMM metche [-h VSERVER] list metche [-h VSERVER] stabilize testing-YYYYMMDDHHMM DESCRIPTION
metche is a tool meant to ease collective system administration by monitoring changes in the system configuration. metche basic usage is to monitor changes in a directory, usually /etc; optionally, metche can also monitor: o one or more user maintained changelog files, o the state of Debian packages and versions. metche should be installed with a cronjob that regularly runs to automatically save the system state as needed. These states are saved in a way similar to the Debian development model: o unstable states are saved as soon as a change is detected. They are kept until a new testing state appears. o testing states is created from the last unstable state that has not been changed after a short amount of time (by default, one hour). Old unstable states are deleted afterwards. o stable states are created from the last testing state, either manually, or after a long amount of time (by default, 3 days). Old testing states are deleted afterwards. When a new testing state is saved, an email is sent to a configurable address, giving an overwiew of the differences with the previous testing. A notification is also sent when a new stable state is saved. metche's configuration is read from /etc/metche.conf. Various settings like changelog monitoring or time between system state switches are described there. OPTIONS
If -h VSERVER is specified, the VServer VSERVER is operated on instead of the host system. This, along with the VSNAMES option, allows one to monitor several VServers running on the system. One of the following commands must be specified on the command line: report When run with the report command, metche displays a report against the specified saved state, or if unspecified, against the latest testing state. This is useful when you have broken your system and want to know which changes have been made since a given, known working, system state. list When run with the list command, metche displays a list of all the saved states. stabilize When run with the stabilize command, metche turns a "testing state" into a "stable state". By default, it will use the last "test- ing state", but this can be overridden by giving a specific state as argument. cron This command should not be called manually, but used from a cronjob. When called, it can perform various operations like: saving "unstable", "testing" or "stable" states as needed and sending reports and notification if configured to do so. This command does not support the -h option. FILES
/etc/metche.conf contains metche configuration. When configured to monitor one changelog, CHANGELOG_FILE (default: /root/Changelog). When configured to monitor multiple changelogs, CHANGELOG_DIR/*/Changelog (default: /root/changelogs). System states are saved in BACKUP_DIR (default: /var/lib/metche). SECURITY
metche is able to use GnuPG to encrypt the email it sends, but does not by default; just enable the ENCRYPT_EMAIL configuration option, and make sure EMAIL_ADDRESS' public key is in root's keyring, trusted enough to be used blindly by metche. If EMAIL_ADDRESS is an email alias or mailing-list's address, you probably want to use the group option in /root/.gnupg/gpg.conf so that metche reports are encrypted for every person subscribed to this alias or mailing-list; for more information, see gpg(1). When DO_DETAILS is enabled and ENCRYPT_EMAIL is disabled, metche sends in clear text email the changes made to the watched directory... either make sure that the EXCLUDES configuration variable prevents it to send sensitive information, or triple check that secure connec- tions will be used end-to-end on the email path. If unsure, set EMAIL_ADDRESS configuration variable to a local mailbox. Please note that EMAIL_ADDRESS is not used for VServers: a VServer's report messages are sent to its root email address. metche stores, in BACKUP_DIR (default: /var/lib/metche), various backups of WATCHED_DIR. Make sure that this backup place is at least as secured as the source. BUGS
See metche's ticket system (https://labs.riseup.net/code/projects/metche/issues) for known bugs, missing features, and the development road-map. AUTHORS
metche and this manual page were written by the boum.org collective, and are now maintained by the metche developers collective <metche@lists.riseup.net>. metche user manual June 5, 2011 METCHE(8)

Featured Tech Videos