Sponsored Content
Top Forums Shell Programming and Scripting Cut Command error cut: Bad range Post 302524124 by dgmm on Saturday 21st of May 2011 05:26:42 PM
Old 05-21-2011
Cut Command error cut: Bad range

Hi
Can anyone what I am doing wrong while using cut command.
Code:
for f in *.log
  do
    logfilename=$f
    Log "Log file Name: $logfilename"
    logfile1=`basename $logfilename .log`
    flength=${#logfile1}
    Log "file length $flength"
    from_length=$(($flength - 15))
    Log "from length $from_length"
    logfile_date=`echo $logfile1 | cut -c ${from_length}-8`
    Log "Logfile date with stringlength $logfile_date"
done

Getting error in cut command for a file as
INT_put_daily_stock_tax_to_ML_20110520_002258
I want use cut command.

The error is showing
Code:
+ + echo INT_put_daily_stock_tax_to_ML_20110520_002258 
+ cut -c 30-8 
cut: Bad range "30-8" in list

Don't know what is wrong when used cut command.
 

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Cut pid from ps using cut command

hay i am trying to get JUST the PID from the ps command. my command line is: ps -ef | grep "mintty" | cut -d' ' -f2 but i get an empty line. i assume that the delimiter is not just one space character, but can't figure out what should i do in order to do that. i know i can use awk or cut... (8 Replies)
Discussion started by: ran ber
8 Replies

2. UNIX for Beginners Questions & Answers

Cut command: can't make it cut fields

I'm a complete beginner in UNIX (and not a computer science student either), just undergoing a tutoring course. Trying to replicate the instructions on my own I directed output of the ls listing command (lists all files of my home directory ) to My_dir.tsv file (see the screenshot) to make use of... (9 Replies)
Discussion started by: scrutinizerix
9 Replies

3. Shell Programming and Scripting

Using :<<cut / cut to comment out block of bash script

I am using : << cut / cut to comment out block of code. Works fine on few lines of script, then it gives me this cryptic error when I try to comment out about 80 lines. The "warning " is at last line of script. done < results 169 echo "END read all positioning parameters" 170... (8 Replies)
Discussion started by: annacreek
8 Replies
SVK::Log::ChangedPaths(3)				User Contributed Perl Documentation				 SVK::Log::ChangedPaths(3)

NAME
SVK::Log::ChangedPaths - partly lazy list of SVK::Log::ChangedPath objects SYNOPSIS
use SVK::Log::ChangedPaths; my $changed_paths = SVK::Log::ChangedPaths->new( $root ); for my $changed_path ( $changed_paths->paths() ) { ... } DESCRIPTION
An object of this class represents a collection of details about the files/directories that were changed in a particular revision. Some log filters want access to information about which paths were affected during a certain revision and others don't. Using this object allows the calculation of path details to be postponed until it's truly needed. METHODS
new Accepts the return value of "SVK::Path->root()" as a parameter and constructs a SVK::Log::ChangedPaths object from it. paths Returns a list of SVK::Log::ChangedPath objects each of which represents the details of the changes to a particular path. DIAGNOSTICS
None CONFIGURATION AND ENVIRONMENT
SVK::Log::ChangedPaths requires no configuration files or environment variables. DEPENDENCIES
o SVK::Log::ChangedPath INCOMPATIBILITIES
None known BUGS AND LIMITATIONS
None known perl v5.10.0 2008-08-04 SVK::Log::ChangedPaths(3)
All times are GMT -4. The time now is 09:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy