diff options
author | rodent <rodent> | 2013-04-07 20:49:31 +0000 |
---|---|---|
committer | rodent <rodent> | 2013-04-07 20:49:31 +0000 |
commit | da9d557ccd4313490cdcaabf97f4bce19df13498 (patch) | |
tree | 79de035a23bbb285c8713b492fa4fa499634f7f8 /misc/buffer | |
parent | c0be38a4f5e5d44fa50008152988b43e17259963 (diff) | |
download | pkgsrc-da9d557ccd4313490cdcaabf97f4bce19df13498.tar.gz |
Edited DESCR in the case of:
File too long (should be no more than 24 lines).
Line too long (should be no more than 80 characters).
Trailing empty lines.
Trailing white-space.
Trucated the long files as best as possible while preserving the most info
contained in them.
Diffstat (limited to 'misc/buffer')
-rw-r--r-- | misc/buffer/DESCR | 27 |
1 files changed, 12 insertions, 15 deletions
diff --git a/misc/buffer/DESCR b/misc/buffer/DESCR index 00f61412db7..b62749726a1 100644 --- a/misc/buffer/DESCR +++ b/misc/buffer/DESCR @@ -1,20 +1,17 @@ -This is a program designed to speed up writing tapes on remote tape -drives. Requirements are shared memory and locks which normally -means that these are supported in your kernel. +This is a program designed to speed up writing tapes on remote tape drives. +Requirements are shared memory and locks which normally means that these are +supported in your kernel. [for FreeBSD/NetBSD, this means you MUST have a kernel +with options SYSVSHM compiled in - markm] -[for Free/NetBSD, this means you MUST have a kernel with - options SYSVSHM - compiled in - markm] +Buffer has been tested under SunOS 4.0.*, SunOS 4.1.*, Solarix, HP-UX 7.0, and +Gould UTX 2.1A (sv universe). -Buffer has been tested under SunOS 4.0.*, SunOS 4.1.*, Solarix, HP-UX 7.0, -and Gould UTX 2.1A (sv universe). - -The program splits itself into two processes. The first process reads -(and reblocks) from stdin into a shared memory buffer. The second -writes from the shared memory buffer to stdout. Doing it this way -means that the writing side effectly sits in a tight write loop and -doesn't have to wait for input. Similarly for the input side. It is -this waiting that slows down other reblocking processes, like dd. +The program splits itself into two processes. The first process reads (and +reblocks) from stdin into a shared memory buffer. The second writes from the +shared memory buffer to stdout. Doing it this way means that the writing side +effectly sits in a tight write loop and doesn't have to wait for input. +Similarly for the input side. It is this waiting that slows down other +reblocking processes, like dd. I run an archive and need to write large chunks out to tape regularly with an ethernet in the way. Using 'buffer' in a command like: |