09-14-2009
I see.
Seems like I might have made a mistake in when popping/pushing directories around.
Well, it's a bit too late to backtrack & pinpoint now. I might as well stick to full directory paths & use 'for' loops to be safer.
Thanks!
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm trying to delete lines from a large text file using VI.
Every line that I am wanting to delete start with 'S' - all others do not. (A list of users)
I've tried using * but doesn't seem to like it...any ideas...
Doesn't have to be VI - but I'm better with VI than sed/awk. (8 Replies)
Discussion started by: peter.herlihy
8 Replies
2. UNIX for Dummies Questions & Answers
when writing a shell script (bourne) and using a unix command like 'ls' is there anything special you need to do to use a wildcard (like *)? (3 Replies)
Discussion started by: benu302000
3 Replies
3. UNIX for Dummies Questions & Answers
ok, I'm trying to write a script file that lists files with specific elements in the name into a txt file, it looks like this
ls s*.dat > file_names.txt
can't figure out whats wrong with that line, any ideas?
thanks in advance (10 Replies)
Discussion started by: benu302000
10 Replies
4. Shell Programming and Scripting
Hi all,
This is my first message in this forum.
I'd like to know if there is a nice way to get the complete path from a symbolic link.
Example:
When I do a ls -ltr I see this output.
lrwxr-xr-x 1 mmmm users 66 Sep 4 09:58 LINK_SEND ->... (4 Replies)
Discussion started by: rodrimuino
4 Replies
5. UNIX for Dummies Questions & Answers
Hi All
Please excuse another straightforward question. When creating a tar archive from a directory I am attempting to use wildcards to eliminate certain filetypes (otherwise the archive gets too large). So I am looking for something along these lines.
tar -cf archive.tar * <minus all *.rst... (5 Replies)
Discussion started by: C3000
5 Replies
6. UNIX for Advanced & Expert Users
These 2 websites do a GREAT job of explaining different types of wildcards. I learned about the categories of characters which I never knew about at all.
GNU/Linux Command-Line Tools Guide - Wildcards
GREP (1 Reply)
Discussion started by: cokedude
1 Replies
7. Solaris
When loooking at files in a directory using ls, how can I tell if I have a hard link or soft link? (11 Replies)
Discussion started by: Harleyrci
11 Replies
8. AIX
Hi
I'm logged in as root in an aix box
Which command will list all the soft links and hard links present in the server ? (2 Replies)
Discussion started by: newtoaixos
2 Replies
LEARN ABOUT ULTRIX
sticky
sticky(8) System Manager's Manual sticky(8)
Name
sticky - executable files with persistent text
Description
The sticky bit (file mode bit 01000), is used to indicate special treatment for certain executable files and directories.
While the sticky bit, mode 01000 is set on a sharable executable file, the text of that file will not be removed from the system swap area.
Thus the file does not have to be fetched from the file system upon each execution. As long as a copy remains in the swap area, the origi-
nal text cannot be overwritten in the file system, nor can the file be deleted. Directory entries can be removed so long as one link
remains.
Sharable files are made by the and options of
To replace a sticky file that has been used, clear the sticky bit with and execute the old program to flush the swapped copy. This can be
done safely even if others are using it. Overwrite the sticky file. If the file is being executed by any process, writing will be pre-
vented. It suffices to simply remove the file and then rewrite it, being careful to reset the owner and mode with and Set the sticky bit
again.
A directory whose sticky bit is set becomes an append-only directory, or, more accurately, a directory in which the deletion of files is
restricted. A file in a sticky directory may only be removed or renamed by a user if the user has write permission for the directory and
the user is the owner of the file, the owner of the directory, or the superuser. This feature is usefully applied to directories such as
which must be publicly writeable but should deny users the license to arbitrarily delete or rename each others' files.
Restrictions
Only the superuser can set the sticky bit.
See Also
chmod(2)
RISC sticky(8)