10-22-2004
You can always narrow down the issue by removing the variable that contains the bc command. If you dont get an error then that pretty well identifies that the variable is the issue.
Try this:
$(echo "scale=1; $intTotalPaidBreak/60" | bc)
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
The following C++ code segment is not working in debug mode build on HP-UNIX machine. It is not printing "Hello World" message on the screen. While it is working fine in release mode build.
==============================================
class KLogStreamBuf : public streambuf {
public:... (0 Replies)
Discussion started by: heena
0 Replies
2. Shell Programming and Scripting
When I run a lengthy script in debug mode i need to capture all the steps which are executed.
e.g
ksh -x script.ksh
+ test -f /proc/mounts
+ /bin/ls -l /proc/21326/exe
+ is=ksh
+ test ksh = ksh
+ test -s /etc/ksh.kshrc
+ . /etc/ksh.kshrc
+ trap 1 2 3
+ who am i
+ awk {print $1}
+... (2 Replies)
Discussion started by: zooby
2 Replies
3. AIX
Is there a way I can execute an installp command in debug mode, so that I can see whats happening when a fileset is being installed or updated? (What files are being replace etc etc).
I have an installp command failing for unknown reason. (7 Replies)
Discussion started by: balaji_prk
7 Replies
4. Red Hat
I have a little dell running redhat server. it's getting ethernet traffic to console and /var/log/messages (up 60Mb) i can't seem to find where to turn it off!
any help would be greatly appreciated.
here's syslog:
here's a snip from the log:
Sep 28 21:34:08 zgarch_serv kernel: IN=eth0... (2 Replies)
Discussion started by: toferloafer
2 Replies
5. Programming
Hi,
I'm using the following commands to execute a proc file, but I'm unable to debug the program. What modifications do I need to make in the command options to debug the program created.
I have a proc1.pc file, using the following three steps to generate the proc1 exe. After the proc1 exe... (2 Replies)
Discussion started by: ehari
2 Replies
6. Shell Programming and Scripting
Is there a way to see or print a sub code?
Sometime a sub could be already defined, but in the debug mode (so, interactively) it could be already out of screen.
So, I would think about a way to check if the sub is defined (just 'defined' is not a problem) and how it is defined.
Also, if... (4 Replies)
Discussion started by: alex_5161
4 Replies
7. Programming
Is there any possibility of running the PHP script in a debug mode ?
If so, do i have to download any package? Any free downloads available?
Can anyone please guide me through? Am a newbie in PHP scripting.
Thanks in Advance! (1 Reply)
Discussion started by: vidhyaS
1 Replies
8. Shell Programming and Scripting
I have a shell program which calls a perl program.
I am running the shell program with command;
$ ksh -x <prog_name>
Inside the shell program, I am calling perl with warnings.
I want to capture the entire output as it comes on screen.
The command I tried is:
$ ksh -x... (1 Reply)
Discussion started by: som.nitk
1 Replies
LEARN ABOUT DEBIAN
ditrack
DITRACK(1) General Commands Manual DITRACK(1)
NAME
dt - DITrack command line client tool
SYNOPSIS
dt command [options] [args]
dt-createdb repository-url issue-db-dir local-wc
dt-upgrade-0.7-db issue-db-dir
OVERVIEW
DITrack is a free, open source, lightweight, distributed issue (bug, defect, ticket) tracking system using a Subversion repository instead
of a backend database. It is written in Python and runs in UNIX environment (*BSD, Linux, MacOS X).
The project is inspired by the idea of Subissue issue tracking system.
However, while Subissue aims in merely replacing the traditional database storage with Subversion repository, DITrack is a major rethought
of the issue tracking system paradigm. The main difference is that instead of sticking to the centralized model (one database, one web
interface, one mail integration machinery), DITrack treats underlying Subversion storage as a versioned distributed file system which
enables benefits of truly distributed operation mode.
For more information about the DITrack project, visit http://www.ditrack.org.
Documentation for DITrack and its tools, including detailed usage explanations of the dt and dt-createdb programs, can be found at
/usr/share/doc/ditrack/html/index.html.
Run `dt help' to access the built-in tool documentation.
Automatic upgrade is possible for databases created by DITrack 0.7. If you are upgrading from previous version of DITrack, use the upgrage
utility from DITrack 0.7 first.
To upgrade a database run the dt-upgrade-0.7-db script, passing the database path as the argument, like:
dt-upgrade-0.7-db /home/user/ditrack-database
The upgrade procedure merely modifies the working copy (nothing gets committed to the repository). So, when done, you should commit the
changes manually.
April 2007 DITRACK(1)