Differences in BASH and ASH shells regarding if command? Post: 302452824

10 More Discussions You Might Find Interesting

1. BSD

BSD, Bash and Shells?

When I use Mac OS X's Terminal the UI is some what easier than that of Linux... I this just a shell or something because using Bash is a pain in RH's Linux 9. It's so sensitive about case etc. ??? In that way what is the shell that OS X uses as it's default Bash is on OS X (OK Duh) and...

2. Shell Programming and Scripting

Why generate "ash and bash" different output for same bash script?

Hi, For my bash script, terminal with bash is generate an OK output and program works right. already, terminal with ash have "line 48: syntax error: Bad substitution" output and program don't work. :confused:

3. Shell Programming and Scripting

Interacting with two BASH shells

Hi. I'm working with two BASH shells in order to perform two tasks. For simplicity, suppose that at Shell #1 I'm executing this program: sleep 100 whose PID is 263. Meanwhile Shell #2 is waiting for its termination to follow with a second one. I tried with: wait 263 # Script for second...

4. Shell Programming and Scripting

Bash shells communication

Hello all, I have the following problem. In a Bash shell I run a program (I don't have the source code) which will execute some steps. At every step the program will wait for a user input. So I would like that another script which is running on a different shell will send these input togheter with...

5. Shell Programming and Scripting

Differences between shells

What is the practical difference among the different shell like csh , ksh , bash etc.:confused::confused: Please use descriptive subjects instead of single words

6. Shell Programming and Scripting

ash busybox read command not working inside function....

I have a script that has to execute a read command in a function, this is in an ash busybox. The code is... trapcatch () { echo "Ctl-c Detected, what do you want to do?" echo "Please choose the number of one of the following options" echo "1. Jump past this Set" echo "2. Exit...

7. Shell Programming and Scripting

Bash Script to Ash (busybox) - Beginner

Hi All, I have a script that I wrote on a bash shell, I use it to sort files from a directory into various other directories. I have an variable set, which is an array of strings, I then check each file against the array and if it is in there the script sorts it into the correct folder. But...

8. Ubuntu

Bash to Ash, errors and adjustments

I wrote Bash script and now I want to convert it to Ash. One headache is this function: do_adduser() { setaddprompt _arr_add=("Add manually" "Add via TXT" "return to main menu" "exit program") select add_action in "${_arr_add}" do case "$REPLY" in 1)...

9. Ubuntu

Bash to ash port, character-matching problem

I'm trying to convert this working bash script into an Ash script, read -p "Username:" _username if ! ]]; then echo "Valid" else echo "INVALID" fi However, Ash does not recognize the "=~" character. How can I do this? Also, is there a good reference guide, so I...

10. Ubuntu

Convert a bash to ash

hello everybody, i'm a beginner in ash and i want to convert this bash script to ash. this script send a xml file to a nagios server : #!/bin/bash PROGNAME=$(basename $0) RELEASE="Revision 0.3" print_release() { echo "$RELEASE" } print_usage() { echo "" echo "$PROGNAME...

LEARN ABOUT XFREE86

lpusers

lpusers(1M)						  System Administration Commands					       lpusers(1M)

NAME

       lpusers - set printing queue priorities

SYNOPSIS

       lpusers -d priority-level

       lpusers -q priority-level -u login-ID-list

       lpusers -u login-ID-list

       lpusers -q priority-level

       lpusers -l

DESCRIPTION

       The lpusers command  sets limits to the queue priority level that can be assigned to  jobs submitted by users of the LP print service.

       The  first  form  of the command (with -d) sets the system-wide priority default to priority-level, where priority-level is a value of 0 to
       39, with 0 being the highest priority. If a user does not specify a priority level with a print request (see lp(1)), the  default  priority
       level is used. Initially, the default priority level is 20.

       The  second form of the command (with -q and -u) sets the default highest priority-level (0-39) that the users in login-ID-list can request
       when submitting a print request. The login-ID-list argument may include	any or all of the following constructs:

       login-ID 	       A user on any system

       system_name!login-ID    A user on the system system_name

       system_name!all	       All users on system system_name

       all!login-ID	       A user on all systems

       all		       All users on all systems

       Users that have been given a limit cannot submit a print request with a higher priority level than the one assigned, nor can they change  a
       request	that  has  already been submitted to have a higher priority. Any print requests submitted with priority levels higher than allowed
       will be given the highest priority allowed.

       The third form of the command (with -u)	removes any explicit priority level for the specified users.

       The fourth form of the command (with -q) sets the default highest priority level for all users not explicitly covered by  the  use  of  the
       second form of this command.

       The last form of the command (with -l)  lists the default priority level  and the priority limits assigned to users.

OPTIONS

       The following options are supported:

       -d priority-level

	   Set the system-wide priority default to priority-level.

       -l

	   List the default priority level and the priority limits assigned to users.

       -q priority-level

	   Set the default highest priority level for all users not explicitly covered.

       -q priority-level -u login-ID-list

	   Set the default highest priority-level that the users in login-ID-list can request when submitting a print request.

       -u login-ID-list

	   Remove any explicit priority level for the specified users.

EXIT STATUS

       The following exit values are returned:

       0	       Successful completion.

       non-zero        An error occurred.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWpsu			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       lp(1), attributes(5)

SunOS 5.10							    19 Aug 1996 						       lpusers(1M)