Ebon wrote:
>
> I would assume that HP/UX has no such limitation. Oh well. Thanks
> for the info.
>
All is not lost though. Instead of writing the whole input file to one
output file, consider piping the result of tobyte to split. Here is the man
page for split:
split(1) MPE/iX Shell and Utilities split(1)
______________________________________________________________________
NAME
split -- split a file into manageable pieces
SYNOPSIS
split [-a n] [-l n] [file [prefix]]
split -b n[b|k|m] [-a n] [file [prefix]]
split [-n] [-a n] file [prefix]
DESCRIPTION
split breaks a file up into a set of files. By default, split starts
a new file every time it has copied 1000 lines.
split names the files that it creates as a prefix followed by a
suffix. x is the prefix unless you specify a different prefix on the
command line. Unless altered by options, the suffix begins as aa and
is incremented with each new file. By default, therefore, the first
file is xaa followed by xab, and so on.
Options
split accepts the following options:
-a n uses a suffix n letters long. The default is two.
-b n[b|k|m]
splits the file every n units. The default unit size is bytes.
When you follow n with b, k, or m, split uses a corresponding
unit size of 512 bytes, 1K (1024 bytes), or 1 megabyte (1,048,576
bytes).
-l n splits the file every n lines.
-n is an obsolescent version of the -l option.
If the file is - (dash), split reads the standard input.
DIAGNOSTICS
Possible exit status values are:
0 Successful completion.
1 An error occurred.
So it would appear that if you used the "-" switch to read stdin and the
"-b" or "-l" to break the file up into manageable chunks, then the file(s)
can be put back together on the other machine. You can even start a new
process that ftp's the first chunk while you are still running tobyte.
Food for thought,
Mark Wonsil
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
