|
|
Sponsored Content
Top Forums
Shell Programming and Scripting
Bash script jumping too quickly to the next command - crash
Post 302973642 by tremblayemilie9 on Thursday 19th of May 2016 02:58:39 PM
05-19-2016
Hi,
thanks for the help.
Yoda;
I tried running the code #!/bin/bash -xv
and I got no information from it...
Maybe I am not doing it right but I see no text or output files from the problem.
Corona;
When this code is run all in one shot, I know that it stops at the step I mentioned above because the output files are not generated. BUT; when I run each steps one by one, it is all good... (
).
Instead, I would like it to run this next step where the ''pipeline'' just seem to run but doing nothing.
By crash, I mean it generates all the first files normally and then, it starts printing through the next steps way too quickly (one of them takes at least 1h normally) and that, up to the last step. I thens stays stuck there as if it was trying to process it still but I know it is not. I have waited for it, and I get no output files.
No error message appears and I am not able to make one appear...
.
I hope this is more clear...
thanks for the help.
Yoda;
I tried running the code #!/bin/bash -xv
and I got no information from it...
Maybe I am not doing it right but I see no text or output files from the problem.
Corona;
When this code is run all in one shot, I know that it stops at the step I mentioned above because the output files are not generated. BUT; when I run each steps one by one, it is all good... (
).Instead, I would like it to run this next step where the ''pipeline'' just seem to run but doing nothing.
By crash, I mean it generates all the first files normally and then, it starts printing through the next steps way too quickly (one of them takes at least 1h normally) and that, up to the last step. I thens stays stuck there as if it was trying to process it still but I know it is not. I have waited for it, and I get no output files.
No error message appears and I am not able to make one appear...
.I hope this is more clear...
Last edited by Scrutinizer; 05-19-2016 at 04:40 PM..
|
|
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
How can I simulate a Linux OS crash without damaging the OS? I am performing an os watchdog test that sends out an alert once the timer
expires. (1 Reply)
Discussion started by: cstovall
1 Replies
2. Shell Programming and Scripting
Hi,
Normally, I will manually to use "ll" command to list the following file from \FILE\CACHE\ directory and check the jump seq. Can I write a script to loop or/and check jump seq file (if jumped seq and show "missing seq no" message for me)
-rw-rw----+ 1 user develop 14012 Sep 4... (1 Reply)
Discussion started by: happyv
1 Replies
3. UNIX for Dummies Questions & Answers
Write a nawk script that will produce the following report:
***FIRST QUARTERLY REPORT***
***CAMPAIGN 2004 CONTRIBUTIONS***
-------------------------------------------------------------------------
NAME PHONE Jan | ... (5 Replies)
Discussion started by: p.palakj.shah
5 Replies
4. Shell Programming and Scripting
hi all,
Ive been trying to find some way of doing this for ages but i have is a shell script that activates a python search and there it no tab completion. more familliar with tcsh at the moment but i'm a newbe.
i was trying to make an easy way to browse to a list of working directories.
... (0 Replies)
Discussion started by: jvan
0 Replies
5. Shell Programming and Scripting
Hi all. I am using procmail to deliver an email to a script I am developing. Procmail delivers the email to the script on standard input. I imagine this is the same as piping input from a command into the script. Hence I've been testing my script by running
echo 'test' | sms-autosend-backup.sh
... (2 Replies)
Discussion started by: akindo
2 Replies
6. Solaris
Hi,
Thanks (10 Replies)
Discussion started by: rocky1954
10 Replies
7. Shell Programming and Scripting
I need help in writing a BASH SCRIPT of ls command.
for example:
$ ./do_ls.sh files
f1.txt
f2.jpeg
f3.doc
$ ./do_ls.sh dirs
folder1
folder2
folder3
My attempt:
#!/bin/bash
#
if test $# -d file
then
echo $dirs
else (3 Replies)
Discussion started by: above8k
3 Replies
8. Shell Programming and Scripting
Hello,
i have bash script where im cycling some command for different lines in external file.
example:
while read domain;do
nslookupout=$(nslookup -type=ns $domain) || true
another commands
done < filenamewithdomains
i added:
|| true
after the command in belief it will just skip... (6 Replies)
Discussion started by: postcd
6 Replies
9. Shell Programming and Scripting
I am beginning to write a new version of the bash menu below. The previous version worked great and now when I start the updated bash it opens and a some lines print in the terminal and it closes quickly. I know there are errors but how can I see them or fix them, I tried set -x with the same... (12 Replies)
Discussion started by: cmccabe
12 Replies
10. Shell Programming and Scripting
I need to be able to use a sed command as a variable in a bash script. I have the sed command that almost works the way I want it. the command is
sed -n '/inet/,/}/p' config.boot
This gets me this result:
inet 192.168.1.245
}
I need to get the IP address into a variable so I... (9 Replies)
Discussion started by: edlentz
9 Replies
LEARN ABOUT DEBIAN
smokeping_probes_skel
Smokeping_probes_skel(3) SmokePing Smokeping_probes_skel(3) NAME
Smokeping::probes::skel - a skeleton for Smokeping Probes SYNOPSIS
*** Probes *** +skel forks = 5 offset = 50% step = 300 timeout = 15 # The following variables can be overridden in each target section pings = 5 # [...] *** Targets *** probe = skel # if this should be the default probe # [...] + mytarget # probe = skel # if the default probe is something else host = my.host pings = 5 DESCRIPTION
This is a non-functional module that is intended to act as a basis for creation of new probes. See the smokeping_extend document for more information. VARIABLES
Supported probe-specific variables: forks Run this many concurrent processes at maximum Example value: 5 Default value: 5 offset If you run many probes concurrently you may want to prevent them from hitting your network all at the same time. Using the probe- specific offset parameter you can change the point in time when each probe will be run. Offset is specified in % of total interval, or alternatively as 'random', and the offset from the 'General' section is used if nothing is specified here. Note that this does NOT influence the rrds itself, it is just a matter of when data acqusition is initiated. (This variable is only applicable if the variable 'concurrentprobes' is set in the 'General' section.) Example value: 50% step Duration of the base interval that this probe should use, if different from the one specified in the 'Database' section. Note that the step in the RRD files is fixed when they are originally generated, and if you change the step parameter afterwards, you'll have to delete the old RRD files or somehow convert them. (This variable is only applicable if the variable 'concurrentprobes' is set in the 'General' section.) Example value: 300 timeout How long a single 'ping' takes at maximum Example value: 15 Default value: 5 Supported target-specific variables: pings How many pings should be sent to each target, if different from the global value specified in the Database section. Note that the number of pings in the RRD files is fixed when they are originally generated, and if you change this parameter afterwards, you'll have to delete the old RRD files or somehow convert them. Example value: 5 AUTHORS
Niko Tyni <ntyni@iki.fi>, SEE ALSO
smokeping_extend 2.6.8 2013-03-17 Smokeping_probes_skel(3)