Sponsored Content
Full Discussion: Problem w. case structure
Top Forums UNIX for Dummies Questions & Answers Problem w. case structure Post 38554 by Joe54321 on Saturday 19th of July 2003 10:15:47 PM
Old 07-19-2003
Hi Perderabo,

Thanks for the help, greatly appreciated!

After reading your answer that [0-60] would be read [0-6] I wondered if you could specify a range for the first entry and another range for the second entry... apparenty you can... this seems to work...

echo -e "Enter a numeric value (0-100): \c"
read answer

case $answer in
[0-9] ) echo "number between 0-59" ;;
[1-5][0-9] ) echo "number between 0-59" ;;
esac

I also did it with an "If" structure and it's easilly done.

Thanks for picking out the $answer error too...

Thanks again Perderabo,

Joe
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Case structure

Hi, Can anyone help me with the following case structure? echo "Please enter the date for which you want the Report:\c" read dat d1=`echo $dat|cut -c7-8` m1=`echo $dat|cut -c5-6` y1=`echo $dat|cut -c1-4` yr=`expr "$d1" - 1` case "$yr" in 0) MONTH=`expr "$m1" - 1`... (4 Replies)
Discussion started by: kamitsin
4 Replies

2. Programming

Search attributes in one structure using the values from another structure

Hello Groups I am trying to find out ways of comparing a value from a 'c' structure to a value in another 'C' structure. the 'C' structure can be a List or liked list as it contains lot many records. if we loop it in both the structures it is going to consume time. I am looking for a simple... (3 Replies)
Discussion started by: dhanamurthy
3 Replies

3. Shell Programming and Scripting

problem with listing of directory structure

Hi When im listing (ls -al ) its listing directories without / at the end of directories dir1 dir2 dir3 and i need to list directories with dir1/ dir2/ dir3/ and this should not be made by command ls -F / should be embedded at the last since one of the scripts reads directories... (1 Reply)
Discussion started by: vasanthan
1 Replies

4. Programming

Problem in static structure array in C

Hi, I have a following problem in C. I have a function A in which I used to call another function (function B) and pass an array of values through array variable by using below:- foo=functionB(array); In functionB, i used to just return some "values" (e.g return num;) in order to pass... (1 Reply)
Discussion started by: ahjiefreak
1 Replies

5. UNIX for Dummies Questions & Answers

ksh case structure

Hello Experts, I ve been trying to build another shell where I am using the following code. transact="tv5cpc1" case "$transact" in "...cp..") xActType="" ;; "...de..") xActType="sp_dep" ;; "...ep..") xActType="sp_epa" ;; "....v.") ... (4 Replies)
Discussion started by: hkansal
4 Replies

6. UNIX for Dummies Questions & Answers

Fall through case structure

Hello Experts, I was wondering how can we get a fall trough case structure. Eg: If we have two cases A and B and a default; if I do not break after A, it should execute all the statements of A as well as B if I break after B else fall through even lower. I tried this: #!/bin/sh v1=1... (6 Replies)
Discussion started by: hkansal
6 Replies

7. Shell Programming and Scripting

case structure in .sh file

Hi, while true do printf "$FBOLD\nPlease enter the minutes (0-59): $FREG" read MIN case "$MIN" in ||s) break 2;; *) echo "" echo "Invalid minutes, please try again.";; esac done In the above... (4 Replies)
Discussion started by: milink
4 Replies

8. Shell Programming and Scripting

Case structure combined with standard input

Hi folks, I am new to bash scripting so please excuse my question. Is there any chance to combine a case structure with the read command? Like case (read -p "" variable) in x) Thx! (7 Replies)
Discussion started by: haukee
7 Replies

9. UNIX for Dummies Questions & Answers

Problem with structure of authlog in regard to an external log Auditing system.

Hello everyone, I hope I'm posting my question in the right section as it is not too easy to find the ideal spot for this one, especially for a brandspankingnew user of this forum. As this might be something simple I chose the Dummy section. By all means, feel free to move the post if not at... (4 Replies)
Discussion started by: Sjleegketting
4 Replies

10. Programming

Malloc problem with fread() to read file to structure in C

Hello, I am trying to read a text file into linked list, but always got the first and last records wrong. 1) The problem looks related to the initialization of the node temp with malloc(), but could not figure it out. No error/warning at compiling, though. 2) The output file is empty,... (10 Replies)
Discussion started by: yifangt
10 Replies
gnats(7)						 Problem Report Management System						  gnats(7)

