10-17-2009
Quote:
Originally Posted by
jlliagre
"kill -9" is never a good advice though, too much cow-boy style.
As I suggested previously, you should first figure out what these processes are and have them stopped gently instead.
Yepee-Ky-yay, Hans.
It's the cdrom directory. He's trying to remove the cd. Why is it never good advice to use -9?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm trying to unmount a file system, but umount says the device is busy. A fuser -c /myfs tells me that nothing on this fs is in use. Any idea?
Oh, and btw, why isn't my signature beeing displayed? Show user's signature is enabled and I have entered one :/ (10 Replies)
Discussion started by: sTorm
10 Replies
2. Solaris
Hi I have placed a CD into the rom and now I can not eject it.
when i type in
eject cdrom i get the follwing error
root@ssdb0009 # eject cdrom
/vol/dev/rdsk/c0t6d0/dp_a0500_solaris_7_and_8_cd: Device busy
Therefore i try and eject it with the -f option (eject -f cdrom) I still get the... (4 Replies)
Discussion started by: dennisca
4 Replies
3. AIX
Now i have a prolem!
I double click on my zip file from cdrom.
System can not read my zip file and i can not eject my cdrom.
How can i manage process and can i end a process
or how can i eject my cdrom?
please have me! thanks (4 Replies)
Discussion started by: leenguyen0101
4 Replies
4. HP-UX
Anyone have any idea why I cannot umount a directory even though fuser shows no process attached to it?
fuser -cu /data/oracle/GMPSHRDM/export
/data/oracle/GMPSHRDM/export:
umount /data/oracle/GMPSHRDM/export
umount: cannot unmount /data/oracle/GMPSHRDM/export : Device busy
umount:... (2 Replies)
Discussion started by: keelba
2 Replies
5. Solaris
Hi,
When I insert a cd to CDROM drive in SF V210 Solaris 10 it took seconds then eject it auto!
How can I solve this issue?
Thanks
Regards :) (8 Replies)
Discussion started by: HishamN
8 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I'm trying to do a sharity mount to mount a terastation network drive.
I'm getting a Device or resource busy message after my mount command. Please see output below...
# /usr/local/sharity3/bin/sharity mount smb://labbackup01/bakup_data /mnt/labbackup01
Device or resource busy.... (2 Replies)
Discussion started by: orahi001
2 Replies
7. Solaris
Hey everyone, I currently have a sparcstation 5, and am trying to run some scripts on it without booting off the hard drive.
Currently I am using a Solaris 8 install cd to boot into single user mode. However, the scripts I have are on a different CD.
What I would like to do is to use the... (6 Replies)
Discussion started by: idlechatter
6 Replies
8. Solaris
The green cdrom light is blinking on our Sun Solaris server. I tried the eject command to eject cdrom:
eject cdrom
cdrom: No such file or directory
bash-2.05# eject
No default media available
bash-2.05# eject cdrom0
cdrom0: No such file or directory
The message log file shows:
Oct 19... (6 Replies)
Discussion started by: agarcia19
6 Replies
9. HP-UX
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
10. UNIX for Beginners Questions & Answers
mount -f nfs 1234:/export/ert /der/fr/ert
mount : /der/fr/ert: device busy
normally I will then do an
fuser filesystem
and kill the pids, which I did.
now if I do an fuser /der/fr/ert
I get the mount point and no pid
> fuser /der/fr/ert
/der/fr/ert:
but it... (1 Reply)
Discussion started by: goya
1 Replies
LEARN ABOUT REDHAT
madvise
MADVISE(2) Linux Programmer's Manual MADVISE(2)
NAME
madvise - give advice about use of memory
SYNOPSIS
#include <sys/mman.h>
int madvise(void *start, size_t length, int advice);
DESCRIPTION
The madvise system call advises the kernel about how to handle paging input/output in the address range beginning at address start and with
size length bytes. It allows an application to tell the kernel how it expects to use some mapped or shared memory areas, so that the kernel
can choose appropriate read-ahead and caching techniques. This call does not influence the semantics of the application (except in the
case of MADV_DONTNEED), but may influence its performance. The kernel is free to ignore the advice.
The advice is indicated in the advice parameter which can be
MADV_NORMAL
No special treatment. This is the default.
MADV_RANDOM
Expect page references in random order. (Hence, read ahead may be less useful than normally.)
MADV_SEQUENTIAL
Expect page references in sequential order. (Hence, pages in the given range can be aggressively read ahead, and may be freed soon
after they are accessed.)
MADV_WILLNEED
Expect access in the near future. (Hence, it might be a good idea to read some pages ahead.)
MADV_DONTNEED
Do not expect access in the near future. (For the time being, the application is finished with the given range, so the kernel can
free resources associated with it.) Subsequent accesses of pages in this range will succeed, but will result either in re-loading
of the memory contents from the underlying mapped file (see mmap) or zero-fill-on-demand pages for mappings without an underlying
file.
RETURN VALUE
On success madvise returns zero. On error, it returns -1 and errno is set appropiately.
ERRORS
EINVAL the value len is negative, start is not page-aligned, advice is not a valid value, or the application is attempting to release
locked or shared pages (with MADV_DONTNEED).
ENOMEM addresses in the specified range are not currently mapped, or are outside the address space of the process.
ENOMEM (for MADV_WILLNEED) Not enough memory - paging in failed.
EIO (for MADV_WILLNEED) Paging in this area would exceed the process's maximum resident set size.
EBADF the map exists, but the area maps something that isn't a file.
EAGAIN a kernel resource was temporarily unavailable.
LINUX NOTES
The current Linux implementation (2.4.0) views this system call more as a command than as advice and hence may return an error when it can-
not do what it usually would do in response to this advice. (See the ERRORS description above.) This is nonstandard behaviour.
The Linux implementation requires that the address start be page-aligned, and allows length to be zero. If there are some parts of the
specified address range that are not mapped, the Linux version of madvise ignores them and applies the call to the rest (but returns ENOMEM
from the system call, as it should).
HISTORY
The madvise function first appeared in 4.4BSD.
CONFORMING TO
POSIX.1b (POSIX.4). POSIX 1003.1-2001 describes posix_madvise with constants POSIX_MADV_NORMAL, etc., with a behaviour close to that
described here. There is a similar posix_fadvise for file access.
SEE ALSO
getrlimit(2), mmap(2), mincore(2), mprotect(2), msync(2), munmap(2)
Linux 2.4.5 2001-06-10 MADVISE(2)