Sponsored Content
Full Discussion: crontab-nmon not working
Operating Systems AIX crontab-nmon not working Post 302201715 by fara_aris on Tuesday 3rd of June 2008 02:23:05 AM
Old 06-03-2008
johnf,

nmon.log;
root@axappk01::/tmp/nmon> more nmon.log
sh: /tmp/nmon_aix53: not found.
root@axappk01::/tmp/nmon>

manual run;
root@axappk01::/> /tmp/nmon_aix53 -fT -s 300 -c 144
ksh: /tmp/nmon_aix53: not found.
root@axappk01::/> /tmp/nmon -fT -s 300 -c 144
ksh: /tmp/nmon: 0403-006 Execute permission denied.
root@axappk01::/> cd /tmp/nmon
root@axappk01::/tmp/nmon> ./nmon_aix53 -fT -s 300 -c 144
root@axappk01::/tmp/nmon> ps -ef | grep nmon
root 1667112 1671362 0 14:17:04 pts/6 0:00 grep nmon
root 852232 1 1 14:16:57 - 0:00 ./nmon_aix53 -fT -s 300 -c 144

permission;
root@axappk01::/> ls -lrt | grep tmp
drwxrwxrwt 77 bin bin 294912 Jun 03 14:19 tmp
root@axappk01::/>
root@axappk01::/> cd /tmp
root@axappk01::/tmp>
root@axappk01::/tmp> ls -lrt | grep nmon
drwxrwxrwx 2 root system 4096 Jun 03 14:16 nmon
root@axappk01::/tmp> cd nmon
root@axappk01::/tmp/nmon> ls -lrt | pg
total 40712
-rwxr-xr-x 1 root system 870 Jun 22 2005 nmon
-rw-r----- 1 root system 70430 Jun 22 2005 nmon_README_june2004.txt
-rwxr-xr-x 1 root system 182126 Jun 22 2005 nmon_aix53
-rwxr-xr-x 1 root system 173420 Jun 22 2005 nmon_aix52
-rwxr-xr-x 1 root system 150386 Jun 22 2005 nmon_aix51
-rw-r----- 1 root system 583680 Aug 02 2007 nmon10p_for_aix5.tar
-rw-r----- 1 root system 348977 Sep 05 2007 nmon10p_for_aix5.tar.Z
-rw-r--r-- 1 root system 39 Jun 03 07:30 nmon.log
-rw-r--r-- 1 root system 155415 Jun 03 14:17 axappk01_080603_1416.nmon
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

crontab not working right

I am having problems with a sparc5 solaris 7 box, when i try to edit cron, (crontab -e as root), it says $ crontab -e 0 and then nothing, if i enter anything it errors out but does accept q for quit. But doesn't bring up my editor of the cron file. How can I troubleshoot this? ... (3 Replies)
Discussion started by: kymberm
3 Replies

2. UNIX for Advanced & Expert Users

crontab not working

Dear all We have SunOS 5.10 Generic_127127-11 sun4u sparc SUNW,Sun-Fire-V250 i have scheduled cronjob but its not working Crontab details 15 15 * * * /d5/oratest/testdb/hotbackup_new.sh TEST247 15 15 * * * mkdir -p rajesh /d4/appltest Crontab log details > CMD: mkdir... (4 Replies)
Discussion started by: rajesh_hv
4 Replies

3. UNIX for Dummies Questions & Answers

crontab not working

In /oracle folder, I created a file called "script.ksh" using vi command. The content of script.ksh is * * * * * echo "welcome">/tmp/capture.log I want the word "welcome" to be displayed in /tmp/capture.log file every minute. I have created capture.log under /tmp folder. Then in... (2 Replies)
Discussion started by: lg123
2 Replies

4. Solaris

crontab is not working.

