01-23-2013
Is there an error telling you it's read-only? If so, what is telling you that? An application?
Obviously you can't write new data to a full filesystem so a poorly written application could interpret the O/S's refusal to write as read-only error.
So, what's giving you the error?
This User Gave Thanks to hicksd8 For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi All,
Could any one please help me in performing the following?
We have the following folder:
/home/test/proj1
/home/test/proj2
/home/test/proj3
Users from different country places files in this folder using FTP (These users uses different flavors of FTP tools).
Our... (1 Reply)
Discussion started by: vfrg
1 Replies
2. Shell Programming and Scripting
In my script, I am creating a file ----> then writting one line (i.e. Timestamp) ----> then FTP'ing. The same script can be executed by many other users.
While other users executing this script, they couldn't Over write this one line (i.e. Timestamp)
My expectation
So I wanted to create a... (2 Replies)
Discussion started by: sbmk_design
2 Replies
3. UNIX for Advanced & Expert Users
I was tryin to copy a large file under /tmp location.
I guess the disk space got full and i got fork error.
Then I tried removing some files but the shell did not let me do anything
bash> rm apache22.tar
bash: fork: Not enough space
bash> pwd
/tmp
bash> vmstat 1
bash: fork: Not... (3 Replies)
Discussion started by: mohtashims
3 Replies
4. Solaris
hi guys..
how to give root permission for particular user
tel me step by step (2 Replies)
Discussion started by: coolboys
2 Replies
5. Solaris
Hi,
I have enabled the Apache webserver on my machime.
Apache root directory is /etc/apache2 and the user in which the web server is configured is webservd,I guess.
I have another user called perf.
Under perf user there is /export/home/perf/v9 directory.
I want to give the OS user of... (3 Replies)
Discussion started by: bikas89
3 Replies
6. AIX
Paging space is 100% full? what step can i take (3 Replies)
Discussion started by: ramraj731
3 Replies
7. UNIX for Dummies Questions & Answers
ANy reasons?
FILESYSTEM not FULL, PERMISSION is 777, but cant write to the filesystem?
any steps to do? reasons for this? (9 Replies)
Discussion started by: kenshinhimura
9 Replies
8. HP-UX
Hi,
I am unable to get the full FS space, as /home is 100% utilized and after deleting unwanted files, its still 100%. After checking the du -sk * | sort -n output and converting it to MBs, the total sizes comes out to be 351 MBs only however the lvol is of 3GB. I don't know where is all the space... (2 Replies)
Discussion started by: Kits
2 Replies
9. Emergency UNIX and Linux Support
Hello,
This is RHEL 5.7. swap is almost full, but I am not sure, what to release and how to release space. This is production server so I would like to try all possible options before reboot.
# top
top - 00:18:26 up 327 days, 7:01, 3 users, load average: 0.16, 0.21, 0.18
Tasks: 782 total, ... (7 Replies)
Discussion started by: solaris_1977
7 Replies
10. UNIX for Beginners Questions & Answers
Hello Team,
Please help me to solve my Problem,
By mistake, I give full permission to /(root) directory. by using the following command "chmod -R 777 /"
after this, the client asks for the password to login via ssh. Before that, I an able to Login without a password.
Please help me to retrieve... (5 Replies)
Discussion started by: Shubham1182
5 Replies
LEARN ABOUT OSX
dispatch_write
dispatch_read(3) BSD Library Functions Manual dispatch_read(3)
NAME
dispatch_read, dispatch_write -- asynchronously read from and write to file descriptors
SYNOPSIS
#include <dispatch/dispatch.h>
void
dispatch_read(int fd, size_t length, dispatch_queue_t queue, void (^handler)(dispatch_data_t data, int error));
void
dispatch_write(int fd, dispatch_data_t data, dispatch_queue_t queue, void (^handler)(dispatch_data_t data, int error)));
DESCRIPTION
The dispatch_read() and dispatch_write() functions asynchronously read from and write to POSIX file descriptors. They can be thought of as
asynchronous, callback-based versions of the fread() and fwrite() functions provided by the standard C library. They are convenience func-
tions based on the dispatch_io_read(3) and dispatch_io_write(3) functions, intended for simple one-shot read or write requests. Multiple
request on the same file desciptor are better handled with the full underlying dispatch I/O channel functions.
BEHAVIOR
The dispatch_read() function schedules an asynchronous read operation on the file descriptor fd. Once the file descriptor is readable, the
system will read as much data as is currently available, up to the specified length, starting at the current file pointer position. The given
handler block will be submitted to queue when the operation completes or an error occurs. The block will be passed a dispatch data object
with the result of the read operation. If an error occurred while reading from the file descriptor, the error parameter to the block will be
set to the appropriate POSIX error code and data will contain any data that could be read successfully. If the file pointer position is at
end-of-file, emtpy data and zero error will be passed to the handler block.
The dispatch_write() function schedules an asynchronous write operation on the file descriptor fd. The system will attempt to write the
entire contents of the provided data object to fd at the current file pointer position. The given handler block will be submitted to queue
when the operation completes or an error occurs. If the write operation completed successfully, the error parameter to the block will be set
to zero, otherwise it will be set to the appropriate POSIX error code and the data parameter will contain any data that could not be written.
CAVEATS
The data object passed to a handler block is released by the system when the block returns. If data is needed outside of the handler block,
it must concatenate, copy, or retain it.
Once an asynchronous read or write operation has been submitted on a file descriptor fd, the system takes control of that file descriptor
until the handler block is executed. During this time the application must not manipulate fd directly, in particular it is only safe to close
fd from the handler block (or after it has returned).
If multiple asynchronous read or write operations are submitted to the same file descriptor, they will be performed in order, but their han-
dlers will only be submitted once all operations have completed and control over the file descriptor has been relinquished. For details on
this and on the interaction with dispatch I/O channels created from the same file descriptor, see FILEDESCRIPTOR OWNERSHIP in
dispatch_io_create(3).
SEE ALSO
dispatch(3), dispatch_data_create(3), dispatch_io_create(3), dispatch_io_read(3), fread(3)
Darwin December 1, 2010 Darwin