Sponsored Content
Full Discussion: Help with script
Top Forums Shell Programming and Scripting Help with script Post 302285070 by ddreggors on Saturday 7th of February 2009 01:31:27 AM
Old 02-07-2009
Code:
sed -i -re 's/(^<\/.*>$)/SSL Cipher\nSSL Wallet Directory\n\1/' `grep -l "<.*/xyz" ./*`

Before:

<Location /xyz/abc>
Directory
Alias
</Location>

After:
<Location /xyz/abc>
Directory
Alias
SSL Cipher
SSL Wallet Directory
</Location>
 

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

create a shell script that calls another script and and an awk script

Hi guys I have a shell script that executes sql statemets and sends the output to a file.the script takes in parameters executes sql and sends the result to an output file. #!/bin/sh echo " $2 $3 $4 $5 $6 $7 isql -w400 -U$2 -S$5 -P$3 << xxx use $4 go print"**Changes to the table... (0 Replies)
Discussion started by: magikminox
0 Replies

2. Shell Programming and Scripting

Script will keep checking running status of another script and also restart called script at night

I am using blow script :-- #!/bin/bash FIND=$(ps -elf | grep "snmp_trap.sh" | grep -v grep) #check snmp_trap.sh is running or not if then # echo "process found" exit 0; else echo "process not found" exec /home/Ketan_r /snmp_trap.sh 2>&1 & disown -h ... (1 Reply)
Discussion started by: ketanraut
1 Replies

3. UNIX for Dummies Questions & Answers

Calling a script from master script to get value from called script

I am trying to call a script(callingscript.sh) from a master script(masterscript.sh) to get string type value from calling script to master script. I have used scripts mentioned below. #masterscript.sh ./callingscript.sh echo $fileExist #callingscript.sh echo "The script is called"... (2 Replies)
Discussion started by: Raj Roy
2 Replies

4. Shell Programming and Scripting

Shell script works fine as a standalone script but not as part of a bigger script

Hello all, I am facing a weird issue while executing a code below - #!/bin/bash cd /wload/baot/home/baotasa0/sandboxes_finance/ext_ukba_bde/pset sh UKBA_publish.sh UKBA 28082015 3 if then echo "Param file conversion for all the areas are completed, please check in your home directory"... (2 Replies)
Discussion started by: ektubbe
2 Replies

5. Shell Programming and Scripting

How to block first bash script until second bash script script launches web server/site?

I'm new to utilities like socat and netcat and I'm not clear if they will do what I need. I have a "compileDeployStartWebServer.sh" script and a "StartBrowser.sh" script that are started by emacs/elisp at the same time in two different processes. I'm using Cygwin bash on Windows 10. My... (3 Replies)
Discussion started by: siegfried
3 Replies
KWALLETCLI(1)						    BSD General Commands Manual 					     KWALLETCLI(1)

NAME
kwalletcli -- command line interface to the KDE Wallet SYNOPSIS
kwalletcli [-q] -hV kwalletcli [-q] -f folder -e entry [-P | -p password] DESCRIPTION
The kwalletcli utility is a command line interface to KWallet. It will only work if KDE is running (DCOP) and reachable (via X11). kwalletcli can be used to get password entries from the Wallet, or to write them there. The options are as follows: -e entry Define the key (entry) to use when accessing the Wallet. Mandatory. -f folder Set the folder to use when accessing the Wallet. Mandatory. -h Display the usage. -P Read the password to write from standard input. Currently limited to 65535 octets. -p password Write password into the designated location in the Wallet. -q Be more quiet. In combination with -V, do not display anything. -V Display the kwalletcli version information. Default mode of operation, that is, unless -P or -p are used, is to read the password from the Wallet and print it to standard output as-is, without any trailing newline. All input and output is assumed to be in UTF-8. The password string (whether read from standard input or command line) is now converted from ``possibly UTF-8 but binary transparent'' to standards-conformant UTF-8 for the Qt side, and back upon reading out. RETURN VALUES
The kwalletcli utility exits 0 on success or >0 if an error occurred: 1 The entry specified cannot be found (read access). 2 The usage was shown. 3 The Wallet could not be opened. May be a missing DCOP connection. Perhaps DISPLAY is not set. 4 The folder specified cannot be found (read access). 5 The folder specified cannot be opened. 6 The value to the key specified could not be retrieved. 8 An error occured trying to write the value. The exit codes 1 and 4, on reading, are not fatal; they merely indicate that the folder or entry specified does not exist. The other errors are fatal and may be used to indicate the user that the KWallet should not be used any more during the current session. ENVIRONMENT
DISPLAY The X11 display to use for communicating with the KDE Wallet. SEE ALSO
kwalletcli_getpin(1) AUTHORS
kwalletcli was written by Thorsten Glaser <tg@mirbsd.org> mostly for tarent GmbH. CAVEATS
Do not use -p password to store it, unless you absolutely must. It is a security risk, because the command line invocation is public infor- mation in a normal Unix environment. Use -P instead and provide the password on standard input. Beware of trailing newlines, especially outside of mksh(1) scripts! BUGS
If DISPLAY is not set, not valid, or kdeinit or kdeinit4 cannot start for other reasons, kwalletcli may not recover gracefully. In KDE 4 versions, this may even result in a Segmentation fault. The author does not know of a way to catch this early; patches are welcome. There is no way (yet) to set a wallet other than the default wallet. While this is a possible enhancement to the kwalletcli CLI, there is no feasible way to expose this functionality to the various front-ends, such as pinentry-kwallet(1), anyway, so the priority of fixing this is low. BSD
April 9, 2011 BSD
All times are GMT -4. The time now is 04:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy