Search Results

Since wc includes leading spaces in its output, try it without the quotes:
if [ $count -gt 1000 ]

This might help you
$ file=sample.csv

$ now=$(date +"%m_%d_%Y")

$ newfile="${file%.*}_$now.${file##*.}"

$ echo $newfile
sample_02_05_2014.csv

Remember that if you "name" portion of the filename contain full stops ., then you will have to adjust the suggestion from anbu23 to cater for that.

Perhaps:-mv "${file}"...

Which shell are you using? Has the command executed successfully?
Try running the script manually and check whether the value of $run is being incremented correctly.

If you face any issues, Try...

Exists where? IS it exist in the $HOME of the cron user?
As I said earlier please provide full path of the path (starts with "/").






You can't use absolute numbers as the variables name....

1. You must have spaces on both side of opening and closing square brackets.

if [ $run -eq 10 ]; then


2. Make sure 'samp.csv' exists, Probably it exists in your current directory. Provide...

-o pid is a format specifier for the ps command that prints only the PID's of the processes specfied by the -c switch (in this case "myscript.sh"). But this will print the default column header name...

kill $(ps -C "myscript.sh" -o pid=)

Why are you running the script in the first place, if you want to later find it's pid and kill it? This doesn't appear to be an efficient way of achieving your task. What exactly do you want to...

I would suggest using at instead of cron. Use a file to keep track of how many times the job has run. When the job is ready to exit, it can update the count of how many time it has run, and if it...

Jobs run by cron are not interactive; they don't have a connection to your keyboard.

This may not be an adequate request for cron. Your entry will start at 10 min past each full hour and this will continue for ever and a day.
Try running a loop ten times and have a sleep 600 in...

You could count each execution and store it in a file. Use this execution counter to decide whether to proceed or not:
if [ -f "/tmp/exec_counter_$(date +%Y%m%d)" ]
then
cnt=$( cat...

mv $file /data/home/abc/xyz/azher/backup/`echo $file|cut -d. -f1`_$now.csv

mv "${file}" /data/home/abc/xyz/azher/backup/"${file%.*}_$now.${file#*.}"

I am with Don here...

There is no way of knowing at any one point in time for any *.csv file that your last
split will always be 33. It surely must be the remainder.

There is the situation...

And, how do the command line arguments in ./a.sh 2 1000 5 relate to your original request to put 100 lines in one file and split the remaining lines in 1000 line chunks?

You never answered Scrutinizer's question: Is this homework?

What shell are you using?

PS How do the command line arguments in ./a.sh 2 1000 5 relate to your original request to put 100 lines...

Do you mean what are the command line arguments to split? Have a look at man split .

Hi, you cannot read and write to the same file at the same time like that.

Try something like:
{ n=0
while IFS= read -r line && [ $(( n+=1 )) -le 100 ]
do
printf "%s\n" "$line"
done...

For the remaining you can use split. Can you show us what you tried so far?

While we always encourage here to show the efforts and at least start trying something. This is the way to learn and also it will give us the feeling that we are not doing your work instead we are...

Show us your sample input and expected output.

Start with (always) looking at the man pages.

man head
man tail
man split

By your luck, all the three man pages are very small (single page), and you can understand them very easily.
Please...

There is a specific forum for 'emergency' or quick requests.

What have you tried?