Sponsored Content
Operating Systems Linux SuSE Cannot delete no permission file Post 302494875 by jurn on Tuesday 8th of February 2011 06:19:01 PM
Old 02-08-2011
add another -- before the the filename
This will stop the programs from thinking it is another switch argument.
e.g.
Code:
chmod -R 777 -- -e0.7


Last edited by Yogesh Sawant; 02-09-2011 at 07:51 AM.. Reason: added code tags
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

The file permission

there is a directory eg. /home/edp/ , all the files under this directory : 1. the file and directory owner is "user1" , 2. the permission is 644 I want everyone hv permission to overwrite all files and write a new file to it , but I want the file owner and permssion keep unchange , could... (1 Reply)
Discussion started by: ust
1 Replies

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

3. UNIX for Advanced & Expert Users

File Permission

User - sysopr need to convert the output file from Oracle UTL_FILE_DIR using dos2unix command. However, the file owner and the group is belongs to oracle with dba group as follows: -rw-r--r-- 1 oradw dba 22049864 May 23 15:37 transmission*.csv What are the possible methods to... (2 Replies)
Discussion started by: KhawHL
2 Replies

4. UNIX for Dummies Questions & Answers

Find who has permission to delete

All, I am running a script , which has permision as below -r-xr-x--- 1 pmgr ffw 11660 Sep 3 2003 ccln and tring to delete the file in the directory inter (sys212:pct:/>) ll | grep ^d dr-xr-xr-x 32 bin bin 8192 Dec 24 03:24 etc drwxr-xr-x 32... (2 Replies)
Discussion started by: arunkumar_mca
2 Replies

5. Cybersecurity

file permission/acl: 2 users with write access on 1 file...

Hello, i need some help/advice on how to solve a particular problem. these are the users: |name | group | ---------- --------------- |boss | department1 | |assistant | department1 | |employee | department1 | |spy | department2 | this is the... (0 Replies)
Discussion started by: elzalem
0 Replies

6. UNIX for Dummies Questions & Answers

permission on file

i have two user named sourav and jishu. i have created a file named source.txt in sourav. i made another user called shovon. i want to give read write permission of souce.txt for shovon but not for jishu. how can i set permission only for jishu ? (1 Reply)
Discussion started by: sourav_ray
1 Replies

7. Post Here to Contact Site Administrators and Moderators

shouldnt we also have the permission to delete our threads

i think we should also have the permissions to delete our own thread (3 Replies)
Discussion started by: tarunicon
3 Replies

8. Solaris

Delete Permission on Directory

Hi, I have a directory /u01/source. Following are current permission on directory source. oracle@TEST # ls -l source drwxrwxrwx 2 user1 userbi 31232 Apr 8 13:33 EG1 drwxrwxrwx 2 user1 userbi 1024 Apr 8 05:45 E2 drwxrwxrwx 2 user1 userbi 57344 Mar 15 10:22 h5 There is another ... (4 Replies)
Discussion started by: fahdmirza
4 Replies

9. Red Hat

Need Script to ZIP/SAVE & then DELETE Log file & DELETE ZIPS older than 12 months

ENVIROMENT Linux: Fedora Core release 1 (Yarrow) iPlanet: iPlanet-WebServer-Enterprise/6.0SP1 Log Path: /usr/iplanet/servers/https-company/logs I have iPlanet log rotation enabled rotating files on a daily basis. The rotated logs are NOT compressed & are taking up too much space. I... (7 Replies)
Discussion started by: zachs
7 Replies

10. Shell Programming and Scripting

Is rsync --delete on some files without write permission possible?

Hello all, I have a problem with rsync command. From a backup server, I use a command like the one below: rsync -av --delete user@host:/home/user/ /home/backup_user/daily_rotating_backup/ In some folders of the user there are some files on which he has removed his write permission on... (3 Replies)
Discussion started by: freddie50
3 Replies
MARK(1)                                                              [nmh-1.5]                                                             MARK(1)

NAME
mark - manipulate message sequences SYNOPSIS
mark [+folder] [msgs] [-sequence name ...] [-add | -delete] [-list] [-public | -nopublic] [-zero | -nozero] [-version] [-help] DESCRIPTION
The mark command manipulates message sequences by adding or deleting message numbers from folder-specific message sequences, or by listing those sequences and messages. A message sequence is a keyword, just like one of the "reserved" message names, such as "first" or "next". Unlike the "reserved" message names, which have a fixed semantics on a per-folder basis, the semantics of a message sequence may be defined, modified, and removed by the user. Message sequences are folder-specific, e.g., the sequence name "seen" in the context of folder "+inbox" need not have any relation whatsoever to the sequence of the same name in a folder of a different name. Three action switches direct the operation of mark. These switches are mutually exclusive: the last occurrence of any of them overrides any previous occurrence of the other two. The -add switch tells mark to add messages to sequences or to create a new sequence. For each sequence named via the -sequence name argu- ment (which must occur at least once) the messages named via msgs (which defaults to "cur" if no msgs are given), are added to the sequence. The messages to be added need not be absent from the sequence. If the -zero switch is specified, the sequence will be emptied prior to adding the messages. Hence, -add -zero means that each sequence should be initialized to the indicated messages, while -add -nozero means that each sequence should be appended to by the indicated messages. The -delete switch tells mark to delete messages from sequences, and is the dual of -add. For each of the named sequences, the named mes- sages are removed from the sequence. These messages need not be already present in the sequence. If the -zero switch is specified, then all messages in the folder are added to the sequence (first creating the sequence, if necessary) before removing the messages. Hence, -delete -zero means that each sequence should contain all messages except those indicated, while -delete -nozero means that only the indi- cated messages should be removed from each sequence. As expected, the command "mark -sequence foo -delete all" deletes the sequence "foo" from the current folder. When creating or modifying sequences, you can specify the switches -public or -nopublic to force the new or modified sequences to be "pub- lic" or "private". The switch -public indicates that the sequences should be made "public". These sequences will then be readable by all nmh users with permission to read the relevant folders. In contrast, the -nopublic switch indicates that the sequences should be made "private", and will only be accessible by you. If neither of these switches is specified, then existing sequences will maintain their cur- rent status, and new sequences will default to "public" if you have write permission for the relevant folder. Check the mh-sequence(5) man page for more details about the difference between "public" and "private" sequences. The -list switch tells mark to list both the sequences defined for the folder and the messages associated with those sequences. Mark will list the name of each sequence given by -sequence name and the messages associated with that sequence. If the sequence is private, this will also be indicated. If no sequence is specified by the -sequence switch, then all sequences for this folder will be listed. The -zero switch does not affect the operation of -list. The current restrictions on sequences are: o The name used to denote a message sequence must consist of an alphabetic character followed by zero or more alphanumeric characters, and cannot be one of the (reserved) message names "new", "first", "last", "all", "next", or "prev". o Only a certain number of sequences may be defined for a given folder. This number is usually limited to 27 (11 on small systems). (The internal implementation relies on bitmasks, with some bits set aside for internal use.) o Message ranges with user-defined sequence names are restricted to the form "name:n", "name:+n", or "name:-n", and refer to the first or last `n' messages of the sequence `name', respectively. Constructs of the form "name1-name2" are forbidden for user defined sequences. FILES
$HOME/.mh_profile The user profile PROFILE COMPONENTS
Path: To determine the user's nmh directory Current-Folder: To find the default current folder SEE ALSO
flist(1), pick(1), mh-sequence(5) DEFAULTS
`+folder' defaults to the current folder `-add' if -sequence is specified, -list otherwise `msgs' defaults to cur (or all if -list is specified) `-nozero' CONTEXT
If a folder is given, it will become the current folder. HELPFUL HINTS
Use flist to find folders with a given sequence, and "pick sequence -list" to enumerate those messages in the sequence (such as for use by a shell script). MH.6.8 11 June 2012 MARK(1)
All times are GMT -4. The time now is 10:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy