Cut Command error cut: Bad range Post: 302524124

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

05-21-2011

Registered User

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.

dgmm

View Public Profile for dgmm

Find all posts by dgmm

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...

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...

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...

LEARN ABOUT DEBIAN

log::dispatch::configurator::appconfig

Log::Dispatch::Configurator::AppConfig(3pm)		User Contributed Perl Documentation	       Log::Dispatch::Configurator::AppConfig(3pm)

NAME

       Log::Dispatch::Configurator::AppConfig - Configurator implementation with AppConfig

SYNOPSIS

	 use Log::Dispatch::Config;
	 use Log::Dispatch::Configurator::AppConfig;

	 my $config = Log::Dispatch::Configurator::AppConfig->new('log.cfg');
	 Log::Dispatch::Config->configure($config);

	 # nearby piece of code
	 my $log = Log::Dispatch::Config->instance;

DESCRIPTION

       Log::Dispatch::Configurator::AppConfig is an implementation of Log::Dispatch::Configurator using AppConfig format. Here is a sample of
       config file.

	 dispatchers = file screen

	 file.class = Log::Dispatch::File
	 file.min_level = debug
	 file.filename = /path/to/log
	 file.mode = append
	 file.format = [%d] [%p] %m at %F line %L%n

	 screen.class = Log::Dispatch::Screen
	 screen.min_level = info
	 screen.stderr = 1
	 screen.format = %m

       You can use ini style grouping.

	 [file]
	 class = Log::Dispatch::File
	 min_level = debug

	 [screen]
	 class = Log::Dispatch::Screen
	 min_level = info

       If you use _ (underscore) in dispatcher name, something very bad may happen. It is safe when you avoid doing so.

AUTHOR

       Tatsuhiko Miyagawa <miyagawa@bulknews.net>

       This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

SEE ALSO

       Log::Dispatch::Config, AppConfig

perl v5.14.2							    2010-02-05			       Log::Dispatch::Configurator::AppConfig(3pm)