I can't test this, but I would be interested in seeing if you like this way with a coprocess better. It is definitely more efficient than starting/closing SQL/Plus for every row in the sidlist file. Try running it with the "time" command and see if it is faster than how you were going to do it before. I have a coprocess example somewhere that I will post that also shows how to retrieve query results into shell variables. I think it would be good info to put out there. Coprocess example: https://www.unix.com/shell-programmin...#post302540429
Hi i just whant to update an password entry in /etc/shadow.
But dosen't get it to work. Something is wrong! in this code.
What i try do do is if user kalle exist in shadow.
I whant it to update it's password for just that entry.
#include <stdio.h>
#include <errno.h>
#include <stdlib.h>... (2 Replies)
hi all
i am very new to unix. we had the below scenior
test.bat file which contains
ftp -s:logfiles.scr servername
logfiles.scr contains
username
password
cd path
get file
bye
We had n number of batch(.bat files). which is having the same kind of scr file pointing... (10 Replies)
Hi,
How can I avoid multiple 'cat while read ....? in my script.
In my script, I am taking the inputs from the temp text file and doing the
(
cat while read input
do
...
...
done
)
task and deleting later.
I know it'll raise the perfomance issue. How to avoid this? (2 Replies)
I have a database that contains a list of server names, and the password for the root user on several servers (100+). I need to verify the passwords for each of the servers in an automated fashion because the database continues to grow. All of the users that I'm going to test are ROOT. I can't... (1 Reply)
Hi all,
putty connection manager is great but when attempting to sudo or ssh to another box via the post login commands it is subject to issues due to network latency (what happens is that pcm enters the password before the unix box is ready to receive it). Is there any clever way I can make... (1 Reply)
How would I grep for password file entry without using
grep 'username' /etc/passwd?
perhaps with who?
I want to create alias that will find the password file entry regardless of the user who is using it.
I am trying to get the same exact line from the file entry like:
Name : Password : UserID... (7 Replies)
How would I grep for password file entry without using
grep 'username' /etc/passwd?
perhaps with who?
I want to create alias that will find the password file entry regardless of the user who is using it.
Thanks (4 Replies)
Before I start, two things.
1) Yes I know it's bad practice and obomination to all things holy, but I'm not a sys admin at JP Morgan, I'm a hobbyist tooling about in a VM, in my pants, at home.
2) If you are just going to flame for even considering hardcoding a root password, thanks, I get... (2 Replies)
Hello,
I have currently coded a bash script below in which it does the following:
# Archives compressed file from another location.
Basically it moves *.gz files to another location.
The script also sends an email whenever a new compressed file is placed. This is the issue that i... (5 Replies)
Hi
I have a root script which is setting up user and his dirs and so on. After I create user and set up all the necessary I have to manually set user password. I try all possible ways what google find me and nothing works for me. If maybe one of you have a solution for my problem it will be... (1 Reply)
Discussion started by: Jaffakeks
1 Replies
LEARN ABOUT CENTOS
gtester
GTESTER(1) User Commands GTESTER(1)NAME
gtester - test running utility
SYNOPSIS
gtester [OPTION...] [testprogram]
DESCRIPTION
gtester is a utility to run unit tests that have been written using the GLib test framework.
When called with the -o option, gtester writes an XML report of the test results, which can be converted into HTML using the gtester-report
utility.
OPTIONS -h, --help
print help and exit
-v, --version
print version information and exit
--g-fatal-warnings
make warnings fatal
-k, --keep-going
continue running after tests failed
-l
list paths of available test cases
-m=MODE
run test cases in MODE, which can be one of:
perf
run performance tests
slow, thorough
run slow tests, or repeat non-deterministic tests more often
quick
do not run slow or performance tests, or do extra repeats of non-deterministic tests (default)
undefined
run test cases that deliberately provoke checks or assertion failures, if implemented (default)
no-undefined
do not run test cases that deliberately provoke checks or assertion failures
-p=TESTPATH
only run test cases matching TESTPATH
-s=TESTPATH
skip test cases matching TESTPATH
--seed=SEEDSTRING
run all test cases with random number seed SEEDSTRING
-o=LOGFILE
write the test log to LOGFILE
-q, --quiet
suppress per test binary output
--verbose
report success per testcase
SEE ALSO gtester-report(1)GLibGTESTER(1)