![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| Shell Programming and Scripting Post questions about KSH, CSH, SH, BASH, PERL, PHP, SED, AWK and OTHER shell scripts and shell scripting languages here. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| File gets truncated after using sed | corleone | Shell Programming and Scripting | 2 | 09-23-2006 11:11 AM |
| PS truncated in AIX | moe2266 | AIX | 2 | 10-13-2005 04:54 PM |
| ps truncated output | renoc | SUN Solaris | 8 | 05-28-2004 08:14 AM |
| ps output truncated | pciatto | UNIX for Advanced & Expert Users | 5 | 12-02-2003 10:20 AM |
| ps output truncated | pciatto | Shell Programming and Scripting | 1 | 06-09-2003 11:40 AM |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
||||
|
Truncated with a pipe?
OK, I'm stumped.
I have a shell script that reads a list, and for every item in the list performs a lookup in our Active Directory. Now, it seems that when I pipe the results into grep, the complete results are not there (truncated?). I'm not sure if this is a limit of the pipe, grep, shell script or what. The thing is, when I just echo the command into a file, all the info is there, but when I echo into a file after a pipe, it's not. This poses an issue because from the pipe, I need to grep for something. The problem is, the something is not there. If I run the same exact command from the command line, it works. It seems that when running the command from a shell script, it can only handle a certain size result?? Running OS X 10.4.3 Thanks for any help! |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|