Sponsored Content
Top Forums Shell Programming and Scripting Argument list too long for date command Post 302556158 by tamil.pamaran on Friday 16th of September 2011 07:51:06 PM
Old 09-16-2011
Argument list too long for date command

Dear Friends,

The following script processes a 14508 lines log file.

Code:
#!/bin/sh
while read line
do
     d=`sed 's/[0-9|.]* - [-|a-zA-Z]* \[\([0-9]*\/[a-zA-Z]*\/[0-9:]* [0-9+]*\)\] .*/\1/' | tr '/' ' ' | sed 's/\([.]*\):\([.]*\)/\1 \2/'`
     y=`date -d "${d}" "+%Y%m%d%H%M%S"`
     echo "${y}"
done

While running the above script, I am getting argument list long error. Can anyone help me to come out this error. I don't this issue if I split two processes(sed and date) in to different files.

Thanks,
Tamil Pamaran

Last edited by pludi; 09-17-2011 at 08:01 PM..
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

command find returned bash: /usr/bin/find: Argument list too long

Hello, I create a file touch 1201093003 fichcomp and inside a repertory (which hava a lot of files) I want to list all files created before this file : find *.* \! -maxdepth 1 - newer fichcomp but this command returned bash: /usr/bin/find: Argument list too long but i make a filter all... (1 Reply)
Discussion started by: yacsil
1 Replies

2. UNIX for Dummies Questions & Answers

Argument list too long - SSH

Hi I executed the code for file in `ls pdb*.ent` do new_name=`echo $file | sed 's/^pdb//;s/.ent/.txt/'` mv $file $new_name done Its giving error at ' ls pdb*.ent' argument list too long i have around 150000 entries please help Thank you (6 Replies)
Discussion started by: empyrean
6 Replies

3. Shell Programming and Scripting

Argument too long list error

I have a wrote a script which consits of the below line.. Below of this script I'm getting this error "ksh: /usr/bin/ls: arg list too long" The line is log_file_time=`ssh -i $HOME/.ssh/id_rsa -q $i ls -lrt /bp/karthik/test/data/log/$abc*|tail -1|awk '{print $8}'` And $abc alias is as "p |... (1 Reply)
Discussion started by: 22karthikreddy
1 Replies

4. UNIX for Dummies Questions & Answers

Argument list too long for Sed command

Hi guys Following command results in sed -i 's/#/\\#/g' /home/test/sqlstents* -bash: /bin/sed: Argument list too long Please help me solve it.. is there any other way i can do this?.. thanks (4 Replies)
Discussion started by: depakjan
4 Replies

5. Shell Programming and Scripting

Argument list too long problem

I have a huge set of files (with extension .common) in my directory around 2 million. When I run this script on my Linux with BASH, I get /bin/awk: Argument list too long awk -F'\t' ' NR == FNR { a=NR } NR != FNR { sub(".common", "", FILENAME) print a, FILENAME, $1 } '... (1 Reply)
Discussion started by: shoaibjameel123
1 Replies

6. Shell Programming and Scripting

Argument list too long!!

Dear Experts, I have a list of 10K files in a directory. I am not able to execute any commands lile ls -lrt, awk, sed, mv, etc........ I wanna execute below command and get the output. How can I achieve it?? Pls help. root# awk -F'|' '$1 == 1' file_20120710* | wc -l /bin/awk: Argument list... (2 Replies)
Discussion started by: Naga06
2 Replies

7. Shell Programming and Scripting

grep : Argument list too long

Hi, i am having some trouble with the below command, can some one suggest me the better way to do it. grep -l 'ReturnCode=1' `find $Log -newer /tmp/Failed.tmp -print | xargs ls -ld | egrep SUB | egrep -ve 'MTP' -ve 'ABC' -ve 'DEF' -ve 'JKL' -ve 'XYZ' | awk '{print $9}'` > $Home1 Its... (2 Replies)
Discussion started by: Prateek007
2 Replies

8. Shell Programming and Scripting

mv : Argument list too long

Hi I am using find command -- find "directory1" -type f | xargs -i mv {} "directory2" to avoid above argument list too long problem. But, issue i am facing is directory1 is having subdirectories due to this i am facing directory traversal problem as i dont want to traverse subdirectories... (9 Replies)
Discussion started by: VSom007
9 Replies

9. UNIX for Advanced & Expert Users

Argument list too long w/ sed

Hi all, I am using GNU sed (named gsed under macports) in OSX. I have a directory with a series of files named pool_01.jpg through pool_78802.jpg. I am trying to use this command to rename the files to their checksum + extension. md5sum * | gsed -e 's/\(*\) \(.*\(\..*\)\)$/mv -v \2 \1\3/e' ... (3 Replies)
Discussion started by: openthomas
3 Replies

10. Shell Programming and Scripting

Argument list too long

Hi Team, Here's the situation. I have approximately 300000 to 500000 jpg files in /appl/abcd/work_dir mv /appl/abcd/work_dir /appl/abcd/process_dir The above move command will work if the jpg files count is close to 50000 (not sure). If the count is less this mv command holds good. But if... (14 Replies)
Discussion started by: kmanivan82
14 Replies
sed(1)							      General Commands Manual							    sed(1)

Name
       sed - stream text editor

Syntax
       sed [-n] [-e script] [-f sfile] [file...]

Description
       The  command  copies  the  named  files	(standard input default) to the standard output, edited according to a script of commands.  The -f
       option causes the script to be taken from file sfile; these options accumulate.	If there is just one -e option and no -f's,  the  flag	-e
       may  be omitted.  The -n option suppresses the default output; inclusion in the script of a comment command of the form also suppresses the
       default output.	(See the description of the `#' command.)

       A script consists of editing commands of the following form:

	      [address [, address] ] function [arguments]

       Nominally, there is one command per line; but commands can be concatenated on a line by being separated with semicolons

       In normal operation cyclically copies a line of input into a pattern space (unless there is something left after a `D' command), applies in
       sequence all commands whose addresses select that pattern space, and at the end of the script copies the pattern space to the standard out-
       put (except under -n) and deletes the pattern space.

       An address is either a decimal number that counts input lines cumulatively across files, a `$' that addresses the last line of input, or  a
       context address, `/regular expression/', in the style of ed(1) modified thus:

	  o    In  a  context  address, the construction ?regular expression?, where ? is any character, is identical to regular expression. Note
	       that in the context address xabcxdefx, the second x stands for itself, so that the regular expression is abcxdef.

	  o    The escape sequence `
' matches a new line embedded in the pattern space.

	  o    A command line with no addresses selects every pattern space.

	  o    A command line with one address selects each pattern space that matches the address.

	  o    A command line with two addresses selects the inclusive range from the first pattern space that matches the first  address  through
	       the  next  pattern  space  that matches the second.  (If the second address is a number less than or equal to the line number first
	       selected, only one line is selected.)  Thereafter the process is repeated, looking again for the first address.

       Editing commands can be applied only to non-selected pattern spaces by use of the negation function `!' (below).

       In the following list of functions the maximum number of permissible addresses for each function is indicated in parentheses.

       An argument denoted text consists of one or more lines, all but the last of which end with `' to hide the new line.  Backslashes  in  text
       are  treated  like  backslashes in the replacement string of an `s' command, and may be used to protect initial blanks and tabs against the
       stripping that is done on every script line.

       An argument denoted rfile or wfile must terminate the command line and must be preceded by exactly one blank.  Each wfile is created before
       processing begins.  There can be at most 10 distinct wfile arguments.

       (1)a
       text
	       Append.	Place text on the output before reading the next input line.

       (2)b label
	       Branch to the `:' command bearing the label.  If label is empty, branch to the end of the script.

       (2)c
       text
	       Change.	 Delete  the  pattern space.  With 0 or 1 address or at the end of a 2-address range, place text on the output.  Start the
	       next cycle.

       (2)d    Delete the pattern space.  Start the next cycle.

       (2)D    Delete the initial segment of the pattern space through the first new line.  Start the next cycle.

       (2)g    Replace the contents of the pattern space by the contents of the hold space.

       (2)G    Append the contents of the hold space to the pattern space.

       (2)h    Replace the contents of the hold space by the contents of the pattern space.

       (2)H    Append the contents of the pattern space to the hold space.

       (1)i
       text
	       Insert.	Place text on the standard output.

       (2)n    Copy the pattern space to the standard output.  Replace the pattern space with the next line of input.

       (2)N    Append the next line of input to the pattern space with an embedded new line.  (The current line number changes.)

       (2)p    Print.  Copy the pattern space to the standard output.

       (2)P    Copy the initial segment of the pattern space through the first new line to the standard output.

       (1)q    Quit.  Branch to the end of the script.	Do not start a new cycle.

       (2)r rfile
	       Read the contents of rfile.  Place them on the output before reading the next input line.

       (2)s/regular expression/replacement/flags
	       Substitute the replacement string for instances of the regular expression in the pattern space.	Any character may be used  instead
	       of `/'.	For a more complete description see The flags is zero or more of

	       g       Global.	Substitute for all nonoverlapping instances of the regular expression rather than just the first one.

	       p       Print the pattern space if a replacement was made.

	       w wfile Write.  Append the pattern space to wfile if a replacement was made.

       (2)t label
	       Test.   Branch  to  the `:' command bearing the label if any substitutions have been made since the most recent reading of an input
	       line or execution of a `t'.  If label is empty, branch to the end of the script.

       (2)w wfile
	       Write.  Append the pattern space to wfile.

       (2)x    Exchange the contents of the pattern and hold spaces.

       (2)y/string1/string2/
	       Transform.  Replace all occurrences of characters in string1 with the corresponding character in string2.  The lengths  of  string1
	       and string2 must be equal.

       (2)! function
	       Don't.  Apply the function (or group, if function is `{') only to lines not selected by the address(es).

       (0): label
	       This command does nothing; it bears a label for `b' and `t' commands to branch to.

       (1)=    Place the current line number on the standard output as a line.

       (2){    Execute the following commands through a matching `}' only when the pattern space is selected.

       (0)     An empty command is ignored.

       (0)#    With one exception, any line whose first nonblank character is a number sign is a comment and is ignored.  The exception is that if
	       the first such line encountered contains only the number sign followed by the letter `n' the default output is suppressed as if the
	       -n option were in force.

Options
       -e 'command;command...'
	       Uses command;command...	as the editing script.	If no -f option is given, the -e keyword can be omitted.  For example, the follow-
	       ing two command are functionally identical:
	       % sed -e 's/DIGITAL/Digital/g' summary > summary.out
	       % sed 's/DIGITAL/Digital/g' summary > summary.out

       -f sfile
	       Uses specified file as input file of commands to be executed.  Can be used with -e option to apply both	explicit  commands  and  a
	       separate script file.

       -n      Suppresses  all	normal	output, writing only lines explicitly written by the `p' or `P' commands or by an `s' command with the `p'
	       flag.

See Also
       awk(1), ed(1), grep(1), lex(1)

																	    sed(1)
All times are GMT -4. The time now is 11:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy