05-09-2008
7 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have to write an script for..
CUST: 123 trans:
some contents
CUST: 1234 trans:
some contents
Now wat i have to do is this:
CUST:123 akash trans:
some contents
CUST:1234 akash1 trans:
I have been able to add... (3 Replies)
Discussion started by: akashag22
3 Replies
2. Solaris
Hi,
I am having a Solaris 5.9 server in which an audit trail script is running every day.It is doing nothing but taking the backup of three files given below
-rw-r--r-- 1 root root 1807 May 18 01:30 login_server1_17May2008
-rw-r--r-- 1 root root 0 May 18 01:30... (5 Replies)
Discussion started by: Renjesh
5 Replies
3. UNIX for Dummies Questions & Answers
awk -F^ '{ if (($1 != "X") && ($5 != "3")) || if (($1 != "S") && ($5 != "2")) print $0}' abc> xyz
The above command returns this error
awk: syntax error near line 1
awk: illegal statement near line 1
I am newbie to awk, Any awk intelligence involved in correcting this issue is highly... (2 Replies)
Discussion started by: karthickrn
2 Replies
4. Shell Programming and Scripting
Hello
Any Unix programm can help me to solve thsi issue:
I have 2 venn digrams please checke the attached file for pictures of venn diagram for eg red is A yellow is B and green is C..Please see attached file for Venn diagrams
In one .....
I have 3 data set A , B and C
Venn diagram... (0 Replies)
Discussion started by: manigrover
0 Replies
5. Shell Programming and Scripting
Disclaimer: I tried searching but wasn't able to get to the answer so please don't flame.
Scenario:
I have a root script that generates a file on box1 and then needs to scp it over to box2 using user1. Both boxes are running open-ssh.
root@locat-host# scp /tmp/file1 user1@box2:/tmp/file1
... (10 Replies)
Discussion started by: denissi
10 Replies
6. Programming
I have mistakenly removed /root/.cabal/ from my root directoty and when I tried to reinstall it I get this output:
faiz:~$ sudo cabal install pandoc --reinstall
Resolving dependencies...
In order, the following will be installed:
pandoc-1.14.0.4 (reinstall)
Warning: Note that reinstalls are... (3 Replies)
Discussion started by: faizlo
3 Replies
7. Shell Programming and Scripting
i have one function block in the beginning of my script and there are some commands inside that function which will perform some operations.
And i am invoking that function from my main script by passing some values. Sometimes it is hanging in the middle for some value.
For example:
For 1st... (3 Replies)
Discussion started by: thomasraj87
3 Replies
LEARN ABOUT DEBIAN
slack.conf
slack.conf(5) File Formats Manual slack.conf(5)
NAME
slack.conf - configuration file for slack
DESCRIPTION
The file /etc/slack.conf contains configuration information for slack(8) and its backends. It should contain one keyword-value pair per
line, separated by an '=' sign. Keywords must consist solely of capital letters and underscores. Values may take any appropriate format,
but must not begin with a space. Comments start with '#', and all text from the '#' to the end of a line is ignored. Trailing whitespace
on lines is ignored. Empty lines or lines consisting of only whitespace and comments are ignored.
Valid keywords are:
SOURCE The master source for slack roles. It can be in one of four forms:
o /path/to/dir
Use a local directory.
o somehost:/path/to/dir
Use given directory on a remote host via rsync over SSH.
o rsync://somehost/module
Use module on a remote rsyncd server (directly over the network).
o somehost::module
Use the rsync daemon protocol over SSH to the given host. See "USING RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION" in
rsync(1)
All forms of SOURCE are passed directly to rsync, so you can do things like add "user@" before the host on any remote forms. For
more about what rsync can do, see its manual page, of course.
For the last form, however, we do a little magic. rsync treats the last two forms equivalently, so we overload the last form by
automatically passing "-e ssh" to rsync when we see it. This hack lets us tell slack to use this nice feature of rsync just using
the SOURCE config option.
ROOT The root filesystem into which to install slack roles. Usually '/'.
ROLE_LIST
The location of the role list, which lists the roles to be installed by default on each host.
This can be a path relative to the source, or can be an entirely separate location if it starts with a slash or a hostname (option-
ally preceeded by user@).
CACHE A local cache directory, used as a local mirror of the SOURCE.
STAGE A local staging directory, used as an intermediate stage when installing files.
BACKUP_DIR
A directory in which to keep dated backups for rollbacks.
EXAMPLE
A typical file might look like this:
# slack.conf configuration file
SOURCE=slack-master:/slack # source is on a remote
# host named "slack-master"
ROLE_LIST=slack-master:/roles.conf
ROOT=/
CACHE=/var/cache/slack
STAGE=/var/lib/slack/stage
BACKUP_DIR=/var/lib/slack/backups
FILES
/etc/slack.conf
SEE ALSO
slack(8), rsync(1)
File formats 2005-05-23 slack.conf(5)