I'm trying to do two different things (converting an OpenVms .com to a ksh shell script): 1) open/read/err= 2) open/write/err=
Any help? I've found some things, but can't seem to find the correct way. (1 Reply)
Hi. I ran nmap on my server, and I get the following:
Starting Nmap 4.76 ( http://nmap.org ) at 2009-03-19 16:33 EDT
Interesting ports on -------- (-----):
Not shown: 997 closed ports
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
6881/tcp open bittorrent-tracker
The... (0 Replies)
First post, sorry to be a bother but this one has been dogging me. I have a process user (java application server) that trips a resource limit every couple weeks and need help finding what limit we're hitting.
First, this is what's running:
This is the error when jobs are run or the... (0 Replies)
Hi there,
I'm sorry in advance if my question seems stupid, but I can't figure out myself.
I was wondering. Is it possible to install a Solaris program on an Open Solaris or Open Indiana operating system?
After searching the web for a long time, it seems that Open Solaris was released by... (7 Replies)
Hi Friends,
Every I try to open a vi window vim help.txt automatically opens evertime.
After doing ZZ or :q! also the same page opens automatically.
How to stop this? Is it machine specific ? Other users who are opening the same servers and files are not facing this issue.
Thanks... (1 Reply)
Hi Friends,
Every I try to open a vi window, vim help.txt automatically opens evertime.
After doing ZZ or :q! also the same page opens automatically.
How to stop this? Is it machine specific ? Other users who are opening the same servers and files are not facing this issue.
Thanks... (3 Replies)
Discussion started by: sudiptabhaskar
3 Replies
LEARN ABOUT REDHAT
close
CLOSE(2) Linux Programmer's Manual CLOSE(2)NAME
close - close a file descriptor
SYNOPSIS
#include <unistd.h>
int close(int fd);
DESCRIPTION
close closes a file descriptor, so that it no longer refers to any file and may be reused. Any locks held on the file it was associated
with, and owned by the process, are removed (regardless of the file descriptor that was used to obtain the lock).
If fd is the last copy of a particular file descriptor the resources associated with it are freed; if the descriptor was the last reference
to a file which has been removed using unlink(2) the file is deleted.
RETURN VALUE
close returns zero on success, or -1 if an error occurred.
ERRORS
EBADF fd isn't a valid open file descriptor.
EINTR The close() call was interrupted by a signal.
EIO An I/O error occurred.
CONFORMING TO
SVr4, SVID, POSIX, X/OPEN, BSD 4.3. SVr4 documents an additional ENOLINK error condition.
NOTES
Not checking the return value of close is a common but nevertheless serious programming error. It is quite possible that errors on a pre-
vious write(2) operation are first reported at the final close. Not checking the return value when closing the file may lead to silent
loss of data. This can especially be observed with NFS and disk quotas.
A successful close does not guarantee that the data has been successfully saved to disk, as the kernel defers writes. It is not common for
a filesystem to flush the buffers when the stream is closed. If you need to be sure that the data is physically stored use fsync(2). (It
will depend on the disk hardware at this point.)
SEE ALSO open(2), fcntl(2), shutdown(2), unlink(2), fclose(3), fsync(2)
2001-12-13 CLOSE(2)