Either add >/dev/null 2>&1 at the end of the lines calling /var/opt/getstat.sh in root's crontab:
or add the line exec >/dev/null 2>&1once in /var/opt/getstat.sh script before it spits its output.
hi i am nitin...
jus a new kid on the block... my query is...
does the concept of region invovle sharin of inodes wen the sticky it is set... eg... if two process share two text regions... wat actually happens
thank u (1 Reply)
Hi Guys,
I have this filesystem got big with inode:
/dev/hd4 3670016 183664 95% 63705 58% /var
I don't know why the system doesn't give alerts on this FS although it's 95% and why the inode is 58%.
Any comments will be highly appreciated.
Thanks,
itik (1 Reply)
Hi guys,
need your help on this since i dont know much about solaris.
the problem is i need to increase inodes space on /export/home/
root@BRF-DANCCM1 # /usr/ucb/df -i
Filesystem iused ifree %iused Mounted on
/dev/vx/dsk/bootdg/rootvol
53026 1162206 ... (7 Replies)
Hi,
I would like to is it possible to repair inode table in solaris without running fsck? I am facing this issue in root file system, because to run fsck I have to bring system in single user mode with booting cdrom media.
I facing strange issue in /var/adm/messages it is showing inode table... (12 Replies)
Environment: O.S Version HP-UX B.11.31 U ia64
What is the recommended Inode free nodes?
On our server Unix Sys Admin, have setup warning email alert when % of I-node usage is above or equal at 5%.
Sample Email:
---------------------------------------------------
Subject: WARNING:... (6 Replies)
Is there any way to create a file on Solaris 10 (ZFS preferably, but UFS would be helpful as well) with a specific inode number? I need to create a file with a large inode, greater than a 32bit integer.
I am trying to test a piece of software which may be incorrectly truncating large inodes down... (16 Replies)
In solaris, orphan process is put to sleep mode and does not consume any CPU resources. In Linux, orphan process is kept in running state consuming all CPU and Ram resources. Is it the case? Is there a difference on how these operating systems will handle orphan processes?
The route cause of... (10 Replies)
Discussion started by: Belure Pooja B
10 Replies
LEARN ABOUT REDHAT
crontab
CRONTAB(1) General Commands Manual CRONTAB(1)NAME
crontab - maintain crontab files for individual users (V3)
SYNOPSIS
crontab [ -u user ] file
crontab [ -u user ] { -l | -r | -e }
DESCRIPTION
Crontab is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user can have
their own crontab, and though these are files in /var, they are not intended to be edited directly.
If the allow file exists, then you must be listed therein in order to be allowed to use this command. If the allow file does not exist but
the deny file does exist, then you must not be listed in the deny file in order to use this command. If neither of these files exists,
then depending on site-dependent configuration parameters, only the super user will be allowed to use this command, or all users will be
able to use this command.
If the -u option is given, it specifies the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines
"your" crontab, i.e., the crontab of the person executing the command. Note that su(8) can confuse crontab and that if you are running
inside of su(8) you should always use the -u option for safety's sake.
The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename ``-'' is
given.
The -l option causes the current crontab to be displayed on standard output.
The -r option causes the current crontab to be removed.
The -e option is used to edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit
from the editor, the modified crontab will be installed automatically.
SEE ALSO crontab(5), cron(8)FILES
/etc/cron.allow
/etc/cron.deny
STANDARDS
The crontab command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax differs from previous versions of Vixie Cron, as
well as from the classic SVR3 syntax.
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
AUTHOR
Paul Vixie <paul@vix.com>
4th Berkeley Distribution 29 December 1993 CRONTAB(1)