Sponsored Content
Full Discussion: Problem in if condition
Top Forums Shell Programming and Scripting Problem in if condition Post 302397113 by kshji on Sunday 21st of February 2010 02:16:59 AM
Old 02-21-2010
or
Code:
if ((delcnt <> 0 && delcnt_old <> 0 ))
then
  ...
fi

Code:
if [ "$delcnt" -ne 0 -a "$delcnt_old" -ne 0  ]
then
  ...
fi

; not needed in those format.
But if then is in same line as if, then you need ; between commands if and then
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

If condition problem

Hi Guys, I want to use if conition for my script. Before I used it tried it with some small test scripts. But it was not succeeded. My script and screen output as follows, Script: echo 'Do you think Yes or No (y/n) : ' read ans echo You input anser as $ans ans1=y if ( $ans == $ans1... (5 Replies)
Discussion started by: maheshsri
5 Replies

2. Shell Programming and Scripting

problem with if condition

hi, :) pls consider the following if statement if //g') ] then ........ else ....... when i execute the script i am getting the following error '(' unexpected I am not able to find the mistake. could anybody tell where i did mistake. cheers RRK (13 Replies)
Discussion started by: ravi raj kumar
13 Replies

3. Shell Programming and Scripting

problem in if condition

hi, actully i need the belp for the below. host_list=" Host1 host2 host3 host4 " n=`hostname` i need to put the condition like the below if n is among the host mention in the host_list if then #some stugg else # some other stuff fi (1 Reply)
Discussion started by: mail2sant
1 Replies

4. Shell Programming and Scripting

problem in if then else condition

Hi , I am trying the following simple script . But it is always giving 1 output. Dont know why #!/bin/sh find . -name "a.log" if ; then echo "1" else echo "0" fi Kindly advice. it is giving 1 output even when the a.log file is not there (26 Replies)
Discussion started by: himvat
26 Replies

5. Shell Programming and Scripting

Problem in using AND OR condition together

a=rhino b=crocodil c=testsc if && "$c" = testsc ] then echo "Test #5 succeeds." else echo "Test #5 fails." fi i need to test or condition before check the output with AND condition. ur help is much appreciated... (11 Replies)
Discussion started by: gokulraj23
11 Replies

6. Shell Programming and Scripting

If condition problem

Hi, I need to use if condition for search a file pattern on a particular location. cd $file_Path if || then do this else do that fi Can someone help me with the if part, how i can put those conditions? make sure format should be *.file* and *.file file is a keyword which i... (5 Replies)
Discussion started by: amit.mathur08
5 Replies

7. Shell Programming and Scripting

Problem with IF condition .

Hi i am writing a script where i am running , 5 scripts together in 1 script . Now what i want is when these 5 scripts run completely , i should execute some other commands like i have compile the data etc. I have have 5 echo statements at the end of all those scripts . Like echo "1 is done" in... (1 Reply)
Discussion started by: honey26
1 Replies

8. Shell Programming and Scripting

If condition problem

Hi All, I am using below if condition to check whether null is passed as a parameter to the program if or ; then echo "ABC">>$FILE else echo "CDF">>$FILE fi However it is saying me null=null command not found . Please help me with this (9 Replies)
Discussion started by: Hypesslearner
9 Replies

9. Shell Programming and Scripting

Condition problem

Hi All, Seeking for your assistance on how to condition it correctly. cat file1.txt 290,1663,43,888,0,0.00,86.91,0.00,26.98,0.00 290,1663,52,0,0,0.00,0.00,0.00,0.00,0.00 290,1663,52,888,0,0.00,34.60,0.00,9.00,0.00 1st scenario: if the fourth column contains 888s and 0s it is by... (16 Replies)
Discussion started by: znesotomayor
16 Replies
coreadm(1M)															       coreadm(1M)

NAME
coreadm - core file administration SYNOPSIS
pattern] pattern] option] option] [pid...] [pid...] [arguments] [pid...] DESCRIPTION
The command is used for user space application core file management by specifying the name and the location of core files for abnormally terminating processes. See core(4). The command can be used to control system wide and process specific core file placement. The path and pattern is used by the operating system when generating a core file. The first form shown in can be used to control system wide core file settings or specify a pattern for init(1M). System administration privilege is required to change global core file settings. Global core file setting, including the setting for init(1M), is preserved across system reboot. Non-privileged users can change per-process core file settings for processes owned by that user. The real or the effective user ID of the calling process must match the real or the saved user ID of the receiving process unless the effective user ID of the calling process is a user who as appropriate privileges. A core file name pattern is a normal file system path name with embedded variables, specified with a leading character, that are expanded from values in effect when a core file is generated by the operating system. An expanded pattern over will be truncated to The possible pattern variables are: Options The following options are supported for Disable or enable the specified core file option. The and options can only be exercised with root privilege. The valid options for and are: Allow (or disallow) core dumps using the global core pattern. Allow (or disallow) core dumps using the per-process core pattern. Allow (or disallow) core dumps using the global core pattern for processes. Allow (or disallow) core dumps using the process core pattern for processes. Set the global core file name pattern to pattern. The pattern must start with an absolute path name which exists and can contain any of the special % variables described in the section. This option can only be exercised by the super-user. This is identical to specifying a per-process pattern only that the setting is applied to init(1M) and is preserved across reboot. Set the per-process core file name pattern to pattern for each of the specified process-ID's. The pattern can contain any of the special variables described in and need not begin with If it does not begin with the core file name will be evaluated relative to the current working directory at the time of core file creation. This option can be used by non-privileged users to specify core file settings for processes owned by that user. Super-users can apply it to any process. The per-process core file will be inherited by the future child processes of the affected pro- cesses. See fork(2). This option, when invoked without a PID will apply the settings to the calling process (usually the invoking shell). This option is used in conjunction with The option will execute the command specified with the per-process pattern that was specified with This option can be used to enable or disable core file creation for the target process. As an example, a user may choose to add the disable in the shell startup script to avoid creation of core files by that user. EXAMPLES
The following examples assume that the user has appropriate privilege. 1. To examine the current core file settings: $ coreadm global core file pattern: init(1M) core file pattern: global core dumps: disabled per-process core dumps: enabled global setid core dumps: disabled per-process setid core dumps: disabled 2. Set global core file settings to include process-ID and machine name and place the core file in the location $ coreadm -e global -g /mnt/cores/core.%p.%n A process with PID 1777 on the machine breaker will generate a core file in as (in addition to the core file generated in the CWD of PID 1777). 3. Examine the per process core file settings for process-IDs 1777 and 1778 $ coreadm 1777 1778 1777: core.%p.%u 1778: /nethome/gandalf/core/core.%f.%p.%t 4. A user can disable creation of core files completely by specifying in the shell startup file (for example, $ coreadm -P disable $$ $ coreadm $$ 1157: (Disabled) WARNINGS
The output format of may change without notice. Applications parsing the output, should not rely on the compatibility of the output format between releases. SEE ALSO
umask(1), init(1M), coreadm(2), core(4). coreadm(1M)
All times are GMT -4. The time now is 03:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy