10-30-2007
oopss....
I've been a little stupid on this one.
Thanks for your input Porter and Radoulov. Radoulov - I see what you're getting at there with all the quoting variables. Whilst it might be a good habit I don't think it would have made much difference in this instance.
There was a part of the script that I had cut out - it's a standard thing we chuck in our scripts which assigns a load of useful variables - including LOGDIR. It was overwriting it with /usr/hxscripts/LOGS - it just didn't occur to me that this might happen. Oops.
Sorry to waste your time, folks!
Thanks again.
-Alex
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi All
I am doing a locate <file_name> on my Redhat 7 System. I am unable to get the output. All the keep getting is:
locate: this is not a vlaid slocate database: /var/lib/locate/slocate.db
What des this mean? Is my system compromised?
Thanks in advance.
KS (13 Replies)
Discussion started by: skotapal
13 Replies
2. UNIX for Dummies Questions & Answers
Ok what is BSD exactly? I know its a type of open source but what is it exactly? (1 Reply)
Discussion started by: Corrail
1 Replies
3. Solaris
Hi all,
Thanks for any replies and for reading in advance.
We have upgraded one of our database instances to 10g on a Solaris 8 box, anyhow the other day it started trying to ping loads of weird IP addresses that we don't use, since our systems all run on pretty similar IP's. It all behind... (0 Replies)
Discussion started by: B14speedfreak
0 Replies
4. Programming
Hello. I'm a complete newbie to C programming. I have a C program that wasn't written by me where I need to write some wrappers around it to automate and make it easier for a client to use. The problem is that the program accepts standard input to control the program... I'm hoping to find a simple... (6 Replies)
Discussion started by: Xeed
6 Replies
5. Shell Programming and Scripting
I am trying to read a file and skip few records based upon the following two columns. Pipe delimiter used between the two columns.
Column1|Column2
Property|CutOff
Target|11111
Min|9999
Max|10000
Comment|This is a test
Property|Weight
Target|222
Min|3434
Max|77777
UOM|mm ... (5 Replies)
Discussion started by: ganesh123
5 Replies
6. Shell Programming and Scripting
hey all, im new and my first question is:
say i have a word "blahblah"
how do i get and replace the last letter of the word with say k, so replace the h with a k.
However you cant just replace the h it has to change the LAST LETTER of the word.
Cheers In advance.
:b: (0 Replies)
Discussion started by: aleks001
0 Replies
7. Shell Programming and Scripting
Hello all!
This is my first post and I'm very new to programming. I would like help creating a simple perl or bash script that I will be using in my work as a junior bioinformatician.
Essentially, I would like to take a tab-delimted or .csv text with 3 columns and write them to a "3D" matrix:
... (16 Replies)
Discussion started by: torchij
16 Replies
8. Red Hat
Cheers!
In /etc/syslog.conf, if an error type is not specified, is it logged anywhere (most preferable is it logged to /var/log/messages) or not?
To be more precise I am interested in error and critical level messages. At default these errors are not specified in syslog.conf, and I need to... (6 Replies)
Discussion started by: dr1zzt3r
6 Replies
9. UNIX for Dummies Questions & Answers
The attachment says it all really...
It is a DEMO at a glance digital readout using the "date" command to make it useful...
For a Mocbook Pro 13", OSX 10.7.5, but may well work on Linux variants too.
Enjoy...
#!/bin/bash
#
# Clock.sh
# A bash DEMO to create a 6 x 7 character set... (4 Replies)
Discussion started by: wisecracker
4 Replies
LEARN ABOUT FREEBSD
devscripts.conf
DEVSCRIPTS.CONF(5) File Formats Manual DEVSCRIPTS.CONF(5)
NAME
devscripts.conf - configuration file for the devscripts package
DESCRIPTION
The devscripts package provides a collection of scripts which may be of use to Debian developers and others wishing to build Debian pack-
ages. Many of these have options which can be configured on a system-wide and per-user basis.
Every script in the devscripts package which makes use of values from these configuration files describes the specific settings recognised
in its own manpage. (For a list of the scripts, either see /usr/share/doc/devscripts/README.gz or look at the output of dpkg -L devscripts
| grep /usr/bin.)
The two configuration files are /etc/devscripts.conf for system-wide defaults and ~/.devscripts for per-user settings. They are written
with bash(1) syntax, but should only have comments and simple variable assignments in them; they are both sourced (if present) by many of
the devscripts scripts. Variables corresponding to simple switches should have one of the values yes and no; any other setting is regarded
as equivalent to the default setting.
All variable names are written in uppercase, and begin with the script name. Package-wide variables begin with "DEVSCRIPTS", and are
listed below, as well as in the relevant manpages.
For a list of all of the available options variables, along with their default settings, see the example configuration file
/usr/share/doc/devscripts/devscripts.conf.ex. This is copied to /etc/devscripts.conf when the devscripts package is first installed.
Information about configuration options introduced in newer versions of the package will be appended to /etc/devscripts.conf when the pack-
age is upgraded.
Every script which reads the configuration files can be forced to ignore them by using --no-conf as the first command-line option.
PACKAGE-WIDE VARIABLES
The currently recognised package-wide variables are:
DEVSCRIPTS_CHECK_DIRNAME_LEVEL, DEVSCRIPTS_CHECK_DIRNAME_REGEX
These variables control scripts which change directory to find a debian/changelog file or suchlike, and some other miscellaneous
cases. In order to prevent unwanted, even possibly dangerous, behaviour, these variables control when actions will be performed.
The scripts which currently make use of these variables are: debc, debchange/dch, debclean, debi, debrelease, debuild and uscan, but
this list may change with time (and I may not remember to update this manpage). Please see the manpages of individual scripts for
details of the specific behaviour for each script.
SEE ALSO
devscripts(1) and /usr/share/doc/devscripts/README.gz.
AUTHOR
This manpage was written for the devscripts package by the package maintainer Julian Gilbey <jdg@debian.org>.
DEBIAN
Debian Utilities DEVSCRIPTS.CONF(5)