Can anyone help explain the "s" in the below permissions example. I was reading about the "sticky bit" (t) but I am a little confused.
On file "test"
wolf% chmod 4777 test
wolf% ls -l
total 4
drwx------ 2 john staff 512 Mar 19 21:34 nsmail
-rwsrwxrwx 1 john staff ... (2 Replies)
Hi everyone, I'm looking for some information concerning Unix permissions. I am new to Unix and am doing research for a graduate class. Given the permissions below, can anyone give me five unique exploits that would be available to a hacker/cracker given this configuaration?
-rw-rw-rw- 1... (1 Reply)
I saved a perl code in xemacs. I used an xterminal to execute it but unix said that I don't have permission. I saved the files in my home directory. How do I change the permission. This is hat unix said:
-ksh: ./names.pl: cannot execute (5 Replies)
Hey,
We've got quite a strange problem on our hands here. We are running an HP 9000/800 B.11.00.
I've just created a new group in /etc/group which i called, let's say newgroup . Then I added 4 users to the group, namely user1, user2, user3, user4 . The command grpchk shows no strange things... (4 Replies)
Hi,
I am a Unix Admin. I have to give the permissions to a user for creating new file in a directory in HP-Ux 11.11 system since he cannot able to create a new file in the directory.
Thanks in advance.
Mike (3 Replies)
My /tmp is set with the following permissions (777) and a 't' at the end.
My umask is set to 022.
When I create a directory under /tmp (tmp/xx) it gets created as 755
as expected.
Yet when I create a file within that directory (/tmp/xx/yy) the permissions
are not 755 they are 644.
... (1 Reply)
Hi, I am creating a ksh script to search for a string of text inside files within a directory tree. Some of these file are going to be read/execute only. I know to use chmod to change the permissions of the file, but I want to preserve the original permissions after writing to the file. How can I... (3 Replies)
Hi,
I have noticed that on my Linux box there is a nice feature which make it impossible for specified member (owner, group or other) to have an given access if a member from which we would expect it more don't have that access.
So it is impossible to read file by all if others have set read... (3 Replies)
Discussion started by: DavidMax
3 Replies
LEARN ABOUT MOJAVE
sortm
SORTM(1) [nmh-1.5] SORTM(1)NAME
sortm - sort messages
SYNOPSIS
sortm [+folder] [msgs] [-datefield field] [-textfield field] [-notextfield] [-limit days] [-nolimit] [-verbose | -noverbose] [-version]
[-help]
DESCRIPTION
Sortm sorts the specified messages in the named folder according to the chronological order of the "Date:" field of each message.
The -verbose switch directs sortm to tell the user the general actions that it is taking to place the folder in sorted order.
The -datefield field switch tells sortm the name of the field to use when making the date comparison. If the user has a special field in
each message, such as "BB-Posted:" or "Delivery-Date:", then the -datefield switch can be used to direct sortm which field to examine.
The -textfield field switch causes sortm to sort messages by the specified text field. If this field is "subject", any leading "re:" is
stripped off. In any case, all characters except letters and numbers are stripped and the resulting strings are sorted datefield-major,
textfield-minor, using a case insensitive comparison.
With -textfield field, if -limit days is specified, messages with similar textfields that are dated within `days' of each other appear
together. Specifying -nolimit makes the limit infinity. With -limit 0, the sort is instead made textfield-major, date-minor.
For example, to order a folder by date-major, subject-minor, use:
sortm -textfield subject +folder
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 folder(1)DEFAULTS
`+folder' defaults to the current folder
`msgs"'defaultstoall"
`-datefield' defaults to date
`-notextfield'
`-noverbose'
`-nolimit'
CONTEXT
If a folder is given, it will become the current folder. If the current message is moved, sortm
will preserve its status as current.
HISTORY
Timezones used to be ignored when comparing dates: they aren't any more.
Messages which were in the folder, but not specified by `msgs', used to be moved to the end of the folder; now such messages are left
untouched.
Sortm sometimes did not preserve the message numbering in a folder (e.g., messages 1, 3, and 5, might have been renumbered to 1, 2, 3 after
sorting). This was a bug, and has been fixed. To compress the message numbering in a folder, use "folder -pack" as always.
BUGS
If sortm encounters a message without a date-field, or if the message has a date-field that sortm cannot parse, then sortm attempts to keep
the message in the same relative position. This does not always work. For instance, if the first message encountered lacks a date which
can be parsed, then it will usually be placed at the end of the messages being sorted.
When sortm complains about a message which it can't temporally order, it complains about the message number prior to sorting. It should
indicate what the message number will be after sorting.
MH.6.8 11 June 2012 SORTM(1)