I've seen several examples of grep showing the filename the string was found in, but what I really need is grep to show the file details in long format (like ls -l would).
scenario is:
grep mobile_number todays_files
This will show me the string I'm after & which files they turn up in, but... (2 Replies)
Hi,
I have a log file without date/time, and I want that everytime tail|grep find something it displays the date/time and the line. I have tried something like this command but without any luck to display the date/time:
tail -F catalina.out | sed "s/^/`date `/" | egrep ... (6 Replies)
Hello friends,
I am building one driver related to wifi. When I am looking its hex dump, I can see that it is including a path to one particular file of kernel headers. It is as under.
6C 75 65 2E 0A 00 00 00 25 64 2E 25 64 2E 25 64 lue.....%d.%d.%d
2D 25 73 00 00 00 00 00 42 45... (4 Replies)
Hello all, i'm stumped.... I need to list all directories with all there info and exclude the files, then vice versa. I am not sure if I need to string several ls commands together or how to even do that. I believe I need to do some variation of ls -l but need to figure out how to take out the... (5 Replies)
In Redhat it is easy....
date --date="60 minutes ago"
How do you do this in Solaris?
I got creative and got the epoch time but had problems..
EPOCHTIME=`truss date 2>&1 | grep "time()" | awk '{print $3 - 900}'`
echo $EPOCHTIME
TIME=`perl -e 'print scalar(localtime("$EPOCHTIME")),... (5 Replies)
Hello,
I have a project that I have compiled on a number of linux systems including CentOS, Ubuntu, and Windows Cygwin. I am trying to build the project under SUSE 12.1. The make file runs allot of the way through, but then throws an error that an included file can't be opened.
This is the... (4 Replies)
Is there a way to tell diff to show differences one line at a time and not to group them? For example, I have two files:
file1:
line 1
line 2
line 3 diff
line 4 diff
line 5 diff
line 6
line 7
file2:
line 1
line 2
line 3 diff.
line 4 diff.
line 5 diff.
line 6
line 7 (13 Replies)
is it possible to make apache log each user activity in its log file "access_log"
i have a web application here that uses apache. in the apache log files, i see that it shows when requests are made to certain pages in my web application. but it doesn't show the user name of the person making... (1 Reply)
I need to shred and delete a file after a certain time. Therefore I use
shred -z /path/to/file.txt | rm -rf /path/to/file.txtIt works well, but typing
in that very directory
ls -shiI still see the so called backup-copy lets say file.txt~
When running bleachbit it will disappear thoroughly.... (3 Replies)
Discussion started by: 1in10
3 Replies
LEARN ABOUT SUSE
prepare_transaction
PREPARE TRANSACTION(7) SQL Commands PREPARE TRANSACTION(7)NAME
PREPARE TRANSACTION - prepare the current transaction for two-phase commit
SYNOPSIS
PREPARE TRANSACTION transaction_id
DESCRIPTION
PREPARE TRANSACTION prepares the current transaction for two-phase commit. After this command, the transaction is no longer associated with
the current session; instead, its state is fully stored on disk, and there is a very high probability that it can be committed success-
fully, even if a database crash occurs before the commit is requested.
Once prepared, a transaction can later be committed or rolled back with COMMIT PREPARED [commit_prepared(7)] or ROLLBACK PREPARED [roll-
back_prepared(7)], respectively. Those commands can be issued from any session, not only the one that executed the original transaction.
From the point of view of the issuing session, PREPARE TRANSACTION is not unlike a ROLLBACK command: after executing it, there is no active
current transaction, and the effects of the prepared transaction are no longer visible. (The effects will become visible again if the
transaction is committed.)
If the PREPARE TRANSACTION command fails for any reason, it becomes a ROLLBACK: the current transaction is canceled.
PARAMETERS
transaction_id
An arbitrary identifier that later identifies this transaction for COMMIT PREPARED or ROLLBACK PREPARED. The identifier must be
written as a string literal, and must be less than 200 bytes long. It must not be the same as the identifier used for any currently
prepared transaction.
NOTES
This command must be used inside a transaction block. Use BEGIN [begin(7)] to start one.
It is not currently allowed to PREPARE a transaction that has executed any operations involving temporary tables, created any cursors WITH
HOLD, or executed LISTEN or UNLISTEN. Those features are too tightly tied to the current session to be useful in a transaction to be pre-
pared.
If the transaction modified any run-time parameters with SET (without the LOCAL option), those effects persist after PREPARE TRANSACTION,
and will not be affected by any later COMMIT PREPARED or ROLLBACK PREPARED. Thus, in this one respect PREPARE TRANSACTION acts more like
COMMIT than ROLLBACK.
All currently available prepared transactions are listed in the pg_prepared_xacts system view.
Caution:
It is unwise to leave transactions in the prepared state for a long time. This will interfere with the ability of VACUUM to reclaim
storage, and in extreme cases could cause the database to shut down to prevent transaction ID wraparound (see in the documentation).
Keep in mind also that the transaction continues to hold whatever locks it held. The intended usage of the feature is that a pre-
pared transaction will normally be committed or rolled back as soon as an external transaction manager has verified that other data-
bases are also prepared to commit.
If you have not set up an external transaction manager to track prepared transactions and ensure they get closed out promptly, it is
best to keep the prepared-transaction feature disabled by setting max_prepared_transactions to zero. This will prevent accidental
creation of prepared transactions that might then be forgotten and eventually cause problems.
EXAMPLES
Prepare the current transaction for two-phase commit, using foobar as the transaction identifier:
PREPARE TRANSACTION 'foobar';
SEE ALSO
COMMIT PREPARED [commit_prepared(7)], ROLLBACK PREPARED [rollback_prepared(7)]
SQL - Language Statements 2010-05-14 PREPARE TRANSACTION(7)