Sponsored Content
Full Discussion: unable to delete a file
Top Forums UNIX for Dummies Questions & Answers unable to delete a file Post 302098187 by arunkumar_mca on Friday 1st of December 2006 07:17:03 AM
Old 12-01-2006
Hi grial....

Hope i will not be a permision problem since when i tried to delete it . It showing that not avalaible if it is a permision problem it would some other then that....Smilie




Please let me know what to do.

Thanks in advance.
Arun kumar.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

unable to delete file for permission problem

Hi, We are facing problem to delete some logfiles. Explaing with example for clear understanding : we have 2 accounts : prdpqrs (application account) & prodxyz (admin account - not root). Both of them are in same group called 'release' While prodxyz is trying to remove a file owned by... (4 Replies)
Discussion started by: sabyasm
4 Replies

2. UNIX for Dummies Questions & Answers

Unable to delete files

I have more than 1 million files (No directories). rm -rf * did not work. How do i delete all these files at a stretch in a single command? (9 Replies)
Discussion started by: sydney2008
9 Replies

3. 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

4. UNIX for Advanced & Expert Users

Unable to delete an open file

I am working on a unix server. I killed all the processes with my id on the machine. After that I tried to delete a file, I got an error:- file not removed.Text File busy. Deletion of directory prompted:- Directory not empty. Can anyone help me regarding this...??? Thanks, Vikas (11 Replies)
Discussion started by: vikasrout
11 Replies

5. Shell Programming and Scripting

Rsync help - unable to delete the Source file

Hi All, I am facing problem deleting Source while using the rsync command. rsync --include=*`date --date="-1 day" \+\%Y\%m\%d`* --include=*`date +\%Y\%m\%d`* --exclude=* --delete-after -auvb -e ssh USER@SERVER:SOURCE DESTINATION However the sync happens but not the deletion of the source... (1 Reply)
Discussion started by: amitkhiare
1 Replies

6. Shell Programming and Scripting

Unable to overwrite but can delete file

I'm debugging a ksh script written by someone else that does the following: It runs a command and redirects stdout to a file called dberror that already exists using ">". This command fails with the following error: The file access permissions do not allow the specified action. dberror:... (1 Reply)
Discussion started by: savage66
1 Replies

7. Solaris

Unable to delete directory even with 777 perm

Hi, I have an 'empty' directory 'tmp' of which I am the owner and 777 permission. But when I try to delete the directory using rmdir or rm command, it gives error. Command prompt snapshot: => uname SunOS ... (4 Replies)
Discussion started by: platinum81
4 Replies

8. HP-UX

Unable to delete iscsi target

Hi Please can someone give me a hint on this, when I list the targets, I see two o them: #iscsiutil -p Operational Target Information ------------------------------ Target # 1 ----------- Target Name : iqn.1992-08.com.netapp:sn.142241859 Target Alias ... (2 Replies)
Discussion started by: fretagi
2 Replies

9. AIX

Unable to delete files

heapdump716960.1416296627.txt heapdump716960.1416299494.txt heapdump716960.1416302375.txt trying to delete the above files root@atec:/oratec/prodcomn/temp>rm heap*.*.txt ksh: /usr/bin/rm: 0403-027 The parameter list is too long. root@atec:/oratec/prodcomn/temp>rm heap*.txt... (2 Replies)
Discussion started by: filosophizer
2 Replies

10. Shell Programming and Scripting

Tried many options but unable to delete blank lines from text file

Hi, I tried the following options but was unable to delete blank lines from file Input file = temp.hash.txt temp.hash.txt content 90 0 89.56 0 0 57575.4544 56.89 (9 Replies)
Discussion started by: uuuunnnn
9 Replies
tcmodchain(1)						      General Commands Manual						     tcmodchain(1)

NAME
tcmodchain - Query compatibily of transcode modules chains. SYNOPSIS
tcmodchain [ -m path ] [ -C ] [ -L ] [ -d verbosity ] [ -v ] module1 module2 COPYRIGHT
tcmodchain is Copyright (C) by Transcode Team DESCRIPTION
tcmodchain allow to inspect transcode(1) modules, as well as it's companion, tcmodinfo(1). While tcmodinfo(1) focus on single modules, tcmodchain is intended to help in exploring/experimenting module interactions. OPTIONS
-m path Look in Path instead of the compiled-in module path while trying to load a module. -C Enable check mode. In check mode tcmodchain expects exactly two module identifiers. tcmodchain will check compatibilty between two given modules. Result will be logged out or not depending of verbosity level. Anyway, if two modules are compatible, tcmodchain will exit succes- fully; otherwise, tcmodchain will exit with error. see RETURN VALUES below. -L Enable list mode. In list mode tcmodchain expects exactly two module identifiers, exactly one of which containing a wildcard. tcmodchain will inspect all avalaible installed modules matching the wildcard and will print out module names that are compatible with the other given one. if at least one compatible module is found, tcmodchain will exit succesfully; otherwise, tcmodchain will exit with error. see RETURN VALUES below. -d verbosity Specify the verbosiness level to use, like transcode does. Default value is 1 (TC_INFO verbosiness). -v Print version information and exit. MODULE IDENTIFIERS
tcmodchain identifies modules using a type:name naming scheme. Currently, as in transcode 1.1.0, only encode and multiplex module types are supported. name can refer to the name of any avalaible transcode modules, using the same rules of tcmodinfo(1) -i option. The wildcard character * is supported in the name section of module identifier. Wildcard meaning is `any of avalaible modules' and is honoured only when list mode (-L option) is used. Using wildcard character for both module identifiers will lead to an error. EXAMPLES
$ tcmodchain -C encode:null multiplex:null -d 1 [encode_null.so] v0.0.3 (2005-06-05) null (fake) A/V encoder [multiplex_null.so] v0.0.2 (2005-12-29) discard each encoded frame [tcmodchain] encode:null | multiplex:null [OK] [tcmodchain] module chain OK $ tcmodchain -L 'encode:*' multiplex:null copy faac lame lzo null x264 xvid PLEASE NOTE that output of this example may vary depending of your installation. At least null and copy modules will be showed on your output. $ tcmodchain -L encode:null 'multiplex:*' avi null raw y4m RETURN VALUES
tcmodchain uses following return values: 0 successfull 1 bad parameter or command line option 2 error while (un)loading a module 3 given module pair isn't compatible 4 error while looking for module(s) AUTHORS
tcmodchain was written by Francesco Romani <fromani@gmail.com> with contributions from many others. See AUTHORS for details. SEE ALSO
transcode(1) tcmodinfo(1) tcmodchain(1) 5 January 2006 tcmodchain(1)
All times are GMT -4. The time now is 05:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy