Command to output ones (like zero-fill), with progress indicator
Well, I was originally going to post this snippet in the original thread titled "how to output ones endlessly like /dev/zero", but that topic was closed without an efficient answer.
This command seems to get me about 500MByte/min, though this is with a 1.5TB 'green' drive running only at 5400rpm so I imagine it'd be faster in most other cases.
I'm looking for a way in Korn shell to zero fill (or space fill) the output from df so that it will sort properly.
"Raw" output from df -k:
df -k
Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/rootvol 4131866 3593302 497246 88% /
/proc ... (9 Replies)
Can anybody suggest you a good script to show progress of a process.
I figured it out some thing like this. But cursor goes to the end of the line and after every loop it goes to the next line.
while true ; do
for i in \| \/ \- \\ \| \/ \- \\
do
echo "\b\b$i \c"
sleep 1
done
done (8 Replies)
Hi folks,
Please advise which command/command line shall I run;
1) to display the command and its output on console
2) simultaneous to save the command and its output on a file
I tried tee command as follows;
$ ps aux | grep mysql | tee /path/to/output.txt
It displayed the... (7 Replies)
Hi Experts,
I have written a php script that calls several smaller bash shell scripts throughout it's loop process. Users run this script to achieve a task that this script has automated. However this script depending upon the amount of input variables could take some time to run. It may be a... (5 Replies)
Greetings,
I have a hard time creating a large number of user profiles in a database.
The data file looks like this :
01/01/80 Mitch Conley
.
.
.
.
And I need to put the output into:
Name: Mitch
Surname: Conley
Birthday: 01/01/80
Thanks in advance! (3 Replies)
Hi,
I want to use zenity --progress and also put the output to the terminal.
I tried using the tee command but that puts the output to the terminal first and then shows the zenity progress dialog.
Take the normal example by the gnome manual:
(
echo "10" ; sleep 1
... (0 Replies)
I have been trying to fill all available file space on my Solaris box for my project but have not been successful. I have tried the following script:
tr '\0' '\060' < /dev/zero | dd of=zero2.txt bs=1024 count=1953125
But the only thing i get in return is this:
"d: bad numeric argument:... (8 Replies)
Hello,
I use a lot this command to edit a bunch of files at once
find . -name filename" | xargs -ifoo sh -c 'echo foo ; sed "s/pattern1/pattern2/" foo > ./tmp ; mv -f ./tmp foo'
I'm trying to put a function on my .bashrc file.
function loopSed()
{
local filename=$1
local... (2 Replies)
I am using UNIX to create a script on our system. I have setup my commands to append their output to an outage file. However, some of the commands return no output and so I would like something to take their place.
What I need
The following command is placed at the prompt:
TICLI... (4 Replies)
hi all,
i want to monitor the progress of a find and exec command, this is the code i use -
find . -type f -exec md5sum {} \; >> /md5sums/file.txt
this command works and produces a text file with all the md5sums but while running it doesnt show the progress
is there anyway i can do this... (4 Replies)
Discussion started by: robertkwild
4 Replies
LEARN ABOUT BSD
rl
RL(4) Kernel Interfaces Manual RL(4)NAME
rl - RL-11/RL01, RL02 moving-head disk
SYNOPSIS
/sys/conf/SYSTEM:
NRL rl_drives # RL01/02
/etc/dtab:
#Name Unit# Addr Vector Br Handler(s) # Comments
rl ? 174400 160 5 rlintr # rl-01/02
major device number(s):
raw: 16
block: 7
minor device encoding:
bits 0007 specify partition of RL drive
bits 0070 specify RL drive
DESCRIPTION
The block files access the disk via the system's normal buffering mechanism and may be read and written without regard to physical disk
records. There is also a `raw' interface which provides for direct transmission between the disk and the user's read or write buffer. A
single read or write call results in exactly one I/O operation and therefore raw I/O is considerably more efficient when many words are
transmitted. The names of the raw files conventionally begin with an extra `r.'
In raw I/O the buffer must begin on a word (even) boundary, and counts should be a multiple of 512 bytes (a disk sector). Likewise seek
calls should specify a multiple of 512 bytes.
DISK SUPPORT
The RL01 drives are each 10240 blocks long and the RL02 drives are 20480 blocks long.
On a RL02 there is room for a full sized root ('a') partition and a reasonable sized swap ('b') partition. The RL01 can only (realisti-
cally) have a single 5mb partition.
FILES
/dev/rl[0-3][a-h] block files
/dev/rrl[0-3][a-h] raw files
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO hk(4), ra(4), ram(4), rk(4), rp(4), rx(4), si(4), xp(4), dtab(5), autoconfig(8)DIAGNOSTICS
rl%d: hard error sn%d cs=%b da=%b. An unrecoverable error occurred during transfer of the specified sector of the specified disk. The
contents of the two error registers are also printed in octal and symbolically with bits decoded. The error was either unrecoverable, or a
large number of retry attempts could not recover the error.
rl%d: hard error sn%d mp=%b da=%b. An unrecoverable drive error occured during transfer of the specified sector of the specified disk.
The contents of the two error registers are also printed in octal and symbolically with bits decoded. The error was either unrecoverable,
or a large number of retry attempts could not recover the error.
rl%d: write locked. The write protect switch was set on the drive when a write was attempted. The write operation is not recoverable.
rl%d: can't get status. A ``get status'' command on the specified drive failed. The error is unrecoverable.
BUGS
In raw I/O read and write(2) truncate file offsets to 512-byte block boundaries, and write scribbles on the tail of incomplete blocks.
Thus, in programs that are likely to access raw devices, read, write and lseek(2) should always deal in 512-byte multiples.
DEC-standard error logging should be supported.
A program to analyze the logged error information (even in its present reduced form) is needed.
3rd Berkeley Distribution August 20, 1987 RL(4)
08-31-2010
Command to output ones (like zero-fill), with progress indicator
