01-25-2010
That wasn't my advice. Please read closer the command I suggested.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi guys,
I Have written a script,In that it will call another file which contains the sql quaries.
while wxecuting that I am getting the below exception
01/16|06:28:06:16800: Operating System Error|Failed to open output file
Can anybody help me about this,,Its urgent (0 Replies)
Discussion started by: Anji
0 Replies
2. Solaris
Morning all,
I have a problem with a Sun workstation which is running Solaris 8.
When I attempt to open an application, the executable fails with this message :
"fatal: libcstd.so.1: open failed: No such file or directory"
It was suggested to me that I need to add these patches to fix the... (4 Replies)
Discussion started by: AndyD
4 Replies
3. Solaris
Hi,
I am working with solaris 9 and I want to install perforce on that,so I downloaded the p4v.bin file and try to install it by the command
./p4v
after that it is giving the error---
ld.so.1: ./p4v.bin: fatal: libm.so.2: open failed: No such file or directory
Killed
I am not... (3 Replies)
Discussion started by: smartgupta
3 Replies
4. Solaris
Hi all,
when am rebooting the server (SF v890) we are facing
"open boot diagnostic failed".
Thanks in Adv. (5 Replies)
Discussion started by: arjunreddy3
5 Replies
5. UNIX for Dummies Questions & Answers
Hi everybody...
I have installed qrdesktop(is a tool similar to rdesktop used to access remote desktop) on Ubuntu 8.10.
when i am accessing the remote desktop some of the keyboard keys are not working on remote desktop like up arrow ,down arrow, left, right, delete etc.
the output of tail... (5 Replies)
Discussion started by: lokeshsingla
5 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I have try to ndm to one server to another server. but i am getting this error. what is this error? are files not in source folder?
Source file open failed. Error= 2
Regards,
Balamurgan (1 Reply)
Discussion started by: krbala1985
1 Replies
7. Red Hat
Hi,
# yum --skip-broken -y update
rpmdb: Thread/process 6657/3078387392 failed: Thread died in Berkeley DB library
error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db3 - (-30974)
error: cannot open... (3 Replies)
Discussion started by: sef alislam
3 Replies
8. Solaris
Hey for some reason I think I deleted a critical file for sendmail. I was looking the log file on /var/log/cron for cron, and the file isn't there and I found out the reason why is because I'm missing libssl.so.0.9.7. Im running Solaris 11.
I checked smtp and got the following:
#svcs -xv... (3 Replies)
Discussion started by: picolin
3 Replies
9. UNIX for Beginners Questions & Answers
I just updated my rdesktop to 1.8.3 from source ( on Slackware 11 ) and had troubles with arrow keys/page up/page down not working.
I see this on the console:
ERROR: Failed to open keymap en-us
The fix is a permission change. I initially looked at /usr/share/rdesktop/keymaps and everything... (1 Reply)
Discussion started by: agentrnge
1 Replies
10. Shell Programming and Scripting
Hi, The below commands works fine on serverB
. /etc/profile;
cd /export/home/user2/utils/plugin/
./runme.shHowever, when i run the same commands from serverA it fails
$ ssh -q user2@serverB ". /etc/profile; cd /export/home/user2/utils/plugin; ./runme.sh"Output Error:
Please find the below... (8 Replies)
Discussion started by: mohtashims
8 Replies
LEARN ABOUT FREEBSD
posix_fadvise
POSIX_FADVISE(2) BSD System Calls Manual POSIX_FADVISE(2)
NAME
posix_fadvise -- give advice about use of file data
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <fcntl.h>
int
posix_fadvise(int fd, off_t offset, off_t len, int advice);
DESCRIPTION
The posix_fadvise() system call allows a process to describe to the system its data access behavior for an open file descriptor fd. The
advice covers the data starting at offset offset and continuing for len bytes. If len is zero, all data from offset to the end of the file
is covered.
The behavior is specified by the advice parameter and may be one of:
POSIX_FADV_NORMAL Tells the system to revert to the default data access behavior.
POSIX_FADV_RANDOM Is a hint that file data will be accessed randomly, and prefetching is likely not advantageous.
POSIX_FADV_SEQUENTIAL Tells the system that file data will be accessed sequentially. This currently does nothing as the default behavior
uses heuristics to detect sequential behavior.
POSIX_FADV_WILLNEED Tells the system that the specified data will be accessed in the near future. The system may initiate an asynchronous
read of the data if it is not already present in memory.
POSIX_FADV_DONTNEED Tells the system that the specified data will not be accessed in the near future. The system may decrease the in-mem-
ory priority of clean data within the specified range and future access to this data may require a read operation.
POSIX_FADV_NOREUSE Tells the system that the specified data will only be accessed once and then not reused. The system may decrease the
in-memory priority of data once it has been read or written. Future access to this data may require a read operation.
RETURN VALUES
The posix_fadvise() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to
indicate the error.
ERRORS
The posix_fadvise() system call returns zero on success, and an error on failure:
[EBADF] The fd argument is not a valid file descriptor.
[EINVAL] The advice argument is not valid.
[EINVAL] The offset or len arguments are negative, or offset + len is greater than the maximum file size.
[ENODEV] The fd argument does not refer to a regular file.
[ESPIPE] The fd argument is associated with a pipe or FIFO.
SEE ALSO
madvise(2)
STANDARDS
The posix_fadvise() interface conforms to IEEE Std 1003.1-2001 (``POSIX.1'').
HISTORY
The posix_fadvise() system call first appeared in FreeBSD 9.1.
BSD
January 30, 2014 BSD