Sponsored Content
Full Discussion: Change value for POSIX
Top Forums UNIX for Advanced & Expert Users Change value for POSIX Post 303002701 by Abhayman on Thursday 31st of August 2017 01:14:15 AM
Old 08-31-2017
Actually I have 500K arguments to passed . The rough length of each argument is roughly 23 characters . so best i can pass is roughly 175 arguments and each loop . This is making the execution very slow as I was planning to pass roughly 2K per loop. Hence, wanted to bypass the POSIX limit .
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Posix and linux

What is posix? What is the relation between Posix, Unix and linux? (1 Reply)
Discussion started by: darbarilal
1 Replies

2. Programming

ANSI C vs POSIX

can somebody explain about the ANSI C vs POSIX. say i was using open and fopen, i know that open is POSIX, and fopen is ANSI C. i read that that POSIX is a system call and ANSI C is like a standard library function. wouldn't the fopen function has to call on open function anyway to open any kind... (2 Replies)
Discussion started by: bb00y
2 Replies

3. Programming

Unix(posix)

Please,does anybody can give me any general info about unix(posix) ? (1 Reply)
Discussion started by: Haris Astreos
1 Replies

4. UNIX for Dummies Questions & Answers

how to read POSIX?

how to read POSIX? poe six or not? (3 Replies)
Discussion started by: robin.zhu
3 Replies

5. Programming

POSIX threads

Hello ! Let's supose I have a main function in C , and two POSIX threads. I give you an example down : int main() { int something; char else; void *FirstThread(); void *SecondThread(); .. <start those two pthreads ..> return 0;} void *FirstThread() { ... } void *SecondThread()... (2 Replies)
Discussion started by: !_30
2 Replies

6. Programming

Posix

HI, When i am configuring php in SUN Solaris. I am getting the below error. configure: error: Your system seems to lack POSIX threads. Do i need to install POSIX? If so can somebody let me know where can i download POSIX for Solaris 8? Thanks, (2 Replies)
Discussion started by: Krrishv
2 Replies

7. UNIX for Advanced & Expert Users

Posix threads

Hi, consider the code below: #include <stdio.h> . . struct myStruct { char *message ; int id; }; . . . void *thread_function( void *ptr ); nt main() { pthread_t thread1, thread2 ,thread3 ; struct myStruct nico1; (2 Replies)
Discussion started by: Behnaz
2 Replies

8. UNIX for Advanced & Expert Users

System V or POSIX

Hi , I am using UNIX network programming Vol1 (by R Stevens) book to learn about IPC. I would be using HP-UX,Solaris and Linux at my work. I have sections for POSIX and for System V in that book. I am quite confused in indentifying those OSs as POSIX or SYstem V. Can anyone please... (1 Reply)
Discussion started by: kumaran_5555
1 Replies

9. Programming

POSIX Thread Help

I want to create a program that creates 2 child process, and each of them creates 2 threads, and each thread prints its thread id. I0ve allread done that the outuput isn't the outuput i want. When a run the following comand "$./a.out | sort -u | wc -l" I have the folowing output 2 $: It should... (3 Replies)
Discussion started by: pharaoh
3 Replies

10. OS X (Apple)

POSIX compliance...

Thanks to all you guys about posix compliance I have learnt an enormous amount over the last few days. I have written a program that is an Egg Timer with simple animation. I now realise how sophisticated 'bash' is compared to full posix compliance. The code below has passed all of the tests from... (11 Replies)
Discussion started by: wisecracker
11 Replies
RECOVERDISK(1)						    BSD General Commands Manual 					    RECOVERDISK(1)

NAME
recoverdisk -- recover data from hard disk or optical media SYNOPSIS
recoverdisk [-b bigsize] [-r readlist] [-s interval] [-w writelist] source [destination] DESCRIPTION
The recoverdisk utility reads data from the source file until all blocks could be successfully read. If destination was specified all data is being written to that file. It starts reading in multiples of the sector size. Whenever a block fails, it is put to the end of the work- ing queue and will be read again, possibly with a smaller read size. By default it uses block sizes of roughly 1 MB, 32kB, and the native sector size (usually 512 bytes). These figures are adjusted slightly, for devices whose sectorsize is not a power of 2, e.g., audio CDs with a sector size of 2352 bytes. The options are as follows: -b bigsize The size of reads attempted first. The middle pass is roughly the logarithmic average of the bigsize and the sectorsize. -r readlist Read the list of blocks and block sizes to read from the specified file. -s interval How often we should update the writelist file while things go OK. The default is 60 and the unit is "progress messages" so if things go well, this is the same as once per minute. -w writelist Write the list of remaining blocks to read to the specified file if recoverdisk is aborted via SIGINT. The -r and -w options can be specified together. Especially, they can point to the same file, which will be updated on abort. OUTPUT
The recoverdisk utility prints several columns, detailing the progress start Starting offset of the current block. size Read size of the current block. len Length of the current block. state Is increased for every failed read. done Number of bytes already read. remaining Number of bytes remaining. % done Percent complete. EXAMPLES
# recover data from failing hard drive ada3 recoverdisk /dev/ada3 /data/disk.img # clone a hard disk recoverdisk /dev/ada3 /dev/ada4 # read an ISO image from a CD-ROM recoverdisk /dev/cd0 /data/cd.iso # continue reading from a broken CD and update the existing worklist recoverdisk -r worklist -w worklist /dev/cd0 /data/cd.iso # recover a single file from the unreadable media recoverdisk /cdrom/file.avi file.avi # If the disk hangs the system on read-errors try: recoverdisk -b 0 /dev/ada3 /somewhere SEE ALSO
dd(1), ada(4), cam(4), cd(4), da(4) HISTORY
The recoverdisk utility first appeared in FreeBSD 7.0. AUTHORS
The original implementation was done by Poul-Henning Kamp <phk@FreeBSD.org> with minor improvements from Ulrich Sporlein <uqs@FreeBSD.org>. This manual page was written by Ulrich Sporlein. BUGS
Reading from media where the sectorsize is not a power of 2 will make all 1 MB reads fail. This is due to the DMA reads being split up into blocks of at most 128kB. These reads then fail if the sectorsize is not a divisor of 128kB. When reading a full raw audio CD, this leads to roughly 700 error messages flying by. This is harmless and can be avoided by setting -b to no more than 128kB. recoverdisk needs to know about read errors as fast as possible, i.e. retries by lower layers will usually slow down the operation. When using cam(4) attached drives, you may want to set kern.cam.XX.retry_count to zero, e.g.: # sysctl kern.cam.ada.retry_count=0 # sysctl kern.cam.cd.retry_count=0 # sysctl kern.cam.da.retry_count=0 BSD
October 1, 2013 BSD
All times are GMT -4. The time now is 10:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy