Sponsored Content
Full Discussion: File Descriptors + cron
Top Forums UNIX for Advanced & Expert Users File Descriptors + cron Post 302118688 by matrixmadhan on Wednesday 23rd of May 2007 01:45:10 PM
Old 05-23-2007
Quote:
Originally Posted by porter
Depending on the operating system the number of file descriptors per process is fixed in the kernel at compile time or configured with a parameter.

In terms of what makes any process different to UNIX it would be limited really to the following...

1. does it have a controlling terminal attached

2. is it's parent dead

3. is it dead, then it's a zombie and has no memory, no file descriptors and just a minimal entry in the process list.

There are other process wide details such as priority, effective user etc, but not much that makes a process different, even case 2 merely means replace it's parent pid with '1'.

Number of file descriptors is unlikely to change.

Thanks for the reply.

But my question is more related to the difference in the allocation of the file descriptors to the different process ( foreground from the terminal / background ).
 

10 More Discussions You Might Find Interesting

1. Programming

File Descriptors

Hi, I have written a daemon process, to perform certain operations in the background. For this I have to close, the open file descriptors, Does anybody know how to find out the number of open file descriptors ? Thanks in Advance, Sheetal (2 Replies)
Discussion started by: s_chordia
2 Replies

2. UNIX for Advanced & Expert Users

File Descriptors

Hello all, A few questions on file descriptors ... scenario : Sun Ultra 30 with Sun OS 5.5.1 , E250 with Solaris 2.6 In one of my servers, the file descriptor status from the soft limit and hard limits are 64 and 1024 respectively for root user. Is the soft limit (64) represents the... (3 Replies)
Discussion started by: shibz
3 Replies

3. UNIX for Dummies Questions & Answers

file descriptors

i m trying to learn processes in unix and i've been reading this but i don't quite get it. its regarding file descriptors. : each is a part of file pointers, they point to another area. indexes into an Operating system maintained table called "file descriptor table". one table per process. may... (3 Replies)
Discussion started by: a25khan
3 Replies

4. Programming

Sockets and File descriptors

I am in a Systems programming class this semester, and our current project is to write a program utilizing sockets and fork. For the project, I decided to make my own instant messaging program. I have the code completed, but I have a problem that keeps old clients from communicating with new... (3 Replies)
Discussion started by: gstlouis
3 Replies

5. Shell Programming and Scripting

Help with exec command and file descriptors II

Need to close files which descriptor number are larger than 9 in ksh. 'exec 10>&-' fails with 'ksh: 10: not found'. How do you specify file descriptors which occupies two or more digits in ksh script? Thanks, Masaki (2 Replies)
Discussion started by: masaki
2 Replies

6. UNIX for Dummies Questions & Answers

Write/read to file descriptors

Is it possible to write to file descriptor 0 and read from 1 or 2? How could this be implemented? (3 Replies)
Discussion started by: machshev
3 Replies

7. HP-UX

exec and file descriptors

Hi, I speak and write english more or less, so I hope my asking be clear. :) In the company I am working, they are using control-m software to lunch shell scripts. So i put this command in all shell scripts: export LOGFILE_tmp=$PRODUC_DATA/tmp/${SCRIPT}_${PAIS}_`date... (0 Replies)
Discussion started by: anamcara
0 Replies

8. UNIX for Dummies Questions & Answers

Semaphores and File Descriptors

What is the difference between a file descriptor and a semaphore? My basic understanding is: - a file descriptor is a small positive integer that the system uses instead of the file name to identify an open file or socket. - a semaphore is a variable with a value that indicates the... (1 Reply)
Discussion started by: Mr_Webster
1 Replies

9. Shell Programming and Scripting

Confused with redirection and file descriptors

Hi all, I've been looking for the way to send stdout and stderr to different files. Well, actually I really knew how to make it, but I wanted to be sure. I've found an instruction very interesting which I'm not able to understand: taken from this site. It says it sends stdout to output.log,... (4 Replies)
Discussion started by: AlbertGM
4 Replies

10. Shell Programming and Scripting

Questions about file descriptors

Hi, I'm playing with KSH I entered following command in terminal { echo "stdout" >&1; echo "stderr" >&2; } > out And I get only stoud in a new file out. My question is: Where did my stderr vanish ? (5 Replies)
Discussion started by: solaris_user
5 Replies
exit(2) 							System Calls Manual							   exit(2)

NAME
exit(), _exit(), _Exit() - terminate a process SYNOPSIS
Parameters status The values of status can be or as described in or any other value, although only the least significant 8 bits (that is, status is available to a waiting parent process. DESCRIPTION
The function first calls all functions registered by in the reverse order of their registration. Each function is called as many times as it was registered. If a function registered by a call to fails to return, the remaining registered functions are called and the rest of the processing is not completed. terminates the calling process and passes status to the system for inspection {see wait(2)}. Returning from main in a C program has the same effect as the status value is the function value returned by main (this value is undefined if main does not take care to return a value or to call explicitly). If the calling process is multithreaded, all threads/lightweight process in the process will be terminated. cannot return to its caller. The result of an call during exit processing is undefined. The functions and are equivalent, except that calls functions registered by and flushes standard I/O buffers, while does not. The function is equivalent to The functions and terminate the calling process with the following consequences. The exact order of these consequences is unspecified. All file descriptors, directory streams, conversion descriptors, and message catalog descriptors open in the calling process are closed. All files created by are removed (see tmpfile(3S)). If the parent process of the calling process is executing a or it is notified of the calling process's termination, and the low- order eight bits; i.e., bits 0377 of status are made available to it (see wait(2)). If the parent process of the calling process is not executing a or and does not have set to the calling process is transformed into a zombie process. A zombie process is a process that only occupies a slot in the process table. It has no other space allocated either in user or kernel space. Time accounting information is recorded for use by (see times(2)). The parent process ID is set to the process ID of the initialization process (aka for all of the calling process's existing child processes and zombie processes. This means the initialization process inherits each of these processes. Threads/LWPs terminated by a call to shall not invoke their cancellation cleanup handlers or their thread specific data destructor functions. Each attached shared memory segment is detached and the value of in the data structure associated with its shared memory identifier is decremented by 1 (see shmop(2)). For each semaphore for which the calling process has set a semadj value (see semop(2)), that semadj value is added to the value of the specified semaphore. If the process has a process, text, or data lock, an is performed, see plock(2). An accounting record is written on the accounting file if the system's accounting routine is enabled (see acct(2)). A signal is sent to the parent process. If the calling process is a controlling process, the signal is sent to each process in the foreground process group of the control- ling terminal belonging to the calling process. The controlling terminal associated with the session is disassociated from the ses- sion, allowing it to be acquired by a new controlling process. If the exit of the calling process causes a process group to become orphaned, and if any member of the newly-orphaned process group is stopped, all processes in the newly-orphaned process group are sent and signals. If the current process has any child processes that are being traced, they are sent a signal. AUTHOR
was developed by HP, AT&T, and the University of California, Berkeley. and were developed by HP. SEE ALSO
sh(1), acct(2), close(2), plock(2), semop(2), shmget(2), shmop(2), sigaction(2), times(2), vfork(2), wait(2), wait3(2), waitpid(2) atexit(3), fclose(3), pthread_cancel(3T), pthread_exit(3T), pthread_key_create(3T), signal(5). See exit conditions STANDARDS CONFORMANCE
exit(2)
All times are GMT -4. The time now is 06:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy