However, an alternative would be to put this file on it's own partition then force a dismount of that partition, effectively simulating the loss of access to the storage media.
We have EDP members will do some testing job in my system , but sometimes these process will generate some error to the system log or any file ( usually the members don't know the log is reached to this level ) , then make the system crashed , could suggest the way how can to prevent this problem ?... (2 Replies)
Every time I close a file that I opened for reading I get the following error: ”Memory fault(coredump)”. And, although it does not (I think) affect the overall process (I write another file based on the file I am reading); it is something I would rather not happen. I don't know why this is... (1 Reply)
We have a ksh which runs once every 15 minutes. Based on a certain condition (for invalid data) we are spooling a file and if the file is of length greater than 0 bytes, then we are mailing this file to a group of users. Upon receiving the file, users correct the data so that on its next run the... (2 Replies)
i have this script which works fine but shows errors when it runs..these are more like warnings and the script runs fine.. i am on a sun machine.. i know it writes all the error messages to a master log file.. is there any way i can turn off these warnings/error messages and prevent them from being... (2 Replies)
Below is a test script to illustrate a problem from a larger script I am writing.
$ cat /tmp/loggingtest
#!/bin/bash
lvcreate -s -l 100%FREE -n var-data-snapshot vg00/var-data 2> >(logger -t "loggingtest.crit") 1> >(logger -t "loggingtest.info")
sync &
wait
lvremove -f... (1 Reply)
Hi guys,
i need to write a shell script that will close file descriptors from /proc/pid/fd
will calling exec 4<&- solve the problem ?
thanks in advance :) (15 Replies)
Hello,
I want to create application which launches some terminal, then some command is executed on that terminal and then prevent terminal from closing.
I started to do on gnome-terminal because the Gnome is the most widely used desktop-manager in the Linux distributions.
I want to do... (3 Replies)
Hello,
I have a script that "validates" a ZIP file that look like this
AAA_20120801.zip =>
x~back end~20120801.TXT
y~time in~20120801.TXT
z~heat_chamber~20120801.TXT
AAA_20120801.ctlMy task is to compare its contents (i.e the list of files contained inside) with the control file that is... (2 Replies)
Hi,
Hopefully someone can help.
We have a process that writes a file using Connect Direct to our local Solaris server and then our C++ program will pick up the file and process it. Unfortunately, because of the size of the file, the C++ program is processing the file before it has finished... (7 Replies)
Hi all,
I have a small graphical application whose only purpose is to pop up certain types of messages. Currently, I'm using it in a Bash script like this:
./MyProg "this is my message"
while
do
... do things ...
done
What I want to do is after the while loop is over (it does... (4 Replies)
Discussion started by: Zel2008
4 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)