similar to: Extremely long creat64 latencies on higly

Hi, About a year and a half ago, Hank Leininger posted a plea to this list for the inclusion of an Include directive in OpenSSH's configuration file. Hank's suggestion is detailed and thorough enough IMHO, so instead of repeating it I'll link it here http://marc.info/?l=openssh-unix-dev&m=118236823907002&w=2 . I'm also interested in this feature, and though my C

On Apr 18, 2007, at 6:44 AM, Yaniv Aknin wrote: > Hello, > > I''d like to plan a storage solution for a system currently in > production. > > The system''s storage is based on code which writes many files to > the file system, with overall storage needs currently around 40TB > and expected to reach hundreds of TBs. The average file size of the >

Hi all, I have questions about something I observed just now: 1) on AMD64, S10u1: # dtrace -n ''fbt::copystr:entry{printf ("%p\n", args[0]);}'' -c /bin/pwd dtrace: invalid probe specifier fbt::copystr:entry{printf ("%p\n", args[0]);}: in action list: index 0 is out of range for fbt::copystr:entry args[ ] but # dtrace -n ''fbt::copystr:entry{printf

OK, I''ve been fritzing around with something I noticed last night, thinking that I understood what was going on, but now it''s getting confusing again. A system that has been running for a couple of months had a hole in the probe ID list near the end in the middle of the fbt probes. And then a couple of syscall probes were stuck in the hole. It looked like this: ... 40311

Hi, I work for a company which develops a rather complicated Linux-based grid-technology appliance. The appliance is made of several Linux hosts, exposing its functionality over a proprietary CLI-like protocol. This protocol currently works by running a proprietary client executable on a host, sending the command via TCP/IP to one of the appliance's hosts and receiving the response. The

Whilst trying out some D to get an insight into what is the most common reason for a given function to return, I have bumped into an error I don''t understand. The first take on what I was trying to do was: # dtrace -n ''fbt:ip:ip_input:return{@home[arg0] = count();}'' and all was well. The next step was: # dtrace -n

Hi, I'd like to argue in favor of bug #877 ( https://bugzilla.mindrot.org/show_bug.cgi?id=877) from a new perspective. Instead of performance, I wish to raise the issue of regulatory compliance and auditing. I read all of #877 and I understand the arguments for and against, but I felt at the end the decisive comment by Damien was mostly based on 'We don't want users to use

Hi, Sometimes it's desirable to bind a port forward to port 0: especially when scripting port forwarding, and more especially so with the '-f -N' options. The version of OpenSSH bundled with OSX (4.7p1) accepts '-L 0:192.168.1.1:22', but only if ran as root (I guess this was more an accident than a feature). I saw that the current version (5.1p1) will decline such an options,

Hi, I''ve a b81 server running for a while. I''ve done all sorts of Python related stuff on it (nothing amazing, mostly compiled python2.5 and iPython in /usr/local), and now am trying to use it with xVM to install Windows on a virtual machine in it. I''m having trouble creating the new machine, and I get a blank error response like so when I try to do it:

Hey, Do you guys think that is a good idea to have a manual page for each provider with a complete description of what probes are offered ? Found some already under 7D category: dtrace dtrace (7d) - DTrace dynamic tracing facility fasttrap fasttrap (7d) - DTrace user instruction tracing provider fbt fbt (7d) - DTrace function boundary tracing provider

Referring to the DTrace manual: "Module If this probe corresponds to a specific program location, the name of the module in which the probe is located. This name is either the name of a kernel module or the name of a user library. Function If this probe corresponds to a specific program location, the name of the program function in which the probe is located." and then ...

what is differenct between syscall::write:entry fbt::write:entry are the two probe fires at the same place. -- This message posted from opensolaris.org

I have a number of systems running solaris10 and i see the package and binary for dtrace installed however whenever we try to run anything we get this error dtrace: failed to initialize dtrace: DTrace device not available on system the only system in which i dont have this error is the development server that has the full solaris 10 install while others are minimized, do i need additional

I wrote a simple c programme and do some dtrace test. the progromme shows below(write.c): /////////////////////////////// #include<stdio.h> #include <sys/types.h> #include <sys/stat.h> #include <fcntl.h> char *value="hello,my name is wanjm\n"; void main() { int fd; fd=open("/export/home/wanjm/temp/read.txt",O_RDWR|O_CREAT); while(1) {

i am doing reads and writes to /dev/rdsk/c0t2d0s4 using dtrace to see how much time it took for ssdread and ssdwrite. It shows very small number 4 or 5. #pragma D option flowindent syscall::pread:entry { self->trace = 1; self->size = arg2; } syscall::pwrite:entry { self->trace = 1; self->size = arg2; } fbt:ssd:ssdread:entry /self->trace/ { self->start = timestamp;

Hello all, I saw this question about a year back in the archive[1], but with no final answer. I would like to trace shmget calls and also get the id of the shared memory segment. That script looked like[2], but we dont get the id since arg1 is the errno value. How do i access the shm id, i would need this to debug a customer problem but i don''t have time to learn it the hard

What is causing this error: dtrace: processing aborted: Abort due to systemic unresponsiveness It happens to my script which shows all the NFS operations coming through common_dispatch() on a server. I wasn''t the one running the test, so I don''t know how long it ran before it died. The script uses a couple of static probes and a couple fbt. Thanks, jim -------------- next

Hi, Following "anonymous tracing" chapter, I wanna trace kmem_init(), but after reboot, I can''t get anything, why? Here is my short script kmem_init.d: #!/usr/sbin/dtrace -s fbt::kmem_init:entry { stack(); } then I just use: #dtrace -AFs kmem_init.d #reboot #dtrace -ae < got nothing here> Thanks, -Alex This message posted from opensolaris.org

I''m using a fbt probe where I get a system call id as an argument, how do I look up the name of it? At the moment I''m post-processing the output using /etc/name/to_sysnum but that doesn''t feel right :) cheers, /Martin -- This message posted from opensolaris.org

Is there a list anywhere of the DTrace FBT provider calls for each version of Solaris since the Nevada build that hosed the DTrace Toolkit. I have no issue with rewriting what I need, but I am hoping to stave off having to look at all the source code to find everything. I know there is a new provider under development, but I need to be able to program DTrace routines for all the updates in