NAME
gnats - Problem Report Management System DESCRIPTION
GNATS is a bug-tracking tool designed for use at a central support site. Software users who experience problems use tools provided with GNATS to submit Problem Reports to the the maintainers of that software; GNATS partially automates the tracking of these problems by: o organizing problem reports into a database and notifying responsible parties of suspected bugs; o allowing support personnel and their managers to edit, query and report on accumulated bugs; and o providing a reliable archive of problems with a given program and a history of the life of the program by preserving its reported problems and their subsequent solutions. GNATS offers many of the same features offered by more generic databases. You can query and edit existing problem reports (PRs) as well as obtain reports on groups of PRs. The database itself is simply an ordered repository for problem reports; each PR receives a unique, incremental PR number which identifies it throughout its lifetime. Many of the primary functions available with GNATS are accessible from within GNU Emacs. PROBLEM REPORT STATES
PRs go through several states in their lifetimes. The set of states is site-specific. The default set of states are: open the initial state of every PR; this means the PR has been filed and the person or group responsible for it has been notified of the suspected problem analyzed the problem has been examined and work toward a solution has begun feedback a solution has been found and tested at the support site, and sent to the party who reported the problem; that party is testing the solution closed the solution has been confirmed by the party which reported it In some cases, it may be necessary to suspend work on a bug; in this case, its state changes to suspended rather than closed. STRUCTURE
Incoming PRs are assigned an incremental serial number and filed according to category. An index is kept concurrently to accelerate searches of the database. All GNATS administration and database files are located in subdirectories of a directory associated with each database. Databases are named, and the association between database names and directories is described by the databases file, which is found on this system in /usr/etc/gnats/databases. Problem Reports are segregated into subdirectories within the database directory by category. For example, problems submitted with a cate- gory of gcc will be filed in the database subdirectory gcc. GNATS administration files are kept in the database subdirectory gnats-adm: addresses contains mappings between submitter IDs and corresponding e-mail addresses categories table of valid categories and parties responsible for them classes table of valid classes of Problem Reports current keeps track of incremental PR numbers assigned dbconfig describes the structure of the database, and various database-specific options gnatsd.user_access lists host names and access levels of hosts authorized to access the database gnatsd.user_access lists user names, passwords and access levels of users authorized to access the database index database index locks directory containing lock files responsible table of responsible parties and their email addresses states table of valid states of Problem Reports submitters database of sites which submit PRs Administrative programs and programs internal to GNATS are kept in the directory /usr/libexec/gnats while those meant for public use are installed in /usr/bin. /usr/libexec/gnats contains the programs: mkdb used by the GNATS administrator to create a new database mkcat used by the GNATS administrator to create new categories [obsolete] rmcat used by the GNATS administrator to remove outdated categories [obsolete] gen-index used by the GNATS administrator to generate a new version of the index queue-pr mail control program which accepts incoming messages and periodically submits them to the database via cron by feeding them through the program file-pr(8) pr-edit program which is mainly responsible for editing existing PRs and filing new ones; it is used by edit-pr and file-pr file-pr script which uses pr-edit to file new PRs at-pr automatically notifies responsible parties if a PR is not analyzed within a requisite period defined in the submitters file delete-pr used to delete closed PRs /usr/bin contains the programs query-pr used to query the database edit-pr used to edit individual PRs send-pr used to submit problems to GNATS Documentation exists for all programs associated with GNATS. SEE ALSO
Keeping Track: Managing Messages With GNATS (also installed as the GNU Info file gnats.info) databases(5), dbconfig(5), delete-pr(8), edit-pr(1) file-pr(8), gen-index(8), gnats(7), gnatsd(8), mkcat(8), mkdb(8), pr-edit(8), query- pr(1), queue-pr(8), send-pr(1). HISTORY
GNATS was greatly inspired by the BSD sendbug(1) and bugfiler(8) programs. It was originally written in C++, Elisp, shell script, and awk. It presently consists of utilities written in C, shell script, and Elisp. AUTHORS
GNATS was originally written by Heinz G. Seidl (Cygnus Support). Subsequent iterations were developed by Brendan Kehoe (Cygnus Support) and Jason Merrill (Cygnus Support), with help from Tim Wicinski. Documentation was initially developed by Jeffrey Osier (Cygnus Support) and Brendan Kehoe (Cygnus Support). Version 4.x was a substantial rewrite done by Bob Manson (Juniper Networks), Milan Zamazal and Yngve Svendsen (Clustra Systems / Sun Microsystems) COPYING
Copyright (c) 1992, 1993, 1999, 2000, 2003, Free Software Foundation Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that this permission notice may be included in translations approved by the Free Software Foundation instead of in the original English. GNATS
August 2003 gnats(7)
All times are GMT -4. The time now is 10:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy