Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1222
  • Last Modified:

Delete files with 0 bytes

Hi,

I'm running a Datastage jobs that create 10 files.I have to write a shell script that will find all the files created at that time range ie as soon the script start running, and delete all the files with 0 bytes.

Your answer is highly appreciated.
Thanks
Srinivas
0
srpendyala
Asked:
srpendyala
  • 3
  • 2
  • 2
  • +2
1 Solution
 
jlevieCommented:
find /path-to/dir -type f -empty -exec rm {} \;

Should do it.
0
 
tfewsterCommented:
> ie as soon the script start running...

That sounds a bit risky - What if the job creates the file but doesn't write anything to it for a few seconds? The "delete" task might remove it in that time and you'd lose real data.

What is the problem with a few 0-byte files existing until the Datastage job completes? You could run jlevies command safely then.
0
 
TintinCommented:
The -empty option is not available on all versions of find.  A more portable way is

find /path-to/dir -type f -size 0 -exec rm {} \;

0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
jlevieCommented:
Quite true...
0
 
srpendyalaAuthor Commented:
Thanks for suggestions and answer."tfewster" you are right. appreciated.

I have one more problem when trying to delete files just by using rm   it prompts for -----644  mode ? (y/n) -----
My task is to find all empty files and remove them.So when I'm using following  script

find . -size 0|rm ---    I'm getting the message ---- Usage: rm [-Rfir] file ...

Pls help me in the script which find empty files and rm them.

Thanks in advance
srn
0
 
jlevieCommented:
The prompt is a result of the file protection mode (644, or rw-r--r--) and the user running the command isn't the owner of the files. Either run the rm command as the user that owns the files or as root.

"find . -size 0|rm" isn't the command that Tintin posted. Try exactly what's in his comment.
0
 
tfewsterCommented:
It looks like the files are owned by another userid and have permissions 644 - so your userid can't modify them.  However, if you have write permissions on the _directory_, you can delete the files - you'll just get the warning that they are read-only (to your id).

If you use the -f option to rm, you won't get the warning.

By the way, `rm` doesn't accept input from stdin, so you can't pipe filenames to it in the way you were trying; Use Tintins command, with the -f option, i.e.
find /path-to/dir -type f -size 0 -exec rm -f {} \;
0
 
TalmashCommented:
not one line but much saftier

foreach file (`find . -type f`)
if (-z $file) then
rm $file
endif
end

tal
0
 
TintinCommented:
Talmash.

Please explain how your script (BTW, needs a #!/bin/csh at the top) is "safer" .
0
 
TalmashCommented:
just no warnings ,

and I am using it for wipeout for the last 5 years .

I am sure there is SHORTER / NICE way to write it .
I just copy-paste what i know is working for me .

about files that are been used at the moment , I can't protect this .

tal
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now