Sponsored Content
Full Discussion: unable to delete a file
Top Forums UNIX for Dummies Questions & Answers unable to delete a file Post 302098164 by sysgate on Friday 1st of December 2006 04:57:22 AM
Old 12-01-2006
permissions issue ? have you tried "rm -rf" ?
 

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
kits(1) 						      General Commands Manual							   kits(1)

NAME
kits - Generates setld format distribution kits SYNOPSIS
/usr/bin/kits key-file input-path output-path [subset...] OPERANDS
The pathname of the manufacturing key file which describes the product to be kitted. Unless optional subset arguments are specified, all subsets listed in the descriptor section of the key-file are kitted. The pathname which specifies the top of a hierarchy of files. This hierarchy contains the files which are to be kitted into subsets. The name of the directory to be used to store the subset image and data files produced by the command. The names of individual subsets can be specified by optionally listing them on the command line. If they are specified, only those subsets are kitted. The kits program assumes that all other subsets for the product have been kitted and that their images are in the directory specified by output-path. The key file specified must contain descriptors for each of the optional named subsets. DESCRIPTION
The kits command produces subset images, inventories, and control files for an installation using the setld command. You need to know the key file which describes the product to be built, a hierarchy from which the component files to be kitted are to be taken, and a destina- tion directory into which the kit information is to be placed. In the output-path directory, the kits command produces a subset image file for each subset and a product_code.image file listing all the kit's subsets. In the instctrl subdirectory of output-path, kits produces an inventory file and a control file. The optional subset con- trol program for any subset in the kit is transferred to output-path/instctrl. An instctrl directory is created if none existed. RESTRICTIONS
Any subset control programs to be provided with the kit must be located in a directory named scps in the working directory where the kits program is invoked. If no subset control program is found for a subset, an empty one is created. ERRORS
The kits program was unable to find the key-file specified on the command line. The kits program was unable to find the specified input- path. The kits program was unable to find the specified output-path. The kits program cannot create an instctrl directory under output- path. Check that the user has write permission to output-path. One of the NAME, CODE, VERS, MI or ROOT values in the specified key-file is either missing or has a null value. The master inventory file pathname specified in the MI entry of the key-file cannot be found. Verify that the pathname is accessible from the current directory. There are no records in the master inventory file for a subset which is being kitted. Check the master inventory file for correctness of content and format. A subset name specified on the command line does not have a descriptor line in the key-file. Check the spelling of the subset name on the command line. Check the contents of the key-file. The compression option was specified in the key-file and an attempt to compress a subset failed. This should not happen. Run the kits program again. EXAMPLES
Produce a kit using key file ULT400.k in the current directory to package files from the hierarchy /var/kits/input, and place the results in /var/kits/output. kits OAT100.k /var/kits/input /var/kits/output Produce a kit using key file ULT400.k in the current directory to package files from the hierarchy /var/kits/input, and place the results in /var/kits/output, but create only the OATDCB100 subset. kits OAT100.k /var/kits/input /var/kits/output OATDCB100 FILES
Log of subset packaging activity SEE ALSO
invcutter(1), newinv(1), tarsets(1), setld(8) stl_comp(4), stl_ctrl(4), stl_image(4), stl_key(4), stl_mi(4), stl_scp(4) Guide to Preparing Product Kits kits(1)
All times are GMT -4. The time now is 12:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy