Sponsored Content
Top Forums UNIX for Advanced & Expert Users Unable to delete an open file Post 302298906 by davf on Wednesday 18th of March 2009 10:22:08 PM
Old 03-18-2009
vikasrout,

If you use fuser with the -u option it will tell you the id of the process locking the file, and the user who owns the process -

fuser -u filename

Regards,
davf
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

unable to delete a file

Hi .. I am trying to deleta a file but i cant do the error i get is rm: hs_pdref_custom_dict_PG1_out_76_out non-existent but when i do ls it is listing the in the directory ... please find the filed below.... -rw-r----- 1 tsta107 users 118011030 Dec 1 04:07... (13 Replies)
Discussion started by: arunkumar_mca
13 Replies

2. UNIX for Dummies Questions & Answers

SP2-0310 unable to open file

Hi , We are running Oracle 8.1.7 on HP-UX B.11.00. Recently we have upgraded Oracle from 8.0.6. to 8.1.7. Almost all the shell script we use has the Sqlplus as sqlplus -s @/apps/prod/sql/xxxx.sql > /apps/prod/log/xxxx.out . However we receive the error SP2-0310: unable to open file... (2 Replies)
Discussion started by: guru_2007
2 Replies

3. UNIX for Dummies Questions & Answers

Unable to open .sql file

Hi , I am running Oracle 8.1.7 on HP-UX B.11.00. Recently I have upgraded Oracle from 8.0.6. to 8.1.7. Almost all the shell script has the Sqlplus as sqlplus -s @/apps/prod/sql/xxxx.sql > /apps/prod/log/xxxx.out . However I receive the error SP2-0310: unable to open file... (2 Replies)
Discussion started by: Ananth.p
2 Replies

4. Solaris

unable to open a .log(4MB) file in vi

am unable to open a .log file which is 4MB size. (18 Replies)
Discussion started by: venkatramana
18 Replies

5. Windows & DOS: Issues & Discussions

Unable to delete a file through SAMBA

We have AIX box with a share. We have a Windows 2000 server with a mapped drive to this share. We were able to create and delete files inside the mapped drive. I removed the map. Changed it to a test share. Removed that map. Added it back to teh original share. However, now we can... (3 Replies)
Discussion started by: mcubitt
3 Replies

6. UNIX for Dummies Questions & Answers

delete open file

hi, I have a little problem. I deleted a file, which was opened in vim editor. it was bad idea... now "df" still display same space. I kill process vim, but maybe file was controlled or opened by another application. Is any eventuallity to find which process has lock file? Command "ps -ax"... (2 Replies)
Discussion started by: delonism
2 Replies

7. Shell Programming and Scripting

PCC-F-NOERRFILE, unable to open error message file

Hi, I was compiling few C programs in the unix server and getting the following error message rm: /home/a0xxx28/AVT/SEEDLIBRARYDB/LIB/*.a non-existent proc MODE=ANSI CODE=ANSI_C INCLUDE=/home/a0xxx28/PVT/SEEDLIBRARYDB/INCLUDE INCLUDE=/home/a0xxx28/PVT/SEEDLIBRARY/INCLUDE ... (1 Reply)
Discussion started by: kavithakuttyk
1 Replies

8. Red Hat

unable to open / create any file in vi

Hi, I am unable to create/open any file in vi editor for normal user, though using root I am able to create/open any file, using redhat 5.5, example vi test it showing nothing after entering command (9 Replies)
Discussion started by: manoj.solaris
9 Replies

9. Shell Programming and Scripting

Unable to open a file in perl

Not able to open a file using this code why not? use strict; use warnings; my $file = "verInfo.txt"; unless(open FILE, $file) { # Die with error message # if we can't open it. die "\nUnable to open $file\n"; } my $line = <FILE>; print $line; close FILE; (7 Replies)
Discussion started by: srijith
7 Replies

10. UNIX for Beginners Questions & Answers

Unable to open input kickstart file curl#37

Hi, Getting the below error while installing from ks.cfg unable to open input kickstart file curl#37 Couldn't open file /tmp/swappart Here am trying to include /tmp/swappart file from pre section under disks and partition section. Dont know where exactly am doing wrong My kickstart file... (3 Replies)
Discussion started by: Sumanthsv
3 Replies
FUSER(P)						     POSIX Programmer's Manual							  FUSER(P)

NAME
fuser - list process IDs of all processes that have one or more files open SYNOPSIS
fuser [ -cfu ] file ... DESCRIPTION
The fuser utility shall write to standard output the process IDs of processes running on the local system that have one or more named files open. For block special devices, all processes using any file on that device are listed. The fuser utility shall write to standard error additional information about the named files indicating how the file is being used. Any output for processes running on remote systems that have a named file open is unspecified. A user may need appropriate privilege to invoke the fuser utility. OPTIONS
The fuser utility shall conform to the Base Definitions volume of IEEE Std 1003.1-2001, Section 12.2, Utility Syntax Guidelines. The following options shall be supported: -c The file is treated as a mount point and the utility shall report on any files open in the file system. -f The report shall be only for the named files. -u The user name, in parentheses, associated with each process ID written to standard output shall be written to standard error. OPERANDS
The following operand shall be supported: file A pathname on which the file or file system is to be reported. STDIN
Not used. INPUT FILES
The user database. ENVIRONMENT VARIABLES
The following environment variables shall affect the execution of fuser: LANG Provide a default value for the internationalization variables that are unset or null. (See the Base Definitions volume of IEEE Std 1003.1-2001, Section 8.2, Internationalization Variables for the precedence of internationalization variables used to determine the values of locale categories.) LC_ALL If set to a non-empty string value, override the values of all the other internationalization variables. LC_CTYPE Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments). LC_MESSAGES Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error. NLSPATH Determine the location of message catalogs for the processing of LC_MESSAGES . ASYNCHRONOUS EVENTS
Default. STDOUT
The fuser utility shall write the process ID for each process using each file given as an operand to standard output in the following for- mat: "%d", <process_id> STDERR
The fuser utility shall write diagnostic messages to standard error. The fuser utility also shall write the following to standard error: * The pathname of each named file is written followed immediately by a colon. * For each process ID written to standard output, the character 'c' shall be written to standard error if the process is using the file as its current directory and the character 'r' shall be written to standard error if the process is using the file as its root directory. Implementations may write other alphabetic characters to indicate other uses of files. * When the -u option is specified, characters indicating the use of the file shall be followed immediately by the user name, in parenthe- ses, corresponding to the process' real user ID. If the user name cannot be resolved from the process' real user ID, the process' real user ID shall be written instead of the user name. When standard output and standard error are directed to the same file, the output shall be interleaved so that the filename appears at the start of each line, followed by the process ID and characters indicating the use of the file. Then, if the -u option is specified, the user name or user ID for each process using that file shall be written. A <newline> shall be written to standard error after the last output described above for each file operand. OUTPUT FILES
None. EXTENDED DESCRIPTION
None. EXIT STATUS
The following exit values shall be returned: 0 Successful completion. >0 An error occurred. CONSEQUENCES OF ERRORS
Default. The following sections are informative. APPLICATION USAGE
None. EXAMPLES
The command: fuser -fu . writes to standard output the process IDs of processes that are using the current directory and writes to standard error an indication of how those processes are using the directory and the user names associated with the processes that are using the current directory. RATIONALE
The definition of the fuser utility follows existing practice. FUTURE DIRECTIONS
None. SEE ALSO
None. COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technol- ogy -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html . IEEE
/The Open Group 2003 FUSER(P)
All times are GMT -4. The time now is 11:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy