12-10-2007
There's no real difference. The first approach will work even if you have a different shell selected at the top of the script or have not set execute permissions on test.sh.
The second approach will use whatever shell is in the #! path and will only run if the execute bit is set.
Which approach to use depends on your environment and needs.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi all,
I have a script like:
echo Please input list file name:
read listn
for file in `cat $listn.txt`
do
send_file $file
done
normally, I will run the script like:
:. resendfile
Please input list filename:
list1
#Then, the script will resend all file from the list1. However,... (4 Replies)
Discussion started by: happyv
4 Replies
2. Shell Programming and Scripting
Hi,
How can I run a script at 9:00am and 6:00pm everyday? Can I run it at background while I logout my account?
Please help!!
Many Thanks!! (1 Reply)
Discussion started by: happyv
1 Replies
3. Shell Programming and Scripting
Hello all
i have csh script called test.csh , and i need to run it in the background
so i do : test.csh &
but i wander can i tell within the script source to run it in the background automatically , without giving the user to add the "&"
when executing in the shell ? (1 Reply)
Discussion started by: umen
1 Replies
4. Shell Programming and Scripting
hi,
i have a script that runs on bash and would like to run it on a machine that has csh and bash. the default setting on that machine is csh. i dont want to change my code to run it with a csh shell. is there any way i can run the script (written in bash) on this machine? in other words is there... (3 Replies)
Discussion started by: npatwardhan
3 Replies
5. UNIX for Dummies Questions & Answers
I have a script I want to run in the background, and I have looked it up but I am not exactly sure how to do. First of all to run it in the background do you have to put something in the script or is it just a command when you go to run it. I found this solution to it but once again I am not to... (2 Replies)
Discussion started by: mauler123
2 Replies
6. Shell Programming and Scripting
Dear All,
I am trying to run a script in background like ./scriptname.sh & but when i try to run it in background it is giving me an error "syntax error at line 12: `(' unexpected" at the line 12, there is a function definition
"function getFileList()".
This script runs fine if i run on... (2 Replies)
Discussion started by: bilalghazi
2 Replies
7. Shell Programming and Scripting
hi,
we have a script which runs for the whole day and whenever the job fails, will send an alert to the mailbox. My problem here is that i need to give the jobname dynamically which is not possible if we run the script in background. Pls help me with this.
Thanks
Ajay (6 Replies)
Discussion started by: ajayakunuri
6 Replies
8. Shell Programming and Scripting
Dear All,
Writing a script in which I want to run a command in background and keep it running even script is finished.
I have tried like below,
`truss -p <pid> >> & /tmp/log &`
But doesnt work.. script goes running and nothing in log file. (7 Replies)
Discussion started by: Deei
7 Replies
9. Shell Programming and Scripting
Hello! I have got a homework. The bash script runs in the background and checks the user's mailbox and when the user gets a new mail a popup window appears with some text and information about the sender (from who and when).I have no idea how to start, any help would be appreciated! Thank you:) (1 Reply)
Discussion started by: capo2ndfret
1 Replies
10. UNIX for Beginners Questions & Answers
Hi Guys,
i am having a script which checks for ip address is pingable or not,when i execute this script in terminal it keeps on showing the pinging status of every ip address and it takes more time when i check for 100 ip address,How to do run a script in background without showing in the terminal... (4 Replies)
Discussion started by: Meeran Rizvi
4 Replies
LEARN ABOUT CENTOS
doveadm-log
DOVEADM-LOG(1) Dovecot DOVEADM-LOG(1)
NAME
doveadm-log - Locate, test or reopen Dovecot's log files
SYNOPSIS
doveadm [-Dv] log errors [-s min_timestamp]
doveadm [-Dv] log find [directory]
doveadm [-Dv] log reopen
doveadm [-Dv] log test
DESCRIPTION
The doveadm log commands are used to locate and reopen the log files of dovecot(1). It's also possible to test the configured targets of
the *log_path settings.
OPTIONS
Global doveadm(1) options:
-D Enables verbosity and debug messages.
-v Enables verbosity, including progress counter.
COMMANDS
log errors
doveadm log errors [-s min_timestamp]
The log errors command is used to show the last - up to 1,000 - errors and warnings. If no output is generated, no errors have occurred
since the last start.
-s min_timestamp
An integer value, representing seconds since the epoch - also known as Unix timestamp. When a min_timestamp was given, doveadm(1)
will only show errors occurred since that point in time.
log find
doveadm log find [directory]
The log find command is used to show the location of the log files, to which dovecot(1) sends its log messages. If dovecot(1) logs its
messages through syslogd(8) and doveadm(1) could not find any log files, you can specify the directory where your syslogd writes its log
files.
log reopen
doveadm log reopen
This command causes doveadm to reopen all log files, configured in the log_path, info_log_path and debug_log_path settings. These settings
are configured in /etc/dovecot/conf.d/10-logging.conf.
This is for example useful after manually rotating the log files.
log test
doveadm log test
This command causes doveadm to write the message "This is Dovecot's priority log (timestamp)" to the configured log files. The used prior-
ities are: debug, info, warning, error and fatal.
EXAMPLE
This example shows how to locate the log files used by dovecot(1).
doveadm log find
Looking for log files from /var/log
Debug: /var/log/dovecot.debug
Info: /var/log/mail.log
Warning: /var/log/mail.log
Error: /var/log/mail.log
Fatal: /var/log/mail.log
REPORTING BUGS
Report bugs, including doveconf -n output, to the Dovecot Mailing List <dovecot@dovecot.org>. Information about reporting bugs is avail-
able at: http://dovecot.org/bugreport.html
SEE ALSO
doveadm(1)
Dovecot v2.2 2013-11-24 DOVEADM-LOG(1)