hi,
we are going for a new unix box and the ip and DNS name has to be changed in all the scripts, where ever it is hard coded.
i was trying the below mentioned command to list all such scripts where the ip/dns name is hard coded:
find / -type f -print | xargs grep -l "ip address" >>... (0 Replies)
I would like to make the same change in multiple shell script files and would like to know if anyone can be of some help? I would appreciate it. (4 Replies)
So a script is working properly (tested many times) , then you add a new fine piece of code ,finaly its fails generally with a syntax error at the last line of the script.
:confused:... does anybody why this happens?
>uname -a
HP-UX test... (4 Replies)
Hi,
could someone help me to create the following scripts
Need to create couple of shell scripts on LINUX SLES 10
Using my id
---------------
First script – this script should contain su and should take input <process name>
1 -login using my id and then sudo to... (1 Reply)
We are changing our OS from HP-Unix 11 to Linux Red Hat. We have few k- shell, c - shell and sql scripts which are currently running under HP-Unix 11. Will these scripts work on LINUX as it is? or we need to do any code changes?IS there anyone who have done this kind of migration before?Thanks for... (2 Replies)
What files or programs have the ability to change your default network scripts and config files? All 3 of these very important files got changed on their own.
/etc/sysconfig/network-scripts/ifcfg-wlan0
/etc/sysconfig/networking/devices/ifcfg-wlan0... (4 Replies)
Hi,
I am a professional in writing shell scripts,
and I am using a one-space indentation like this
for i in file1 file2
do
if
then
echo "$i"
fi
done
so very deeply nested stuff still fits on my screen.
At release time I usually double the indentation via
sed 's/^ */&&/'
to make... (8 Replies)
Discussion started by: MadeInGermany
8 Replies
LEARN ABOUT SUSE
set_constraints
SET CONSTRAINTS(7) SQL Commands SET CONSTRAINTS(7)NAME
SET CONSTRAINTS - set constraint checking modes for the current transaction
SYNOPSIS
SET CONSTRAINTS { ALL | name [, ...] } { DEFERRED | IMMEDIATE }
DESCRIPTION
SET CONSTRAINTS sets the behavior of constraint checking within the current transaction. IMMEDIATE constraints are checked at the end of
each statement. DEFERRED constraints are not checked until transaction commit. Each constraint has its own IMMEDIATE or DEFERRED mode.
Upon creation, a constraint is given one of three characteristics: DEFERRABLE INITIALLY DEFERRED, DEFERRABLE INITIALLY IMMEDIATE, or NOT
DEFERRABLE. The third class is always IMMEDIATE and is not affected by the SET CONSTRAINTS command. The first two classes start every
transaction in the indicated mode, but their behavior can be changed within a transaction by SET CONSTRAINTS.
SET CONSTRAINTS with a list of constraint names changes the mode of just those constraints (which must all be deferrable). The current
schema search path is used to find the first matching name if no schema name is specified. SET CONSTRAINTS ALL changes the mode of all
deferrable constraints.
When SET CONSTRAINTS changes the mode of a constraint from DEFERRED to IMMEDIATE, the new mode takes effect retroactively: any outstanding
data modifications that would have been checked at the end of the transaction are instead checked during the execution of the SET CON-
STRAINTS command. If any such constraint is violated, the SET CONSTRAINTS fails (and does not change the constraint mode). Thus, SET CON-
STRAINTS can be used to force checking of constraints to occur at a specific point in a transaction.
Currently, only foreign key constraints are affected by this setting. Check and unique constraints are always effectively not deferrable.
Triggers that are declared as ``constraint triggers'' are also affected.
NOTES
This command only alters the behavior of constraints within the current transaction. Thus, if you execute this command outside of a trans-
action block (BEGIN/COMMIT pair), it will not appear to have any effect.
COMPATIBILITY
This command complies with the behavior defined in the SQL standard, except for the limitation that, in PostgreSQL, it only applies to for-
eign-key constraints.
SQL - Language Statements 2010-05-14 SET CONSTRAINTS(7)