sorry for my questions about that below script but i have an error that i don't understand.
It seems that my find command is not working fine but for me the command is ok
Thanks for your help
Code:
=====================================
/usr/IBM/HTTPServer/apache_cache
/usr/IBM/HTTPServer/apache_cache/toto.txt
find: bad status-- –name
find: bad status-- ‘*’
find: bad status-- –mtime
find: bad status-- +1
find: bad status-- –exec
find: bad status-- rm
find: bad status-- {}
find: bad status-- ;
==========================================
Code:
#!/bin/sh
# About the script
#==============================================================================
# author : Vision IT Group
# version : 1.0
# date written : January 2014
# application : delete -mtime +1 files in the apache_cache
#==============================================================================
#
################################ PATH ###########################################
DATUM1="$(date +%y%m%d.%H%M%S)"
NAME="CacheIHS_Logs"
PATHCACHELOGS="/usr/IBM/HTTPServer/logs/"
LOG_FILE=$PATHCACHELOGS/$NAME.log
################################ CODE ###########################################
#echo "find files to delete in the cache"
#echo "---------------------------------"
find "/usr/IBM/HTTPServer/apache_cache" –name ‘*’ –mtime +1 –exec rm {} \;
#Define Logfilename
#------------------
echo "Clear done ..."$DATUM1 >> $LOG_FILE
echo "---------------------------------------" >> $LOG_FILE
Moderator's Comments:
Please use code tags next time for your code and data..
I need to write a script that can find a bad record (for example: there is date field colom but value provided in the file for this field is N/A) then script shoud searches this pattern and then insert the whole record into the bad file.
Example:
File1
Name designation dateOfJoining... (1 Reply)
I need to write a script that can find a bad record (for example: there is date field colom but value provided in the file for this field is N/A) then script shoud searches this pattern and then insert the whole record into the bad file.
Example:
File1
Name designation dateOfJoining... (2 Replies)
rshstatus=`rsh -n lilo /db/p2/oracle/names9208/restart_names.sh`
if $rshstatus <>0 then
errstatus=1
mailx -s "xirsol8dr" ordba@xxx.com >> $log_dr
else if errstatus=0
echo "status to xirsol8dr successful"
can anyone provide if this is t he correct way to do this or is there a better way? (1 Reply)
Hi
I am trying to connect to db2 database from Unix shell script (k shell)
I need to catch the status of connect whether it is succesful or not.
----------------------------------------------------------
# Read login credentials for db2
tput clear
echo "Please enter your Userid:\c"... (3 Replies)
Hi,
I'm getting this message from my 64bit Redhat 5.5 NFSv3 clients. They are mounting an Oracle 7110 Array that is exporting the NFS shares.
nfs_stat_to_errno: bad nfs status return value: 88
As the 7110 is a Solaris/ZFS array I've traced the errno 88 to be an "Illegal Byte Sequence" by... (2 Replies)
I am using blow script :--
#!/bin/bash
FIND=$(ps -elf | grep "snmp_trap.sh" | grep -v grep) #check snmp_trap.sh is running or not
if
then
# echo "process found"
exit 0;
else
echo "process not found"
exec /home/Ketan_r /snmp_trap.sh 2>&1 & disown -h ... (1 Reply)
Hi Folks,
Please help me ,I need a unix shell script to check for multiple jobs running. if there are multiple backup Jobs running then it should be trigger an email .
Thanks,
Anand T (1 Reply)
when I run the following command in AIX (bash),
find ./*
I get the following error.
find: bad status-- ./*
Thats becasuse, its an empty directory. The same works, when there the directory is not empty. Even though the find deesnt have to rerun any result.
My full find command would look... (4 Replies)
In a fastload teradata utility I am trying to delete the files which are older than 30days using the find and rm command as following.
find . -name 'xxx_*' -mtime +30 -exec rm -f {} \;
I expect it to delete all the files older than 30 days but sometimes it gives an error : find: bad status--... (3 Replies)
Discussion started by: stelkar
3 Replies
LEARN ABOUT OSF1
badsect
badsect(8) System Manager's Manual badsect(8)NAME
badsect - Creates files to contain bad sectors
SYNOPSIS
/usr/sbin/badsect bbdir sector...
DESCRIPTION
The badsect command makes a file to contain a bad sector. Normally, bad sectors are made inaccessible by the standard formatter, which
provides a forwarding table for bad sectors to the driver. If a driver supports the bad blocking standard, it is preferable to use that
method to isolate bad blocks because the bad block forwarding makes the disk appear perfect, and such disks can then be copied with dd(1).
The technique used by badsect is also less general than bad block forwarding, as badsect cannot make amends for bad blocks in the i-list of
file systems or in swap areas.
On some disks, adding a sector that is suddenly bad to the bad sector table currently requires the running of the standard formatter.
Thus, to deal with a newly bad block or on disks where the drivers do not support the bad-blocking standard, badsect can be used to good
effect.
Use the badsect command on a quiet file system in the following way: Mount the file system and change to its root directory. Make a direc-
tory BAD there. Run badsect, giving as argument the BAD directory followed by all the bad sectors you wish to add. (The sector numbers
must be relative to the beginning of the file system, as reported in console error messages.) Change back to the root directory, unmount
the file system, and run fsck(8) on the file system. The bad sectors should show up in two files or in the bad sector files and the free
list. Have fsck remove files containing the offending bad sectors, but do not have it remove the BAD/nnnnn files. This operation will
leave the bad sectors in only the BAD files.
The badsect command works by giving the specified sector numbers in a mknod(2) system call, creating an illegal file whose first block
address is the block containing bad sector and whose name is the bad sector number. When fsck discovers the file, it will ask "HOLD BAD
BLOCK?" An affirmative response will cause fsck to convert the inode to a regular file containing the bad block.
RESTRICTIONS
If more than one of the sectors comprised by a file system fragment are bad, you should specify only one to badsect, as the blocks in the
bad sector files cover all the sectors in a file system fragment.
ERRORS
The badsect command refuses to attach a block that resides in a critical area or is out of range of the file system. A warning is issued
if the block is already in use.
SEE ALSO
Commands: fsck(8)badsect(8)
01-31-2014
