Sponsored Content
Full Discussion: permission 400
Operating Systems Linux Red Hat permission 400 Post 302373728 by _val_ on Saturday 21st of November 2009 03:00:22 PM
Old 11-21-2009
Quote:
Originally Posted by mark54g
if you really want root to do nothing to it, chattr -i

Then nobody will be able to do anything to the file to modify it until the immutable flag is removed.
A little note. chattr which stands for (change attribute) should be defined as follows:
Code:
chattr +i filename

In this case you won't be able to remove the file(unless you change it to -i) even if your root.
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

connect to as-400 system

it's possible connect to as-400 system to extract file from server and calculate the data (parse the file)???? if possible , how make the operation ??? how shell language /type i use ??? tanks (0 Replies)
Discussion started by: ZINGARO
0 Replies

2. AIX

IBM AIX on AS/400 Systems

Sry for my beginner question. I didn't find a list with all supported server types for an AIX 5.3 installation. Unfortunately ibm.com page has problems with the sign in so I can't ask in the ibm foum. Will AIX 5.3 run on a 9402, 9404 or 9406 system? Thanks for your help. (3 Replies)
Discussion started by: analyzer
3 Replies

3. Solaris

apache ErrorDocument 400 /cgi-bin/400.cgi

Hi All, Sorry if the question is trivial for you but, I am new to Apache (2.0.63) and am trying to figure out how to display my 400.cgi. Here is what I have in httpd.conf servername testing DocumentRoot "/usr/local/apache2/htdocs" ErrorDocument 400 /cgi-bin/badrequest-400.cgi Here is... (0 Replies)
Discussion started by: afadaghi
0 Replies

4. UNIX for Dummies Questions & Answers

AS/400

hi everyone,,, Can anybody tell me that whether the AS/400 is an "operating system" or a "Server" ? thanks in advance.... please if possible reply urgently,,,i am waiting..... (8 Replies)
Discussion started by: kunalpatil09
8 Replies

5. UNIX for Dummies Questions & Answers

AS/400

Hi everybody,,,, This is kunal here, I am very new to as/400 and recently started working on it in one of IT company....I am planning to have Certification exam of AS/400. Can anybody please send me the links of different sites where I can have study material of AS/400 and also the details... (1 Reply)
Discussion started by: kunalpatil09
1 Replies

6. AIX

AS/400

Hi everybody, I am learning AS/400 and working on it as a System Administrator. Can anybody please suggest me the best blog site for AS/400....just like Unix.com for Linux / Unix administrator. So that I can get all my answers related to AS/400... thanks in advance, kunal patil :) (0 Replies)
Discussion started by: kunalpatil09
0 Replies

7. UNIX for Dummies Questions & Answers

First 400,000 lines?

Hi, I need to C&P the first 400,000 lines of a log file into a compressed file using Putty. I already tried emailing myself using mailx (didnt send) and used head -400000 access_log > /tmp/access_log to move the relevant lines into it's own file. And when I tried increasing the scroll back max... (2 Replies)
Discussion started by: Mbohmer
2 Replies

8. Shell Programming and Scripting

Wants to create 3 users in 400 servers

I wants to create 3 users and set password for the users in 400 servers. I can run this script without error. If wants to set the password in the same command it is not working. Like that i have to create 3 users #!/usr/bin/ksh for server in `cat /tmp/servers` do echo "servername =... (5 Replies)
Discussion started by: G0kulakrishnan
5 Replies

9. Shell Programming and Scripting

How AS 400 sorting data?

Hi Gurus, I have a requests to sort data based on AS 400 sorting order. below is example: the data is sorted by ascending order. could anybody explain how AS 400 sort data? IMM00007 07918607 1242 423 (3 Replies)
Discussion started by: green_k
3 Replies
CHATTR(1)						      General Commands Manual							 CHATTR(1)

NAME
chattr - change file attributes on a Linux file system SYNOPSIS
chattr [ -RVf ] [ -v version ] [ mode ] files... DESCRIPTION
chattr changes the file attributes on a Linux file system. The format of a symbolic mode is +-=[acdeijstuACDST]. The operator `+' causes the selected attributes to be added to the existing attributes of the files; `-' causes them to be removed; and `=' causes them to be the only attributes that the files have. The letters `acdeijstuACDST' select the new attributes for the files: append only (a), compressed (c), no dump (d), extent format (e), immutable (i), data journalling (j), secure deletion (s), no tail-merging (t), undeletable (u), no atime updates (A), no copy on write (C), synchronous directory updates (D), synchronous updates (S), and top of directory hierarchy (T). The following attributes are read-only, and may be listed by lsattr(1) but not modified by chattr: huge file (h), compression error (E), indexed directory (I), compression raw access (X), and compressed dirty file (Z). OPTIONS
-R Recursively change attributes of directories and their contents. -V Be verbose with chattr's output and print the program version. -f Suppress most error messages. -v version Set the file's version/generation number. ATTRIBUTES
When a file with the 'A' attribute set is accessed, its atime record is not modified. This avoids a certain amount of disk I/O for laptop systems. A file with the `a' attribute set can only be open in append mode for writing. Only the superuser or a process possessing the CAP_LINUX_IMMUTABLE capability can set or clear this attribute. A file with the `c' attribute set is automatically compressed on the disk by the kernel. A read from this file returns uncompressed data. A write to this file compresses data before storing them on the disk. Note: please make sure to read the bugs and limitations section at the end of this document. A file with the 'C' attribute set will not be subject to copy-on-write updates. This flag is only supported on file systems which perform copy-on-write. (Note: For btrfs, the 'C' flag should be set on new or empty files. If it is set on a file which already has data blocks, it is undefined when the blocks assigned to the file will be fully stable. If the 'C' flag is set on a directory, it will have no effect on the directory, but new files created in that directory will the No_COW attribute.) When a directory with the `D' attribute set is modified, the changes are written synchronously on the disk; this is equivalent to the `dirsync' mount option applied to a subset of the files. A file with the `d' attribute set is not candidate for backup when the dump(8) program is run. The 'E' attribute is used by the experimental compression patches to indicate that a compressed file has a compression error. It may not be set or reset using chattr(1), although it can be displayed by lsattr(1). The 'e' attribute indicates that the file is using extents for mapping the blocks on disk. It may not be removed using chattr(1). The 'I' attribute is used by the htree code to indicate that a directory is being indexed using hashed trees. It may not be set or reset using chattr(1), although it can be displayed by lsattr(1). The 'h' attribute indicates the file is storing its blocks in units of the filesystem blocksize instead of in units of sectors, and means that the file is (or at one time was) larger than 2TB. It may not be set or reset using chattr(1), although it can be displayed by lsattr(1). A file with the `i' attribute cannot be modified: it cannot be deleted or renamed, no link can be created to this file and no data can be written to the file. Only the superuser or a process possessing the CAP_LINUX_IMMUTABLE capability can set or clear this attribute. A file with the `j' attribute has all of its data written to the ext3 journal before being written to the file itself, if the filesystem is mounted with the "data=ordered" or "data=writeback" options. When the filesystem is mounted with the "data=journal" option all file data is already journalled and this attribute has no effect. Only the superuser or a process possessing the CAP_SYS_RESOURCE capability can set or clear this attribute. When a file with the `s' attribute set is deleted, its blocks are zeroed and written back to the disk. Note: please make sure to read the bugs and limitations section at the end of this document. When a file with the `S' attribute set is modified, the changes are written synchronously on the disk; this is equivalent to the `sync' mount option applied to a subset of the files. A directory with the 'T' attribute will be deemed to be the top of directory hierarchies for the purposes of the Orlov block allocator. This is a hint to the block allocator used by ext3 and ext4 that the subdirectories under this directory are not related, and thus should be spread apart for allocation purposes. For example it is a very good idea to set the 'T' attribute on the /home directory, so that /home/john and /home/mary are placed into separate block groups. For directories where this attribute is not set, the Orlov block alloca- tor will try to group subdirectories closer together where possible. A file with the 't' attribute will not have a partial block fragment at the end of the file merged with other files (for those filesystems which support tail-merging). This is necessary for applications such as LILO which read the filesystem directly, and which don't under- stand tail-merged files. Note: As of this writing, the ext2 or ext3 filesystems do not (yet, except in very experimental patches) support tail-merging. When a file with the `u' attribute set is deleted, its contents are saved. This allows the user to ask for its undeletion. Note: please make sure to read the bugs and limitations section at the end of this document. The 'X' attribute is used by the experimental compression patches to indicate that a raw contents of a compressed file can be accessed directly. It currently may not be set or reset using chattr(1), although it can be displayed by lsattr(1). The 'Z' attribute is used by the experimental compression patches to indicate a compressed file is dirty. It may not be set or reset using chattr(1), although it can be displayed by lsattr(1). AUTHOR
chattr was written by Remy Card <Remy.Card@linux.org>. It is currently being maintained by Theodore Ts'o <tytso@alum.mit.edu>. BUGS AND LIMITATIONS
The `c', 's', and `u' attributes are not honored by the ext2, ext3, and ext4 filesystems as implemented in the current mainline Linux ker- nels. The `j' option is only useful if the filesystem is mounted as ext3. The `D' option is only useful on Linux kernel 2.5.19 and later. AVAILABILITY
chattr is part of the e2fsprogs package and is available from http://e2fsprogs.sourceforge.net. SEE ALSO
lsattr(1) E2fsprogs version 1.42.9 December 2013 CHATTR(1)

Featured Tech Videos

All times are GMT -4. The time now is 08:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy