Sponsored Content
Top Forums Programming Copy a file using UNIX-system calls Post 302300936 by jim mcnamara on Wednesday 25th of March 2009 12:00:00 PM
Old 03-25-2009
Quote:
well in my textbook it says
Do not use a textbook, reference the man page for read. There are a lot of reasons for doing using the man page, you've discovered the first one.
Code:
man 2 read

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

System Calls

What does the system call "dup" do? What is the difference between dup and dup2 I have a fair idea of what it does but I am confused when its coming down to the exact details... Please help me!:confused: (2 Replies)
Discussion started by: clickonline1
2 Replies

2. UNIX for Dummies Questions & Answers

System calls for cp and mv

Which system calls are made for operations cp and mv (2 Replies)
Discussion started by: gaurava99
2 Replies

3. UNIX for Dummies Questions & Answers

System calls?

open, creat, read, write, lseek and close Are they all primitive? :confused: *Another Question: is there a different between a system call, and an i/o system call? (2 Replies)
Discussion started by: PlunderBunny
2 Replies

4. Solaris

System calls ?

where can i find the differences in System calls between solaris and aix? also is it possible to find a comprehensive list of them? (1 Reply)
Discussion started by: TECHRAMESH
1 Replies

5. UNIX Desktop Questions & Answers

Using system calls

Hi, I'm new to UNIX system calls. Can someone share your knowledge as to how exactly system calls should be executed? Can they be typed like commands such as mkdir on the terminal itself? Also, are there any websites which will show me an example of the output to expect when a system call like... (1 Reply)
Discussion started by: ilavenil
1 Replies

6. UNIX for Dummies Questions & Answers

About system calls.

Hi all, I am new here . I want to know about system call in detail. As system calls are also function .How system identifies it.:) (2 Replies)
Discussion started by: vishwasrao
2 Replies

7. UNIX for Dummies Questions & Answers

system calls in C

Hello, how would i be able to call ps in C programming? thanks, ---------- Post updated at 01:39 AM ---------- Previous update was at 01:31 AM ---------- here's the complete system call, ps -o pid -p %d, getpit() (2 Replies)
Discussion started by: l flipboi l
2 Replies

8. UNIX for Dummies Questions & Answers

Unix directory system calls question

I'm currently studying for my exam, and is practicing with sample exam questions. However there is a question asking "Name THREE UNIX Directory system calls" and the answer given is "opendir, closedir and readdir", however the next question ask "Why is a write directory system call not included... (1 Reply)
Discussion started by: Izzy123
1 Replies

9. UNIX for Dummies Questions & Answers

How to Export Glance "Global System Calls" data to a file

Hello... I'm trying to setup a cronjob to record system data using glance at certain times of the day. My question is, how would one export the "Global System Calls" information to a file? Below is the command I have been using and it works to export CPU information. glance -f ... (0 Replies)
Discussion started by: fumus
0 Replies

10. UNIX for Dummies Questions & Answers

System calls in UNIX

Hi i am very new to programming in UNIX and don't understand the difference between a system call and a normal function call. Also can I implement system calls from within a program? If so could someone please give me an example of a system call from within a program. Lastly, when creating a... (1 Reply)
Discussion started by: bjhum33
1 Replies
LEXGROG(1)							Manual pager utils							LEXGROG(1)

NAME
lexgrog - parse header information in man pages SYNOPSIS
lexgrog [-m|-c] [-fhwV] [-E encoding] file ... DESCRIPTION
lexgrog is an implementation of the traditional "groff guess" utility in lex. It reads the list of files on its command line as either man page source files or preformatted "cat" pages, and displays their name and description as used by apropos and whatis, the list of prepro- cessing filters required by the man page before it is passed to nroff or troff, or both. If its input is badly formatted, lexgrog will print "parse failed"; this may be useful for external programs that need to check man pages for correctness. If one of lexgrog's input files is "-", it will read from standard input; if any input file is compressed, a decompressed version will be read automatically. OPTIONS
-m, --man Parse input as man page source files. This is the default if neither --man nor --cat is given. -c, --cat Parse input as preformatted man pages ("cat pages"). --man and --cat may not be given simultaneously. -w, --whatis Display the name and description from the man page's header, as used by apropos and whatis. This is the default if neither --whatis nor --filters is given. -f, --filters Display the list of filters needed to preprocess the man page before formatting with nroff or troff. -E encoding, --encoding encoding Override the guessed character set for the page to encoding. -h, --help Print a help message and exit. -V, --version Display version information. EXIT STATUS
0 Successful program execution. 1 Usage error. 2 lexgrog failed to parse one or more of its input files. EXAMPLES
$ lexgrog man.1 man.1: "man - an interface to the on-line reference manuals" $ lexgrog -fw man.1 man.1 (t): "man - an interface to the on-line reference manuals" $ lexgrog -c whatis.cat1 whatis.cat1: "whatis - display manual page descriptions" $ lexgrog broken.1 broken.1: parse failed WHATIS PARSING
mandb (which uses the same code as lexgrog) parses the NAME section at the top of each manual page looking for names and descriptions of the features documented in each. While the parser is quite tolerant, as it has to cope with a number of different forms that have histori- cally been used, it may sometimes fail to extract the required information. When using the traditional man macro set, a correct NAME section looks something like this: .SH NAME foo - program to do something Some manual pagers require the '-' to be exactly as shown; mandb is more tolerant, but for compatibility with other systems it is never- theless a good idea to retain the backslash. On the left-hand side, there may be several names, separated by commas. Names containing whitespace will be ignored to avoid pathological behaviour on certain ill-formed NAME sections. The text on the right-hand side is free-form, and may be spread over multiple lines. If several features with different descriptions are being documented in the same manual page, the following form is therefore used: .SH NAME foo, bar - programs to do something .br baz - program to do nothing (A macro which starts a new paragraph, like .PP, may be used instead of the break macro .br.) When using the BSD-derived mdoc macro set, a correct NAME section looks something like this: .Sh NAME .Nm foo .Nd program to do something There are several common reasons why whatis parsing fails. Sometimes authors of manual pages replace '.SH NAME' with '.SH MYPROGRAM', and then mandb cannot find the section from which to extract the information it needs. Sometimes authors include a NAME section, but place free-form text there rather than 'name - description'. However, any syntax resembling the above should be accepted. SEE ALSO
man(1), mandb(8), apropos(1), whatis(1). NOTES
lexgrog attempts to parse files containing .so requests, but will only be able to do so correctly if the files are properly installed in a manual page hierarchy. AUTHOR
The code used by lexgrog to scan man pages was written by: Wilf. (G.Wilford@ee.surrey.ac.uk). Fabrizio Polacco (fpolacco@debian.org). Colin Watson (cjwatson@debian.org). Colin Watson wrote the current incarnation of the command-line front-end, as well as this man page. 2.6.0.2 2011-04-13 LEXGROG(1)
All times are GMT -4. The time now is 05:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy