10-03-2010
Sounds like a network problem then.
The busintr shouldn't make any difference.
I would suspect the problem network is not enabled for large send.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I wrote a script to test many systems to see if they are up or not. if a system is down, i am notified by email
now, most of the time,when systems are down in my enviroment, it is because the user accidentally or purposely (not knowing the consequences) hit the power button. so these problems... (3 Replies)
Discussion started by: TRUEST
3 Replies
2. Shell Programming and Scripting
Hi all,
I'm trying to write a shell script that will ping a site and and write the date and 1 or 0 (for success or no success) to a file.
it looks roughly like this:
#/bin/sh
set mydate = `date`
set myvar = `ping -c 1 hostname | grep -c "100%"`
if ($myvar == 1) then
echo... (1 Reply)
Discussion started by: TylerDurden
1 Replies
3. UNIX for Dummies Questions & Answers
I can ping by ip address but not by host name
everything is on the same subnet
check all of the normal files
I can telnet in to the unix box but can not open a connect to
the share dir.
unix ver sunSO 5.9
all the other computers ar Windows XP (with firewall turn off)
Thanks... (1 Reply)
Discussion started by: vviscomi
1 Replies
4. UNIX for Dummies Questions & Answers
I want to access window file system through Samba. when i ping Window machine through linux machine it connect, but in reverse case it shows "Request time out". could any one suggest what problem may be. (1 Reply)
Discussion started by: sonirajesh
1 Replies
5. IP Networking
Comp1=192.168.100.2
Comp2=192.168.100.6
both the comp have win2000 Os.
Using Cross cable i have connected back to Back.
When i ping From Comp1 to Comp2 its working fine.
But
When i ping From Comp2 to Comp1 its not working.
I know don't know what went wrong please help me out.... (4 Replies)
Discussion started by: ashokmeti
4 Replies
6. Solaris
Can someone tell me how I can get the following bolded output without having to issue the control C key when a ping is running?
ping -s cca-wl6
PING cca-wl6: 56 data bytes
64 bytes from cca-wl6: icmp_seq=0. time=0.796 ms
64 bytes from cca-wl6: icmp_seq=1. time=0.581 ms
64 bytes from... (5 Replies)
Discussion started by: SkySmart
5 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I have a list of 500 IP address and need to ping all the IP address. I had written a script to do this and its working if the IP is valid one. If any invalid IP present, the process got hang up.
Also I have tried with -c , -I and -w options, its not working.
Any one help me on this... (2 Replies)
Discussion started by: Rksiva
2 Replies
8. Solaris
Hi friends,
I am running Solaris 10, which is connected to a DSL router running DHCP. During the installation I chose not to use DHCP and assigned a permanent IP address to solaris machine. I also did not choose any name service as well. The rest of the details are as under.
Solaris Machine
IP... (4 Replies)
Discussion started by: gabam
4 Replies
9. HP-UX
I am having a problem with a new server build that has got me completely baffled. This server has a private back end network so the way it is supposed to work is that the server thinks its ip address is 10.131.0.48 but the rest of the world knows it as 199.68.100.100 per DNS. It has to be this way... (2 Replies)
Discussion started by: keelba
2 Replies
10. Shell Programming and Scripting
How can I get the following result of the "ping" command?
Example:
root@OpenWrt:~# ping google.com -c1 | sed -n 1p
PING google.com (216.58.210.14): 56 data bytes
How can I get the data only in the range of ()?
The result of what I want to get it:
216.58.210.14
Please use code... (4 Replies)
Discussion started by: andrewxxx
4 Replies
LEARN ABOUT MOJAVE
tcl_mem_debug
TCL_MEM_DEBUG(3) Tcl Library Procedures TCL_MEM_DEBUG(3)
__________________________________________________________________________________________________________________________________________________
NAME
TCL_MEM_DEBUG - Compile-time flag to enable Tcl memory debugging
_________________________________________________________________
DESCRIPTION
When Tcl is compiled with TCL_MEM_DEBUG defined, a powerful set of memory debugging aids is included in the compiled binary. This includes
C and Tcl functions which can aid with debugging memory leaks, memory allocation overruns, and other memory related errors.
ENABLING MEMORY DEBUGGING
To enable memory debugging, Tcl should be recompiled from scratch with TCL_MEM_DEBUG defined (e.g. by passing the --enable-symbols=mem flag
to the configure script when building). This will also compile in a non-stub version of Tcl_InitMemory to add the memory command to Tcl.
TCL_MEM_DEBUG must be either left defined for all modules or undefined for all modules that are going to be linked together. If they are
not, link errors will occur, with either Tcl_DbCkfree and Tcl_DbCkalloc or Tcl_Ckalloc and Tcl_Ckfree being undefined.
Once memory debugging support has been compiled into Tcl, the C functions Tcl_ValidateAllMemory, and Tcl_DumpActiveMemory, and the Tcl mem-
ory command can be used to validate and examine memory usage.
GUARD ZONES
When memory debugging is enabled, whenever a call to ckalloc is made, slightly more memory than requested is allocated so the memory debug-
ging code can keep track of the allocated memory, and eight-byte "guard zones" are placed in front of and behind the space that will be
returned to the caller. (The sizes of the guard zones are defined by the C #define LOW_GUARD_SIZE and #define HIGH_GUARD_SIZE in the file
generic/tclCkalloc.c -- it can be extended if you suspect large overwrite problems, at some cost in performance.) A known pattern is writ-
ten into the guard zones and, on a call to ckfree, the guard zones of the space being freed are checked to see if either zone has been mod-
ified in any way. If one has been, the guard bytes and their new contents are identified, and a "low guard failed" or "high guard failed"
message is issued. The "guard failed" message includes the address of the memory packet and the file name and line number of the code that
called ckfree. This allows you to detect the common sorts of one-off problems, where not enough space was allocated to contain the data
written, for example.
DEBUGGING DIFFICULT MEMORY CORRUPTION PROBLEMS
Normally, Tcl compiled with memory debugging enabled will make it easy to isolate a corruption problem. Turning on memory validation with
the memory command can help isolate difficult problems. If you suspect (or know) that corruption is occurring before the Tcl interpreter
comes up far enough for you to issue commands, you can set MEM_VALIDATE define, recompile tclCkalloc.c and rebuild Tcl. This will enable
memory validation from the first call to ckalloc, again, at a large performance impact.
If you are desperate and validating memory on every call to ckalloc and ckfree is not enough, you can explicitly call Tcl_ValidateAllMemory
directly at any point. It takes a char * and an int which are normally the filename and line number of the caller, but they can actually
be anything you want. Remember to remove the calls after you find the problem.
SEE ALSO
ckalloc, memory, Tcl_ValidateAllMemory, Tcl_DumpActiveMemory
KEYWORDS
memory, debug
Tcl 8.1 TCL_MEM_DEBUG(3)