8 More Discussions You Might Find Interesting
1. AIX
periodically my oracle 11.2.0.1 listener process 'tnslsnr' seems to crash and disappear ( I am using an AIX 6.1 unix platform ). When this happens I am able to restart my listener ok. However when this happens there is is no stop recorded in my listener log (as there normally would be - hence why I... (1 Reply)
Discussion started by: jimthompson
1 Replies
2. Shell Programming and Scripting
Hi,
I will ftp aroung 80 files after connecting to an FTP Server. But after 2 minutes of connection, it is timed out and connection is dying. Server had a 2 minute connection timeout if connection is idle. But my question, Isn't tranfering files not considered as an activity. Is the connection... (7 Replies)
Discussion started by: vasuarjula
7 Replies
3. Post Here to Contact Site Administrators and Moderators
First of all, I want to thank everyone who runs this forum for the fine job they've done. While I myself have not yet had any need for help, I have enjoyed and learned while helping others.
Due diligence disclaimer: I searched for a discussion on this issue, using "tynt" and "copy paste", but... (11 Replies)
Discussion started by: alister
11 Replies
4. Shell Programming and Scripting
I have a perl program that I want to read from a file passed as an argument or from a pipe. If their is no pipe or arguments, I want it to output a help message. I am stuck on how to prevent perl from reading from the keyboard if it isn't fed any file names or data from a pipe. The only things I... (4 Replies)
Discussion started by: ilikecows
4 Replies
5. Shell Programming and Scripting
two things.
why doesn't the 'die' message get displayed - "Error: release log directory creation failed..."?
why does the script name and line number get displayed despite the inclusion of a '\n'. apparently adding a newline prevents this from happening.
if (! -d "$logdir") {
use... (4 Replies)
Discussion started by: mjays
4 Replies
6. UNIX for Dummies Questions & Answers
I am using SunOS 5.7
I have installed Python 2.5 via make install
Without going into details, I'd like to uninstall it and replace it with an earlier version. Maybe as far back as 2.2.3. Unfortuantely, make uninstall gives me Don't know how to make target 'uninstall'. This is thematically... (2 Replies)
Discussion started by: Dbecker
2 Replies
7. Solaris
Hi there
I have a backup script that runs every night and for some reason ive been getting in in the morning and the process has died, Is there any way I can tell when it died? if not .....would anybody recommend some scripting that i could do that would be able to tell me this information
... (3 Replies)
Discussion started by: hcclnoodles
3 Replies
8. News, Links, Events and Announcements
Mods: Delete this if you think that this is not appropriate.
I found this rather amusing. If you go to www.unix.net now you will see the OpenGroup selling license plates that read "Live Free or Die/Unix/Unix is a trademark of the OpenGroup"
(http://www.unix.net/unix_plates.html)
I just... (12 Replies)
Discussion started by: auswipe
12 Replies
pddump(1) General Commands Manual pddump(1)
NAME
pddump - Dump profiling data files
SYNOPSIS
pddump file...
OPERANDS
A data file generated by a profiled program. A valid file is identified as a "profiling data file" by the file(1) command.
DESCRIPTION
The pddump command displays, on the standard output, the record definitions and data of the specified profiling data files.
Each file's dump is prefixed by the line "File = file:". This is followed by the file's field-alignment option and a list containing the
file's name/value attribute pairs and the file's record definitions. Then each record in the file is dumped, showing the name of the record
and the name and value of each of its fields.
Strings are printed within double quotes, unsigned integers are printed in hexadecimal, and signed integers and floating-point numbers are
printed in decimal. Non-array data lines contain equal signs to assist in filtering.
The content of the profiling data files produced by Tru64 UNIX may be expanded in future releases, but Tru64 UNIX tools will continue to
support older formats. To write tools that process Tru64 UNIX profiling data files, use the pdtostd(1) command to convert the Tru64 UNIX
formats to industry standard formats, where a standard format exists. Alternatively, use the libpdf.a utilities to read the profiling data
files directly, skipping any new attributes, records, or fields that may appear.
FILES
Library of routines for reading and writing profiling data files Header file for libpdf.a
SEE ALSO
Commands: atom(1), cc(1), file(1), kprofile(1), pdtostd(1), uprofile(1)
AtomTools: hiprof(5), pixie(5)
Programmer's Guide
pddump(1)
10-23-2005
RE: Are U mad ?
