Additionally, it looks like ulimit might be something a Sys Admin would use, not a developer like me. Is that correct?
So I think my best option, from the way it sounds, is to just use the kill dash-6 (SIGABRT) option. Thanks anyway everyone. I appreciate your suggestions.
~Marcus
Hi,
whenever I am giving a 'ls' command system is going into infinite loop displaying the current home directory.
There is no separate shell script/file with ls name anywhere in the system.
I am using Solaris 10.
Any help / guidance in solving this problem is highly appreciated.
... (3 Replies)
Hi guys, I'm having a problem getting my infinite loop to loop. It simply reads in the users choice form the menu, executes the corresponding case statement and quits instead of looping back to the main menu again. I have a feeling it might be something with my if then statements within the case... (2 Replies)
hi all,
this is how my scrip looks like
#!/bin/sh
bindir='/opt/apps/script/bin'
datadir='/opt/apps/script/data'
dir='/opt/apps/script'
while : ; do
ls -1rt /opt/apps/script/data/check.txt*|tail -1 > /dev/null 2>&1
if ;then
chmod +rwx $bindir/dummy2.sh
... (8 Replies)
I wanted to copy (not forward but copy) all incoming email to another address of mine. It worked, but now I encountered an infinite loop problem: When the second address doesn't like the content and bounces the message back, the bounce message will be sent back and forth.
So, what I have in... (1 Reply)
Hi All,
I need to run an infinite loop.
requirement below:
function1 --> creates a file file1
function2 ---> need to call if the file creates
i am running these both function via a script --> script.sh
i need to run the function1 first and if the file file1 creates then need to run the... (3 Replies)
1. The problem statement, all variables and given/known data:
My problem is an infinite loop when i press any other key other then Y or y in the while loop. what i want it to do is return to the normal script outside of it if pressing N or n or keep asking the same question if its any other... (4 Replies)
Hi, I was debating if I should put this in the dummies or scripts section, I apologize in advance if I chose poorly.
Fairly new to Unix and BASH scripting but I thought I made it fairly well given my limited understanding. However, the output indicates that it's looping and I'm ending up with a... (5 Replies)
Im unable to stop the below infinite loop (bash script). Can someone tell me why this isnt responding to signals eg: ctrl+c (SIGINT) or ctrl+z
c=0
test_loop() {
c=$(($c+1))
echo "count value is : $c "
sleep 1
test_loop
}
Im using: SunOS 5.10
PS: If run this as... (13 Replies)
Discussion started by: Arun_Linux
13 Replies
LEARN ABOUT OSX
dtruss
dtruss(1m) USER COMMANDS dtruss(1m)NAME
dtruss - process syscall details. Uses DTrace.
SYNOPSIS
dtruss [-acdeflhoLs] [-t syscall] { -p PID | -n name | command }
DESCRIPTION
dtruss prints details on process system calls. It is like a DTrace version of truss, and has been designed to be less intrusive than truss.
Of particular interest is the elapsed times and on cpu times, which can identify both system calls that are slow to complete, and those
which are consuming CPU cycles.
Since this uses DTrace, only users with root privileges can run this command.
OPTIONS -a print all details
-b bufsize
dynamic variable buffer size. Increase this if you notice dynamic variable drop errors. The default is "4m" for 4 megabytes per CPU.
-c print system call counts
-d print relative timestamps, us
-e print elapsed times, us
-f follow children as they are forked
-l force printing of pid/lwpid per line
-L don't print pid/lwpid per line
-n name
examine processes with this name
-o print on-cpu times, us
-s print stack backtraces
-p PID examine this PID
-t syscall
examine this syscall only
EXAMPLES
run and examine the "df -h" command
# dtruss df -h
examine PID 1871
# dtruss -p 1871
examine all processes called "tar"
# dtruss -n tar
run test.sh and follow children
# dtruss -f test.sh
run the "date" command and print elapsed and on cpu times,
# dtruss -eo date
FIELDS
PID/LWPID
Process ID / Lightweight Process ID
RELATIVE
relative timestamps to the start of the thread, us (microseconds)
ELAPSD elapsed time for this system call, us
CPU on-cpu time for this system call, us
SYSCALL(args)
system call name, with arguments (some may be evaluated)
DOCUMENTATION
See the DTraceToolkit for further documentation under the Docs directory. The DTraceToolkit docs may include full worked examples with ver-
bose descriptions explaining the output.
EXIT
dtruss will run forever until Ctrl-C is hit, or if a command was executed dtruss will finish when the command ends.
AUTHOR
Brendan Gregg [Sydney, Australia]
SEE ALSO procsystime(1M), dtrace(1M), truss(1)version 0.80 Jun 17, 2005 dtruss(1m)