very bizzare file writing problem Post: 302262387

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Bizzare (while statement)

I'm trying to use the while statement to increment a positive number, with a leading "0". when I pass it through, it seems to come out with a negative value, and all the increments remain negative. This is what I have: i=010986294184 j=010986988888 while ; do echo $i i=(($i + 1)) done...

2. UNIX for Dummies Questions & Answers

Problem writing file path to txt file

if test -z "$1" then echo "you must give a filename or filepath" else path=`dirname $1` f_name =`basename $1` if path="." then path=`pwd` fi fi cat $f_name $path >> index.txt The only problem I am encountering with this is writing $path to index.txt Keeps going gaga: cat:...

3. UNIX for Advanced & Expert Users

Problem while writing to a file...?

Hi, I have an issue with the file writing... It is, Suppose that if I am writing some data to a file... and at the same time another user has opened the file and want to write in to the file(writing to the file at the same time)...the another has to know that someone has opened the file, mean...

4. Shell Programming and Scripting

Problem in writing the data to a file in one row

5. IP Networking

Bizzare network attack?

A server I host is having very rare glitches where a file the user downloads will have incorrect contents. This almost never happens when I am looking, I caught it once and only once -- a user messaged me saying his antivirus had given him a warning about an image file downloaded from his...

6. Shell Programming and Scripting

help with counting processes, bizzare behavior

I have a ksh script (dtksh Version M-12/28/93d on Solaris 10) that is run daily by cron and sometime hangs forever. I need to detect if there is an old copy hung before I start the new run, and if so send an email and exit the script. Here is part of the code: #!/usr/dt/bin/dtksh...

7. UNIX for Advanced & Expert Users

Bizzare TCP/IP problem

Hi all. I have a really really weird problem that I've been working on for days. The problem manifested as users cannot connect to our web servers via SSH when they're using our wireless network. Here's where it gets weird: - Clients from anywhere other than the wireless subnet can...

8. Programming

Bizzare optimization problem

I have a C program that, for the life of me, I can't see any possible stack corruption in but for some reason corrupts a local variable to 0 when not referenced. My compiler is gcc 4.3.4. But my question's not really a code question, it's a compiler question. The glitch is weirdly specific: ...

9. Shell Programming and Scripting

Problem with writing into a file through shell script

Hi all, I have a shell script which I use to login to the server from the client and then from the server I run a bunch of other scripts to complete my task. I am having problems with the script below- #!/bin/bash while read line do connections=`echo $line | cut -d " " -f 1` period=`echo...

10. Shell Programming and Scripting

Bizzare behavior on redirect of stdout

Oracle Linux 5.6 64-bit (derivative of RHEL) Dear Ann Landers, This is about as bizarre as anything I've ever seen. I have a little test script I've been working with. When I redirect stdout to a file, no file. Make a copy of the script to another name. Execute it and redirect stdout, and...

LEARN ABOUT FREEBSD

kgdb

KGDB(1) 						    BSD General Commands Manual 						   KGDB(1)

NAME

     kgdb -- kernel debugger

SYNOPSIS

     kgdb [-a | -f | -fullname] [-b rate] [-q | -quiet] [-v] [-w] [-d crashdir] [-c core | -n dumpnr | -r device] [kernel [core]]

DESCRIPTION

     The kgdb utility is a debugger based on gdb(1) that allows debugging of kernel core files.

     The options are as follows:

     -a 	  Increase the annotation level.  An annotation level of 1 features the historical -fullname option of gdb(1).	This is useful
		  when running kgdb in Emacs.  The -f or -fullname options are supported for backward compatibility as well.

     -b rate	  Set the baudrate to rate.

     -q 	  Suppress printing of the banner when the debugger starts.  The -quiet form is supported for compatibility as well.

     -v 	  Increase verbosity.

     -w 	  Opens kmem-based targets in read-write mode.	(This is identical to what --wcore used to do in previous gdb versions for
		  FreeBSD.)

     -d crashdir  Use crashdir instead of the default, /var/crash to locate kernel core dump files in.	The name vmcore. plus the dump number will
		  be appended to determine the actual dump file name.

     -c core	  Explicitly use core as the core dump file.

     -n dumpnr	  Use the kernel core dump file numbered dumpnr for debugging.

     -r device	  Use device to connect kgdb to for a remote debugging session.

     The -c, -n, and -r options are mutually exclusive.

     Optionally, the name of the kernel symbol file and the name of the core dump file can be supplied on the command-line as positional argu-
     ments.  If no kernel symbol file name has been given, the symbol file of the currently running kernel will be used.  If no core dump file has
     been specified through either of the options or the last command-line argument, /dev/mem will be opened to allow debugging the currently run-
     ning kernel.

FILES

     /dev/mem	 Default memory image to open if no core dump file has been specified.

     /var/crash  Default directory to locate kernel core dump files.

SEE ALSO

     gdb(1)

HISTORY

     The kgdb utility first appeared in its current form in FreeBSD 5.3.

BSD
								 October 11, 2006							       BSD