I have a script which name is sicaklik.sh It is in the root directory. I can run manually but I want to run automatically every 3 minutes but it is not working. WHY? #whoami root #crontab -l #ident "@(#)root 1.21 04/03/23 SMI" 3 * * * * sh ./sicaklik.sh #ls -l sicaklik*... (6 Replies)
Discussion started by: getrue
6 Replies

5. UNIX for Dummies Questions & Answers

crontab not working

Hi, I had setup crontab to execute my script every day midnight 00:00 Below are the current settings. crontab -l 0 0 * * * /apps/bin/compress.ksh_moht > /dev/null 2>&1 Should it not work? I need help fix this? (8 Replies)
Discussion started by: shifahim
8 Replies

6. Red Hat

crontab is not working!!

I can run manually script of ntopdump.sh but crontab can't run this script very five minutes. # crontab -l */3 * * * * root sh /root/ping.sh */5 * * * * root sh /root/ntopdump.sh # # pwd /root # ls -l total 88 -rwxrwxr-x 1 root root 1645 Jun 14 19:01 anaconda-ks.cfg drwxrwxr-x 2 root... (14 Replies)
Discussion started by: getrue
14 Replies

7. Solaris

crontab not working

Shell = ksh Hi all, I scheduled an automated job on my application server like below, 30 13 * * 1-5 $HOME/my_script.sh However the script was not executed as expected. Any reason that may cause this to happen? (6 Replies)
Discussion started by: isaacniu
6 Replies

8. UNIX for Advanced & Expert Users

Crontab not working, please help

Hi, When I set the crontab to run every minute, every hour, it works fine. * * * * * env > /tmp/env.output However I want to run it every day at 8:00 AM and it does not run. * 8 * * * env > /tmp/env.output I ran the 'date' command which says it's 8AM PST and also the 'TZ'... (0 Replies)
Discussion started by: samantha13
0 Replies

9. Linux

Crontab not working

Hi, I know this is a common topic. I'm trying to launch a perl script using a contab -e entry. I've been trying diff options but nothing seems to work: My cron is running: UID PID PPID C STIME TTY TIME CMD root 3755 1 0 Nov27 ? 00:00:00 crond This... (4 Replies)
Discussion started by: krebe
4 Replies

10. Shell Programming and Scripting

Crontab not working

Hi All, I have a script with deatils as : $ ls -ld catch_logs.sh -rwx--x--x 1 muser muser 752 Jun 5 22:36 catch_logs.sh User crontab looks likes: $ crontab -l SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin * * * * * /opt/scripts/catch_logs.sh Now if I run this script... (7 Replies)
Discussion started by: Junaid Subhani
7 Replies
GZEXE(1)						      General Commands Manual							  GZEXE(1)

NAME
gzexe - compress executable files in place SYNOPSIS
gzexe name ... DESCRIPTION
The gzexe utility allows you to compress executables in place and have them automatically uncompress and execute when you run them (at a penalty in performance). For example if you execute ``gzexe /usr/bin/gdb'' it will create the following two files: -rwxr-xr-x 1 root root 1026675 Jun 7 13:53 /usr/bin/gdb -rwxr-xr-x 1 root root 2304524 May 30 13:02 /usr/bin/gdb~ /usr/bin/gdb~ is the original file and /usr/bin/gdb is the self-uncompressing executable file. You can remove /usr/bin/gdb~ once you are sure that /usr/bin/gdb works properly. This utility is most useful on systems with very small disks. OPTIONS
-d Decompress the given executables instead of compressing them. SEE ALSO
gzip(1), znew(1), zmore(1), zcmp(1), zforce(1) CAVEATS
The compressed executable is a shell script. This may create some security holes. In particular, the compressed executable relies on the PATH environment variable to find gzip and some standard utilities (basename, chmod, ln, mkdir, mktemp, rm, sleep, and tail). BUGS
gzexe attempts to retain the original file attributes on the compressed executable, but you may have to fix them manually in some cases, using chmod or chown. GZEXE(1)
All times are GMT -4. The time now is 07:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy