the following command should be in either back quotes or $(..)
we can't directly assign the like this the command ouput
here after nawk it should be normal single quote, not back quote.. and after the closed brace }, it should be single quote and then again single back quote...
I am trying to run the script bellow but its given me "syntax error at line 20 :'done' unexpected." error message"
can someone check to see if the script is ok? and correct me pls.
Today is my first day with scripting.
Gurus should pls help out
#!/bin/ksh
# Purpose: Check to see if file... (3 Replies)
hi there
i write one awk script file in shell programing
the code is related to dd/mm/yy to month, day year format
but i get an error
please can anybody help me out in this problem ??????
i give my code here including error
awk `
# date-month -- convert mm/dd/yy to month day,... (2 Replies)
Hi,
I have following K script, that is in rc0.d directory to be run on shutdown. It's linked using the 'ln' command to init.d.Can anyone tell me as to why it's not running, or if i have incorrect syntax?I get:
"test: argument expected
type=uname -p
+ "
When running it with sh -x
... (8 Replies)
Hello everyone.
I'm stuck with an error message that neither I nor any of my computer science peeps can understand. The program I wrote is meant to be a simple decimal to binary converter, but with this message it's more complicated than I thought.
Here's the code:
#include <iostream>... (2 Replies)
Hello everyone.
I'm stuck with an error message that neither I nor any of my computer science peeps can understand. The program I wrote is meant to be a simple decimal to binary converter, but with this message it's more complicated than I thought.
Here's the code:
#include <iostream>... (3 Replies)
Hi All,
I am getting below error message while executing memory utilization script.
$ ./mem1.sh
syntax error on line 1, teletype
syntax error on line 1, teletype
$
$ uname -a
SunOS 5.9 XXX Generic_122300-60 sun4u sparc SUNW,Sun-Fire-V440
$
But i can execute same script in... (3 Replies)
Hi guys here i'm again with more question
The code below try to find an user and write everything about him if exist, so my problem appear on line of test, where the program test if the user has secondary groups related. The rest it's clear
# usugrup.sh lista todas las caracteristicas de un... (3 Replies)
Hello,
I have another problem with my script. Please accept my apologies, but I am really nooby in sh scripts. I am writing it for first time.
My script:
returned=`tail -50 SapLogs.log | grep -i "Error"`
echo $returned
if ; then
echo "There is no errors in the logs"
fi
And after... (10 Replies)
Hi
Below script is throwing an error:
repos=root
filename=/home/admin/Desktop/authz
case $repos in
root)
root_folder="\"
do
sed "/$root_folder/a $username = $access" $filename
done
;;
esac
exit 0
Error:
./new1.sh: line 77: syntax error near unexpected token `do' (1 Reply)
Discussion started by: ankur328
1 Replies
LEARN ABOUT CENTOS
btraceback
BTRACEBACK(1) Network backup, recovery and verification BTRACEBACK(1)NAME
btraceback - wrapper script around gdb and bsmtp
SYNOPSIS
btraceback /path/to/binary pid
DESCRIPTION
btraceback is a wrapper shell script around the gdb debugger (or dbx on Solaris systems) and bsmtp, provided for debugging purposes.
USAGE
btraceback is called by the exception handlers of the Bacula daemons during a crash. It can also be called interactively to view the cur-
rent state of the threads belonging to a process, but this is not recommended unless you are trying to debug a problem (see below).
NOTES
In order to work properly, debugging symbols must be available to the debugger on the system, and gdb, or dbx (on Solaris systems) must be
available in the $PATH.
If the Director or Storage daemon runs under a non-root uid, you will probably need to be modify the btraceback script to elevate privi-
leges for the call to gdb/dbx, to ensure it has the proper permissions to debug when called by the daemon.
Although Bacula's use of btraceback within its exception handlers is always safe, manual or interactive use of btraceback is subject to the
same risks than live debugging of any program, which means it could cause Bacula to crash under rare and abnormal circumstances. Conse-
quently we do not recommend manual use of btraceback in production environments unless it is required for debugging a problem.
ENVIRONMENT
btracback relies on $PATH to find the debugger.
FILES
/usr/lib/bacula/btraceback
The script itself.
/usr/sbin/btraceback
symbolic link to /usr/lib/bacula/btraceback
/etc/bacula/scripts/btraceback.gdb
the GDB command batch used to output a stack trace
AUTHOR
This manual page was written by Lucas B. Cohen <lbc@members.fsf.org>
SEE ALSO bsmtp(1)Kern Sibbald 6 December 2009 BTRACEBACK(1)