Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Difference between file descriptor and file pointer Post 302444882 by kvok on Friday 13th of August 2010 05:31:11 AM
Old 08-13-2010
Quote:
Originally Posted by karthigayan
File descriptor is an integer which is an index in the kernel on the opened files(Which is called file descriptor table).It is used to deal with the files . most of the functions like open,close,read using the file descriptors to deal with the files.

File pointer is a location with in the file.Which points the next character which going to read.
So shall I understand that the filedescriptor is number of amount connections for particular process/program which will be used ? and its predefined ?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

file activity (open/closed) file descriptor info using KORN shell scripting

I am trying to find a way to check the current status of a file. Such as some cron job processes are dependent on the completion of others. if a file is currently being accessed / modified or simply open state I will wait until it is done being processed before attempting the next process on that... (3 Replies)
Discussion started by: Gary Dunn
3 Replies

2. UNIX for Dummies Questions & Answers

File Descriptor Help

What is a file descriptor in Unix?? How to find a file descriptor of a file in Unix?? Does it have anything to do with the Inode numbers?? (3 Replies)
Discussion started by: rahulrathod
3 Replies

3. UNIX for Dummies Questions & Answers

confusion (file pointer and file descripter)

Hi everybody, i am newbie to unix and confused with file pointers and file descripters. could anyone help me to clear my doubts .. when we call unix system calls to create a file then we are dealing wih file descripters i think file descripters are also normals file as stored inhard disks... (1 Reply)
Discussion started by: johnray31
1 Replies

4. Programming

Get the file descriptor of a socket file. C vs Python.

Hi, I want to validate that a file is a socket file on Linux. I know I can do this using the S_ISSOCK macro, but I am not sure how to get the file descriptor for the socket file. For example, I know that /tmp/mapping-foo is a socket file. In Python I can do something like this: >>> import... (2 Replies)
Discussion started by: goon12
2 Replies

5. Shell Programming and Scripting

File Descriptor

Hello All, Im opening a file desciptor in perl and sending data using print CMD "$xyz". is there a limit to the length of the string that I can give to this CMD at a time. (3 Replies)
Discussion started by: rimser9
3 Replies

6. UNIX for Dummies Questions & Answers

File Descriptor

Hi What the below path contains? /proc/<pid>/fd (1 Reply)
Discussion started by: siba.s.nayak
1 Replies

7. Programming

Copying and overwriting a file using file descriptor

Hi , i have two basic requirement on linux platform . I am using C language to do this . 1) copying one file to another (assuming i know their file descriptors) 2) Overwriting a file using it file descriptor . Please guide. regards Aki (2 Replies)
Discussion started by: meet123321
2 Replies

8. Shell Programming and Scripting

file descriptor KSH

Hello, How can i use file descriptor in a script to read 2 files at the same time and extract line 200 from file 1 and line 500 from file 2. Thanks. (6 Replies)
Discussion started by: LiorAmitai
6 Replies

9. Shell Programming and Scripting

file descriptor count

I am trying to write a script which will only show me the file descriptor count for a process/pid. My script will return me the count only not the whole output. For example, I would like my script to return the output 23 this case, not the whole output. Can anybody please help me how do I get... (11 Replies)
Discussion started by: mohullah
11 Replies

10. Shell Programming and Scripting

Variable File Descriptor

Greetings. I am happily using constructs like the following; I have set -x to show fine distinctions. $ exec 4> afile + exec + 4> afile $ print -u4 This is the first line in afileAs you can see from the -x expansion, the shell performed the exec command and redirected file descriptor to... (4 Replies)
Discussion started by: rpaskudniak
4 Replies
closefrom(3C)						   Standard C Library Functions 					     closefrom(3C)

NAME
closefrom, fdwalk - close or iterate over open file descriptors SYNOPSIS
#include <stdlib.h> void closefrom(int lowfd); int fdwalk(int (*func)(void *, int), void *cd); DESCRIPTION
The closefrom() function calls close(2) on all open file descriptors greater than or equal to lowfd. The effect of closefrom(lowfd) is the same as the code #include <sys/resource.h> struct rlimit rl; int i; getrlimit(RLIMIT_NOFILE, &rl); for (i = lowfd; i < rl.rlim_max; i++) (void) close(i); except that close() is called only on file descriptors that are actually open, not on every possible file descriptor greater than or equal to lowfd, and close() is also called on any open file descriptors greater than or equal to rl.rlim_max (and lowfd), should any exist. The fdwalk() function first makes a list of all currently open file descriptors. Then for each file descriptor in the list, it calls the user-defined function, func(cd, fd), passing it the pointer to the callback data, cd, and the value of the file descriptor from the list, fd. The list is processed in file descriptor value order, lowest numeric value first. If func() returns a non-zero value, the iteration over the list is terminated and fdwalk() returns the non-zero value returned by func(). Otherwise, fdwalk() returns 0 after having called func() for every file descriptor in the list. The fdwalk() function can be used for fine-grained control over the closing of file descriptors. For example, the closefrom() function can be implemented as: static int close_func(void *lowfdp, int fd) { if (fd >= *(int *)lowfdp) (void) close(fd); return(0); } void closefrom(int lowfd) { (void) fdwalk(close_func, &lowfd); } The fdwalk() function can then be used to count the number of open files in the process. RETURN VALUES
No return value is defined for closefrom(). If close() fails for any of the open file descriptors, the error is ignored and the file descriptors whose close() operation failed might remain open on return from closefrom(). The fdwalk() function returns the return value of the last call to the callback function func(), or 0 if func() is never called (no open files). ERRORS
No errors are defined. The closefrom() and fdwalk() functions do not set errno but errno can be set by close() or by another function called by the callback function, func(). FILES
/proc/self/fd directory (list of open files) USAGE
The act of closing all open file descriptors should be performed only as the first action of a daemon process. Closing file descriptors that are in use elsewhere in the current process normally leads to disastrous results. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |MT-Level |Unsafe | +-----------------------------+-----------------------------+ SEE ALSO
close(2), getrlimit(2), proc(4), attributes(5) SunOS 5.11 27 Apr 2000 closefrom(3C)
All times are GMT -4. The time now is 06:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy