Check if argument passed is an integers Post: 31264

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

how to print all argument passed

like i have script with which i have passed arg list :eg: i/p: scriopt1 arg1 arg2 arg3 .... argn o/p: arg1 arg2 arg3 .... argn

2. Shell Programming and Scripting

How to check that passed parameters all have the same extension?

$ ls monkey.txt banana.csv tree.txt $ myscript monkey.txt tree.txt All extensions ARE alike. $ myscript *txt All extensions ARE alike. $ myscript monkey.txt banana.csv All extensions are NOT alike. $ myscript * All extensions are NOT alike. My brain has given up; what's the simplest...

3. Shell Programming and Scripting

File not recognized when passed as argument

I have the below script in file read_file.ksh if ] || ] then echo "Required one input file" echo "Enter a file to get char count:" read $FILE_NAME if ] then echo "valid file" else echo "Not a valid file." fi When run as read_file.ksh detail.csv or...

4. Shell Programming and Scripting

Check if passed arguments is users

i want to check passed arguments one by one and if it is user print home director of that user

5. Shell Programming and Scripting

shell script for ftp files passed in command line argument

i want to write a shell script function that will ftp the files passed in the command line . i have written a shell script for ftp but how will it do for all files passed in command line argument , i am passing 4 files as argument ./ftp.sh file1 file2 file3 file4 code written by me...

6. Shell Programming and Scripting

Shell script that check the argument passed to it and prints error if test condition is not met

I want to make a script that check for the argument passed to it and generates an error in case any character/string argument passed to it. I am using below code, but its not working. can anyone help. #!/bin/bash if ]; then echo 'An integer argument is passed to the script hence...

7. Shell Programming and Scripting

Variable passed as argument

I have a script. #!/bin/sh cur_$1_modify_time=Hello echo "cur_$1_modify_time" When I run like sh /root/script1 jj I expect value "Hello" being assigned to variable "cur_jj_modify_time" and output being "Hello" ie echoing $cur_jj_modify_time But the output comes as # sh...

8. Shell Programming and Scripting

Grep float/integers but skip some integers

Hi, I am working in bash in Mac OSX, I have following 'input.txt' file: <INFO> HypoTestTool: >>> Done running HypoTestInverter on the workspace combined <INFO> HypoTestTool: The computed upper limit is: 11 +/- 1.02651 <INFO> HypoTestTool: expected limit (median) 11 <INFO> HypoTestTool: ...

9. How to Post in the The UNIX and Linux Forums

Read a json file passed as cmd line argument

usage: myscript.sh config.json config.json: { "HOST":"abc", "DB_NM":"xyz", "USR_NM":"asd", "PWD":"xxx", ......... ......... ......... ........ } myscript.sh:

10. Shell Programming and Scripting

Getting number of argument passed to a shell script

Hi Experts, I have been trying to work on a simple shell script that will just add the two argument passed to it. Here is what i tried : #!/bin/bash welcome(){ echo "Welcome to this Progg. which will accept two parameter" } main_logic(){ arg=$# echo "Number of argument passed is...

LEARN ABOUT REDHAT

man.conf

MAN.CONF(5)                                                     File Formats Manual                                                    MAN.CONF(5)

NAME

       man.conf - configuration file for man

DESCRIPTION

       This is the configuration file for the man(1), apropos(1), and makewhatis(8) utilities.  Its presence, and all directives, are optional.

       This file is an ASCII text file.  Leading whitespace on lines, lines starting with '#', and blank lines are ignored.  Words are separated
       by whitespace.  The first word on each line is the name of a configuration directive.

       The following directives are supported:

       manpath path
               Override the default search path for man(1), apropos(1), and makewhatis(8).  It can be used multiple times to specify multiple
               paths, with the order determining the manual page search order.

               Each path is a tree containing subdirectories whose names consist of the strings 'man' and/or 'cat' followed by the names of
               sections, usually single digits.  The former are supposed to contain unformatted manual pages in mdoc(7) and/or man(7) format; file
               names should end with the name of the section preceded by a dot.  The latter should contain preformatted manual pages; file names
               should end with '.0'.

               Creating a mandoc.db(5) database with makewhatis(8) in each directory configured with manpath is recommended and necessary for
               apropos(1) to work, but not strictly required for man(1).

       output option [value]
               Configure the default value of an output option.  These directives are overridden by the -O command line options of the same names.
               For details, see the mandoc(1) manual.

                      option     value     used by -T
                      fragment   none      html
                      includes   string    html
                      indent     integer   ascii, utf8
                      man        string    html
                      paper      string    ps, pdf
                      style      string    html
                      width      integer   ascii, utf8

       _whatdb path/whatis.db
               This directive provides the same functionality as manpath, but using a historic and misleading syntax.  It is kept for backward
               compatibility for now, but will eventually be removed.

FILES

       /etc/man.conf

EXAMPLES

       The following configuration file reproduces the defaults: installing it is equivalent to not having a man.conf file at all.

             manpath /usr/share/man
             manpath /usr/X11R6/man
             manpath /usr/local/man

SEE ALSO

       apropos(1), man(1), makewhatis(8)

HISTORY

       A relatively complicated man.conf file format first appeared in 4.3BSD-Reno.  For OpenBSD 5.8, it was redesigned from scratch, aiming for
       simplicity.

AUTHORS

       Ingo Schwarze <schwarze@openbsd.org>

Debian                                                           December 28, 2016                                                     MAN.CONF(5)