Hi,
I'm looking for advice on where is the best place on Solaris to put a script that will setup system vairables prior to any users loging in. I've tried /etc/rc3.d without much success as the variables do not appear in the output from an env command.
I want the system to have these... (7 Replies)
I'm trying to define a variable named sin
I already have a variable named cos, which has the value "hello"
I want sin to have the value of "hellothere",
so sin would be something like
sin = $cos & "there"
but I'm not sure that I know the syntax.
Can anyone help?
:confused: (4 Replies)
I've got a modified samba script (named it winprint) that I can use to print out to a to a shared Win Network printer from an AIX machine. This is a modification of the samba provided smbprint script changed to work under AIX as the backend for a queue. It does not read a config file
I can print... (0 Replies)
Is it possible to send a custom signal to a process?
e.g. Send signal 9999 to my process, which handles it with some custom handler.
How would one do this? (12 Replies)
I am running the example from the following webpage:
MySQL :: MySQL 5.0 Reference Manual :: 12.1.11 CREATE TRIGGER Syntax
and the problem is that triggers cannot be defined for some reason:
CREATE DATABASE IF NOT EXISTS triggertest;
USE triggertest;
CREATE TABLE test1(a1 INT);
CREATE TABLE... (3 Replies)
In root dir i have created a .profile file and added variable and assigned a path to it:
a = '/dir/dir'
export a
but when i echo (echo $a) the path or use this variable the value or path not getting displayed.
i tried executing the .profile and logging out and logging in, didnt workout. am... (1 Reply)
I have defined this alias as quick way to find out which mount point to use for a USB drive after inserting it:
# alias da='dmesg | grep da | grep MB'
However, when invoking it, it states the following:
# da
da: Command not found.
Can someone explain what is the issue here and how it can be... (3 Replies)
Hi All,
I have a trivial question but I dont know how to solve it.
So basically I'm working on a USB key and I have a directory with some scripts which I use to work on files present in other directories within the USB or sometimes on the main harddisk too. The problem is every time I have to... (3 Replies)
Hi
I'd say I'm having this weird problem where my script isn't taking the value off a variable or printing it. My code is like this:
set count_C= `grep -c C mols`
set count_H= `grep -c H mols`
set count_O= `grep -c O mols`
sed -i '7,7 s/$/ $count_C $count_O $count_H/g' input It... (8 Replies)
Discussion started by: saleheen
8 Replies
LEARN ABOUT CENTOS
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)