01-09-2020
Welcome to the forums!
A number of things is wrong (to start with):
1. a logical construct [ logical ] should have trailing/leading spaces, e.g.: if [ "$DAYOFWEEK" == 1 ]
2. numerical comparison within the [] should be done with -eq/-ge/-le/etc..., eg: if [ "$DAYOFWEEK" -eq 1 ]
3. the grouping of the logicals within the if, should be done as follows, e.g. if [ logical1 ] && [ logical2 ]
4. you're missing a 'closing' fi for your leading if - I bet your trailing doneshould be an fi
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have a rather big script that i have written in ksh and it is falling over in two places with a 'test argument' error. I know this usually means that the if statement is not correct, but it is fine. I have looked through the rest of the script for any odd brackets or ` marks, but can't see... (2 Replies)
Discussion started by: handak9
2 Replies
2. Shell Programming and Scripting
How do I change directories to a path given by input variable in Korn Shell?
e.g. I tired with the Korn Shell below but it doesn't work.
----------------------------------
#!/bin/ksh
echo "Enter folder name: \c"
read folder
cd $folder
----------------------------------
Any help will... (5 Replies)
Discussion started by: stevefox
5 Replies
3. UNIX for Dummies Questions & Answers
Hello,
How do I write a korn shell that will rename file with the current date. What I want to do is, I have a file that is re-written every day. But instead, I want to keep a 14 day history of the file. So I want to write a script that will rename the current file with a date attached to the... (2 Replies)
Discussion started by: watson2000
2 Replies
4. Shell Programming and Scripting
How do I replace a space " " character at a particular position in a line?
e.g. I have a file below
$ cat i2
111 002 A a
33 0011 B c
2222 003 C a
I want all the 1st spaces to be replaced with forward slash "/" and the 3rd spaces to have 5 spaces to get the output below:
111/002... (8 Replies)
Discussion started by: stevefox
8 Replies
5. Shell Programming and Scripting
Hi all,
I need a Korn Shell script that will go out to all Unix Servers and pull all non humans IDs from them while at the same time produce a file to show which servers we have access to and which ones we don't.
Thanks in advance. (5 Replies)
Discussion started by: vinsara
5 Replies
6. Shell Programming and Scripting
I'd like a shell-script syntax checker that can detect at least the following errors, and more:
1. Variable $VAR used but VAR has not been defined.
2. Variable VAR defined but never used.
3. Use of unquoted variables which might break external commands e.g. SOMETHING in: value=`grep $SOMETHING... (5 Replies)
Discussion started by: garethr
5 Replies
7. Shell Programming and Scripting
Hi,
I am new to this unix scripting, I got a requirement like..
Files with *.XML extension will be generating in a /home/sample/ folder for every 15 mins. I need to monitor those files in that particular folder for every hour.
If no file has been generated in that particular folder for an... (7 Replies)
Discussion started by: siri_886
7 Replies
8. Shell Programming and Scripting
All,
Can anyone please help me with the below scenario in korn shell script.
Can anyone please give me some hints to proceed on this.
I have a Flat file of the below format.
Input file format:... (1 Reply)
Discussion started by: sp999
1 Replies
9. Shell Programming and Scripting
#! /bin/ksh
while read line
do
if ] ; then
echo "no data"
continue;
fi
echo "performing operation on $line"
done < prg.txt (3 Replies)
Discussion started by: Juhi Kashyap
3 Replies
10. Shell Programming and Scripting
Hi,
I have files in the directory like below which I need to validate if all the required files are present.
A_B_001 of 002_time1.txt
A_B_002 of 002_time1.txt
A_B_001 of 001_time2.txt
Scenarios-
a)If file with 001 of 002_time1 or 002 of 002_time1 is missing in the folder,script should... (6 Replies)
Discussion started by: aneeta13
6 Replies
LEARN ABOUT DEBIAN
colorgccrc
COLORGCCRC(5) File Formats Manual COLORGCCRC(5)
NAME
colorgccrc - configuration file for colorgcc
DESCRIPTION
A colorgccrc configuration file is used to configure the highlighting of the compiler output from colorgcc.
SYNTAX
Each line consists of a keyword designating a configuration variable. The keyword is followed by `:' and then one or several values
(depending on the keyword). Lines beginning with a hash mark `#' are comments.
CONFIGURATION VARIABLES
g++ | gcc | c++ | cc | g77 | gcj | gnat | gpc
Specifies the paths to the compilers. Takes one value; a path to the compiler.
nocolor
Specifies what terminal types colorization should be disabled on. Takes one or several values, separated by whitespace.
srcColor
Specifies the highlighting attributes source-code should be given. Takes one or several color attributes. See the section COLOR
ATTRIBUTES for more information.
introColor
Specifies the highlighting attributes for normal compiler output. Takes one or several color attributes. See the section COLOR
ATTRIBUTES for more information.
warningFileNameColor | errorFileNameColor
Specifies the highlighting attributes for the filename in a warning or an error, respectively. Takes one or several color
attributes. See the section COLOR ATTRIBUTES for more information.
warningNumberColor | errorNumberColor
Specifies the highlighting attributes for the line-number in a warning or an error, respectively. Takes one or several color
attributes. See the section COLOR ATTRIBUTES for more information.
warningMessageColor | errorMessageColor
Specifies the highlighting attributes for the message-text in a warning or an error, respectively. Takes one or several color
attributes. See the section COLOR ATTRIBUTES for more information.
COLOR ATTRIBUTES
The following attributes are valid for highlighting.
clear, reset
bold, underline, underscore, blink, reverse, concealed
black, red, green, yellow, blue, magenta, cyan, white
on_black, on_red, on_green, on_yellow, on_blue, on_magenta, on_cyan, on_white
SEE ALSO
gcc(1), colorgcc(1)
HISTORY
Jan 15 2003: Initial version of this manual-page.
REPORTING BUGS
Report bugs to <jmoyers@geeks.com>
AUTHORS
Jamie Moyers <jmoyers@geeks.com> is the author of colorgcc.
This manual page was written by Joe Wreschnig <piman@sacredchao.net>, and modified by David Weinehall <tao@debian.org>, for the Debian
GNU/Linux system (but may be used by others).
COPYRIGHT
Copyright (C) 2003 Jamie Moyers
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
Jan 15, 2003 COLORGCCRC(5)