Sponsored Content
Full Discussion: arg list too long
Top Forums UNIX for Dummies Questions & Answers arg list too long Post 4810 by edge on Wednesday 1st of August 2001 02:32:05 AM
Old 08-01-2001
You could also use grep with ls to get the file list you want:

ls -l | grep 'ABC'
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

egrep and Arg list too long

hi everyone, We have a heck of a lot of files in a particular directory and I need to search through all of them to find a list of all files containing particular text strings...one being a date and the other being the name of the report that is printed on the files..... I've tried the... (6 Replies)
Discussion started by: kingo
6 Replies

2. UNIX for Dummies Questions & Answers

zcat --> Arg list too long

Hi all I have more than 1000 files in a folder and when ever i use a "compress" or "zcat" command it give error /bin/zcat: Arg list too long. . any solution for this :o (3 Replies)
Discussion started by: muneebr
3 Replies

3. UNIX for Advanced & Expert Users

arg list too long

Does anyone have a solution for arg list too long error. I have got this from the web but I fail to make any sense out of it Thanks enc (8 Replies)
Discussion started by: encrypted
8 Replies

4. UNIX for Dummies Questions & Answers

ls -t arg list too long

echo dirname/filename* | xargs ls -t As a substitute doesn't give the results desired when I exceed the buffer size. I still want the files listed in chronological order, unfortunately xargs releases the names piecemeal...does anyone have any ideas? :( (4 Replies)
Discussion started by: CSU_Ram
4 Replies

5. UNIX for Dummies Questions & Answers

arg list too long when mv files?

hello all i need some help because i am a unix/linux dummy...i have the following: DIR1> has 121437 files in it with varying dates going back to early April, a sub dir DIR1/DIR2> has 55835 files in it I need to move all files (T*.*) out of DIR1 into DIR2 that are older than today? Ive been... (2 Replies)
Discussion started by: jamos007
2 Replies

6. UNIX for Dummies Questions & Answers

arg list too long when trying to tar files

Hi, I am trying to perform this task: tar -cvf tar.newfile ??????.bas I got error "arg list too long". Is ther any way around? I have about 1500 file need to be tar together. Thanks in advance (5 Replies)
Discussion started by: jds3
5 Replies

7. UNIX for Dummies Questions & Answers

Arg List too Long in SCP

Hey guys. I have a program written in which i am trying to get the files from one remote machine and transferring the files to another remote machine using SCP. It works fine for 50 or 60 files but when the files grows to 250 then i get an error message stating "Arg list too long". #scp -p... (5 Replies)
Discussion started by: chris1234
5 Replies

8. Shell Programming and Scripting

arg list too long

Hi, Help. I have a file that contains a list of users in a file. I want to cat the content of the file and feed it into sed to a preformated report. The error I got is "ksh: /usr/bin/sed: arg list too long" My method below. A=`cat FILE1.txt` B=`echo $A` sed "s#USERLIST#$B#" FILE2 >... (2 Replies)
Discussion started by: Zenwork
2 Replies

9. Shell Programming and Scripting

arg list too long error

Hello, I'm trying to search through 30,000 files in 1 directory, and am getting the "arg list too long" error. I've searched this forum and have been playing around with xargs and can't get that to work either. I'm using ksh on Solaris. Here's my original code: nawk "/Nov 21/{_=2}_&&_--"... (14 Replies)
Discussion started by: Kristin_in_CO
14 Replies

10. UNIX for Dummies Questions & Answers

Arg list too long

Hello All, I am trying to find a file name with .sh exention from a list of .dat files inside a directory. find /app/folder1/* -name '*.dat'| xargs grep '.sh' ksh: /usr/local/bin/find: arg list too long Please help me finding the command. Thanks (3 Replies)
Discussion started by: tkhan9
3 Replies
explain_fcntl(3)					     Library Functions Manual						  explain_fcntl(3)

NAME
explain_fcntl - explain fcntl(2) errors SYNOPSIS
#include <libexplain/fcntl.h> const char *explain_fcntl(int fildes, int command, long arg); const char *explain_errno_fcntl(int errnum, int fildes, int command, long arg); void explain_message_fcntl(char *message, int message_size, int fildes, int command, long arg); void explain_message_errno_fcntl(char *message, int message_size, int errnum, int fildes, int command, long arg); DESCRIPTION
These functions may be used to obtain explanations for errors returned by the fcntl(2) system call. explain_fcntl const char *explain_fcntl(int fildes, int command, long arg); The explain_fcntl function is used to obtain an explanation of an error returned by the fcntl(2) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. The errno global variable will be used to obtain the error value to be decoded. This function is intended to be used in a fashion similar to the following example: if (fcntl(fildes, command, arg) < 0) { fprintf(stderr, "%s ", explain_fcntl(fildes, command, arg)); exit(EXIT_FAILURE); } fildes The original fildes, exactly as passed to the fcntl(2) system call. command The original command, exactly as passed to the fcntl(2) system call. arg The original arg, exactly as passed to the fcntl(2) system call. Returns: The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads. Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. explain_errno_fcntl const char *explain_errno_fcntl(int errnum, int fildes, int command, long arg); The explain_errno_fcntl function is used to obtain an explanation of an error returned by the fcntl(2) system call. The least the message will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail. This function is intended to be used in a fashion similar to the following example: if (fcntl(fildes, command, arg) < 0) { int err = errno; fprintf(stderr, "%s ", explain_errno_fcntl(err, fildes, command, arg)); exit(EXIT_FAILURE); } errnum The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces- sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno. fildes The original fildes, exactly as passed to the fcntl(2) system call. command The original command, exactly as passed to the fcntl(2) system call. arg The original arg, exactly as passed to the fcntl(2) system call. Returns: The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads. Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. explain_message_fcntl void explain_message_fcntl(char *message, int message_size, int fildes, int command, long arg); The explain_message_fcntl function may be used to obtain an explanation of an error returned by the fcntl(2) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. The errno global variable will be used to obtain the error value to be decoded. This function is intended to be used in a fashion similar to the following example: if (fcntl(fildes, command, arg) < 0) { char message[3000]; explain_message_fcntl(message, sizeof(message), fildes, command, arg); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } message The location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe. message_size The size in bytes of the location in which to store the returned message. fildes The original fildes, exactly as passed to the fcntl(2) system call. command The original command, exactly as passed to the fcntl(2) system call. arg The original arg, exactly as passed to the fcntl(2) system call. explain_message_errno_fcntl void explain_message_errno_fcntl(char *message, int message_size, int errnum, int fildes, int command, long arg); The explain_message_errno_fcntl function may be used to obtain an explanation of an error returned by the fcntl(2) system call. The least the message will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail. This function is intended to be used in a fashion similar to the following example: if (fcntl(fildes, command, arg) < 0) { int err = errno; char message[3000]; explain_message_errno_fcntl(message, sizeof(message), err, fildes, command, arg); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } message The location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe. message_size The size in bytes of the location in which to store the returned message. errnum The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces- sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno. fildes The original fildes, exactly as passed to the fcntl(2) system call. command The original command, exactly as passed to the fcntl(2) system call. arg The original arg, exactly as passed to the fcntl(2) system call. SEE ALSO
fcntl(2) manipulate a file descriptor explain_fcntl_or_die(3) manipulate a file descriptor and report errors COPYRIGHT
libexplain version 0.52 Copyright (C) 2008 Peter Miller explain_fcntl(3)
All times are GMT -4. The time now is 01:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy