09-26-2011
set a umask value in for the user that creates the logs, then they will be created with the permissions you specify instead of what im guessing is your system default.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Does any one now if you can change permissions on a linked file with out completely removing it and then relinking it? (2 Replies)
Discussion started by: moviestud80
2 Replies
2. Shell Programming and Scripting
I want to do just what the title says. Here's why:
I am adapting a script that backups to a mount. In the script it has a catch where if the drive isn't RW then it unmounts and attempts to remount RW.
# attempt to remount the RW mount point as RW; else abort
$MOUNT -o remount,rw... (3 Replies)
Discussion started by: Movomito
3 Replies
3. UNIX for Dummies Questions & Answers
Hi,
Within a SQL file i am calling 5 shell scripts in back ground and redirecting their outputs to different log files in a specific directory.
Now when I observed is, the log files are created with different permissions even though i did not do any thing specific.
For example in... (3 Replies)
Discussion started by: steria_learner
3 Replies
4. Shell Programming and Scripting
Hi All,
I am completely stuck here.
I have a set of files (with names A.txt, B.txt until L.txt) which contain words like these:
computer
random access memory
computer networking
mouse
terminal
windows
All the files from A.txt to L.txt have the same format i.e. complete words in... (2 Replies)
Discussion started by: shoaibjameel123
2 Replies
5. UNIX for Dummies Questions & Answers
Hi,
If User1, User2 and User3 are in the same group. User1 should not be able to view the files of User2 and User3. But User2 and User3 should be able to view all files.
How to set permission for this.
Please help.
Thanks,
Priya. (1 Reply)
Discussion started by: banupriyat
1 Replies
6. Red Hat
Hello All,
I have an application that creates the log files and they created with 600 permissions instead of 644(default). How can I set the permissions so that files can be created with 644. I looked into the /etc/profile for the umask settings and it is set 002(if UID>199). And when I type... (5 Replies)
Discussion started by: s_linux
5 Replies
7. Solaris
Hi!
I have a dir in a server, that receives files with the wrong permissions, so I decide to put on a cron entry that changes its permitions, but because of the time gap, not all of them get changed.
What I did was the following:
... (14 Replies)
Discussion started by: fretagi
14 Replies
8. Shell Programming and Scripting
Hi,
I am looking for a shell script which serves the below purpose.
Please find below the algorithm for the same and any help on this would be highly appreciated.
1)set of strings need to be replaced among set of files(directory may contain different types of files)
2)It should search for... (10 Replies)
Discussion started by: Amulya
10 Replies
9. Solaris
I want to set ACL permissions using this command in solaris 10 , but I get an error message.
server# mkdir dir1
server# setfacl -m user:allan:rwx dir1
setacl error: Operation not applicable
Any one can help in this matter.
Please use CODE tags as required by forum rules! (2 Replies)
Discussion started by: AbuAliiiiiiiiii
2 Replies
LEARN ABOUT CENTOS
rollback_to_savepoint
ROLLBACK TO
SAVEPOINT(7) PostgreSQL 9.2.7 Documentation ROLLBACK TO SAVEPOINT(7)
NAME
ROLLBACK_TO_SAVEPOINT - roll back to a savepoint
SYNOPSIS
ROLLBACK [ WORK | TRANSACTION ] TO [ SAVEPOINT ] savepoint_name
DESCRIPTION
Roll back all commands that were executed after the savepoint was established. The savepoint remains valid and can be rolled back to again
later, if needed.
ROLLBACK TO SAVEPOINT implicitly destroys all savepoints that were established after the named savepoint.
PARAMETERS
savepoint_name
The savepoint to roll back to.
NOTES
Use RELEASE SAVEPOINT (RELEASE_SAVEPOINT(7)) to destroy a savepoint without discarding the effects of commands executed after it was
established.
Specifying a savepoint name that has not been established is an error.
Cursors have somewhat non-transactional behavior with respect to savepoints. Any cursor that is opened inside a savepoint will be closed
when the savepoint is rolled back. If a previously opened cursor is affected by a FETCH or MOVE command inside a savepoint that is later
rolled back, the cursor remains at the position that FETCH left it pointing to (that is, the cursor motion caused by FETCH is not rolled
back). Closing a cursor is not undone by rolling back, either. However, other side-effects caused by the cursor's query (such as
side-effects of volatile functions called by the query) are rolled back if they occur during a savepoint that is later rolled back. A
cursor whose execution causes a transaction to abort is put in a cannot-execute state, so while the transaction can be restored using
ROLLBACK TO SAVEPOINT, the cursor can no longer be used.
EXAMPLES
To undo the effects of the commands executed after my_savepoint was established:
ROLLBACK TO SAVEPOINT my_savepoint;
Cursor positions are not affected by savepoint rollback:
BEGIN;
DECLARE foo CURSOR FOR SELECT 1 UNION SELECT 2;
SAVEPOINT foo;
FETCH 1 FROM foo;
?column?
----------
1
ROLLBACK TO SAVEPOINT foo;
FETCH 1 FROM foo;
?column?
----------
2
COMMIT;
COMPATIBILITY
The SQL standard specifies that the key word SAVEPOINT is mandatory, but PostgreSQL and Oracle allow it to be omitted. SQL allows only
WORK, not TRANSACTION, as a noise word after ROLLBACK. Also, SQL has an optional clause AND [ NO ] CHAIN which is not currently supported
by PostgreSQL. Otherwise, this command conforms to the SQL standard.
SEE ALSO
BEGIN(7), COMMIT(7), RELEASE SAVEPOINT (RELEASE_SAVEPOINT(7)), ROLLBACK(7), SAVEPOINT(7)
PostgreSQL 9.2.7 2014-02-17 ROLLBACK TO SAVEPOINT(7)