Sponsored Content
Top Forums UNIX for Dummies Questions & Answers problem while deleting a file Post 302120350 by advaitham on Wednesday 6th of June 2007 12:06:52 AM
Old 06-06-2007
Use end-of-options notation

UNIX/Linux has a special notation '--' which indicates end of options. From then on the utility will not or should not interpret the arguments as options. Try
rm -- -f%*lock.clock
 

10 More Discussions You Might Find Interesting

1. Programming

problem deleting date-time stamped file in a directory

I have a number of files of the format filename.xfr_mmddyy_%H%M%S which i get in a specified directory daily. Now i want to search in the specified directory & delete the files which are more than 2 days old .So I use a command find $DIR/backup/* -ctime +2 -exec rm -f {} \; But after executing... (1 Reply)
Discussion started by: dharmesht
1 Replies

2. UNIX for Dummies Questions & Answers

Problem deleting file with special character

I'm having problems deleting a file with a special character and I'm hoping that somebody here can help. The file "-osample1.c" will not remove from my directory. Here is an example of what happens. Any ideas would be appreciated. > ls *sample1* ls: illegal option -- . usage: ls... (2 Replies)
Discussion started by: hart1165
2 Replies

3. UNIX for Dummies Questions & Answers

Problem while Deleting file

All, I am trying to delete a user created file from specified folder. This folder is using for my Team member (i.e, Public folder). For example, $ ls -l total 1336 -rw-rw-r-- 1 g_btha customer 2655 Dec 06 12:35 A_COL_1001 While deleting/moving this file I am getting the following... (3 Replies)
Discussion started by: nvkuriseti
3 Replies

4. UNIX for Dummies Questions & Answers

problem in deleting a file

Hello: I made this mistake on my tru64 machine, I renamed a file from: binary.errlog to binary.errlog(B3) now when im tryign to move or delete the file Im getting: # rm binary.errlog(B3) ksh: syntax error: `(' unexpected 4# mv binary.errlog(B3) log ksh: syntax error: `(' unexpected ... (3 Replies)
Discussion started by: aladdin
3 Replies

5. UNIX for Advanced & Expert Users

problem with deleting a file

hi friends, i need to delete a file named "-vyxx-.0.sdct.txt" i'm unable to use "rm -vyxx-.0.sdct.txt" jus give me your suggesstions thanks in advance (5 Replies)
Discussion started by: rprajendran
5 Replies

6. Shell Programming and Scripting

Problem in deleting lines from the file

Hi All I am not able to delete few line from long file. I have a big file which is of 53998 B in size i want to delete lines starting from 32768 to 53998 and collect remaining file in new file. It is giving exception sed: command garbled: 32768,$countd Please find the sample script... (2 Replies)
Discussion started by: rajeshorpu
2 Replies

7. Shell Programming and Scripting

Problem with deleting

Hi, I have a folder A which contains files 1,2,3... I also have a file xyz under a diff folder B containg the entries 1,2,3... I am trying to compare and delete the nonexisting ones from xyz using the below code: QFILE=/B/xyz cd A ls -1 > /tmp/file1 for fname in `cat $QFILE` do if ... (4 Replies)
Discussion started by: swasid
4 Replies

8. Shell Programming and Scripting

Problem in deleting files

Hi Guys, In one of my folders i have 10000 log files starting with sqlfile..... Iam trying to delete the log files alone from the folder using for loop but i am getting an error ksh: /usr/bin/ls: 0403-027 The parameter list is too long. For loop i used for i in `ls sqlfile*`... (4 Replies)
Discussion started by: mac4rfree
4 Replies

9. UNIX for Advanced & Expert Users

reg problem deleting file

hi, 1. When i am deleting file in the linux machine i am getting below error message. rm text.fil rm: remove regular file `text.fil'? y rm: cannot remove `text.fil': Read-only file system From su also i tried i am getting same error message. 2. Some times the file permissions and user name... (1 Reply)
Discussion started by: coconut.ramu
1 Replies

10. UNIX Desktop Questions & Answers

Problem with deleting .dmp file

Hi, everybody! I have a big problem. I don't understand Unix, but I work as a system administrator, and sometimes I make some data exports and I have to delete old .dmp files, but today I had a mistake, I wrote rm * 909* This is a part of my folder contents in unix before deleting drwxrwxr-x 2... (4 Replies)
Discussion started by: susan12
4 Replies
halockrun(1M)						  System Administration Commands					     halockrun(1M)

NAME
halockrun - run a child program while holding a file lock SYNOPSIS
/usr/cluster/bin/halockrun [-nsv] [-e exitcode] lockfilename prog [args] DESCRIPTION
The halockrun utility provides a convenient means to claim a file lock on a file and run a program while holding that lock. As this utility supports script locking, this utility is useful when programming in scripting languages such as the Bourne shell. See sh(1). halockrun opens the file lockfilename and claims an exclusive mode file lock on the entire file. See fcntl(2) fcntl(2)). Then it runs the program prog with arguments args as a child process and waits for the child process to exit. When the child exits, halockrun releases the lock, and exits with the same exit code with which the child exited. The overall effect is that the child prog is run as a critical section, and that this critical section is well-formed, in that no matter how the child terminates, the lock is released. If the file lockfilename cannot be opened or created, then halockrun prints an error message on stderr and exits with exit code 99. You can run this command in the global zone or in a non-global zone. The command affects only the global or non-global zone in which you issue the command. OPTIONS
The following options are supported: -e exitcode Normally, errors detected by halockrun exit with exit code 99. The -e option provides a means to change this special exit code to a different value. -n The lock should be requested in non-blocking mode: if the lock cannot be granted immediately, halockrun exits immediately, with exit code 1, without running prog. This behavior is not affected by the -e option. Without the -n option, the lock is requested in blocking mode, thus, the halockrun utility blocks waiting for the lock to become available. -s Claim the file lock in shared mode, rather than in exclusive mode. -v Verbose output, on stderr. EXIT STATUS
Errors detected by halockrun itself, such that the child process was never started, cause halockrun to exit with exit code 99. (This exit code value can be changed to a different value using the -e option. See OPTIONS. Otherwise, halockrun exits with the same exit code with which the child exited. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWscu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
fcntl(2), attributes(5) Sun Cluster 3.2 10 Apr 2006 halockrun(1M)
All times are GMT -4. The time now is 02:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy