09-12-2007
What is the need for "p" after myfifo? what is it meant for?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi I am having trouble with a script to export individual schemas to tape from an oracle database. Basicaly I need to export each shema through a pipe with compression and store each shema name in a file with the relevant tape marker. (4 Replies)
Discussion started by: truma1
4 Replies
2. Filesystems, Disks and Memory
Hello!
How I can increase or decrease predefined pipe buffer size?
System FreeBSD 4.9 and RedHat Linux 9.0
Thanks! (1 Reply)
Discussion started by: Jus
1 Replies
3. Shell Programming and Scripting
Hi...Can anyone please guide me on FIFO Pipes in UNIX.I have lerant things like creating fifo pipes,using them for reads and writes etc.I want to know what is the maximum amount of memory that such a pipe may have? Also can anyone guide me on where to get info on this topic from? (1 Reply)
Discussion started by: tej.buch
1 Replies
4. UNIX for Advanced & Expert Users
The following code does not work (zsh, Solaris), but works without the first line (files instead of pipes) :confused:
mkfifo p1 p2
echo "Hello" | tee p1 > p2 &
paste p1 p2
I would high appreciate any help to fix it. (9 Replies)
Discussion started by: zzol
9 Replies
5. HP-UX
Hi,
Please help me on this.
I am creating a named pipe in a kshell script.
I am using mkfifo pipe_name command to create the pipe.
I want to remove the named pipe after my work is completed.
How can i do that. (8 Replies)
Discussion started by: chintapalli001
8 Replies
6. UNIX for Dummies Questions & Answers
hi,
i am working on a script for oracle export, m using a parameter file...
i want to compress the dump file that is generated..
in my script following is the code i have written.
i am not able to generata .gz file
mknod /tmp/exp_tesd1_pipe p
gzip -cNf... (4 Replies)
Discussion started by: saharookiedba
4 Replies
7. Shell Programming and Scripting
Tried the following on Hpux 11.11, using both ksh, and dtksh
$diff <(sort file1) <(sort file2)
$ ksh: syntax error: `(' unexpected
Strange thing is I tried the same command under RHEL5 using ksh 93 and it works fine. Does anyone know if this is possible on HPUX without the use of... (0 Replies)
Discussion started by: fire!
0 Replies
8. UNIX for Advanced & Expert Users
I'm not sure whether or not this question really belongs in this forum and will accept rebuke should I have mistakenly put it in the wrong place (hopefully the rebuke will be accompanied by an answer, though)
I wish to implement named pipe communication between two process using MKS Toolkit. I... (2 Replies)
Discussion started by: ArndW
2 Replies
9. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Write a C program to search the current directory for all pipes.
1. It will print the pipe... (2 Replies)
Discussion started by: natwickley
2 Replies
10. Shell Programming and Scripting
Dear community,
I communicate with an external program (maxima) using named pipes. If I use a text file to capture the output (maxima > out.txt) i can see the programs answer directly after the input written into the file. But if bypass the output into a named pipe (maxima > pipe) and capture it... (1 Reply)
Discussion started by: Pustekuchen
1 Replies
LEARN ABOUT DEBIAN
log::agent::tag
Agent::Tag(3pm) User Contributed Perl Documentation Agent::Tag(3pm)
NAME
Log::Agent::Tag - formats caller information
SYNOPSIS
Intended to be inherited from
DESCRIPTION
This class is meant to be inherited by all the classes implementing a log message tag.
A message tag is a little string that is either appended or prepended to all log messages.
For instance, and oversimplifying a bit, a tag meant to be prepended will be inserted in front of the current log message, separated by
separator, which defaults to a single space:
+------------+-----------+---------------------------------+
| tag string | separator | current log message |
+------------+-----------+---------------------------------+
This operation is called tag insertion. The whole string then becomes the current log message, and can be the target of another tag
insertion.
The reality is a little bit more complex, to allow successive tags to be prepended or appended in the order they are specified, and not in
reverse order as they would be if naively implemented. See Log::Agent::Message for the exact semantics of append() and prepend()
operations.
FEATURES
This section documents the interface provided to heirs, in case you wish to implement your own tag class.
_init(name, postfix, separator)
Initialization routine that should be called by all heirs during creation to initialize the common attributes.
postfix
When true, the tag is meant to be appended to the log message. Otherwise, it is prepended.
name
The name of this tag. It is meant to provide by-name access to tags, check whether a given tag is recorded, etc... The names "caller"
and "priority" are architecturally defined to refer to "Log::Agent::Tag::Caller" and "Log::Agent::Tag::Priority" objects.
NOTE: Currently unused by any client code.
separator
The sperating string inserted between the tag and the log message. It defaults to " " if not specified, i.e. left to "undef" when
calling _init().
string()
A deferred routine, to be implemented by heirs.
Returns the tag string only, without the separator, since its exact placement depends on the value of the "postfix" attribute.
insert(message)
Insert this tag withing the "Log::Agent::Message" message, according to the tag specifications (placement, separator). Calls string()
to produce the tag string.
This routine is frozen and should not be redefined by heirs.
STANDARD TAGGING CLASSES
Tagging classes define via their "string()" routine what is the string to be used as a tag. The insertion of the tag within the log
message is done via a frozen routine from the "Log::Agent::Tag" ancestor.
The following classes are provided by "Log::Agent":
"Log::Agent::Tag::Callback"
The "string()" routine invokes a user-supplied callback, given as a "Callback" object. You need the Callback module from CPAN if you
wish to use this class.
"Log::Agent::Tag::Caller"
Used internally to compute the caller and format it according to user specifications.
"Log::Agent::Tag::Priority"
Used internally to format message priorities and add them to the log messages.
"Log::Agent::Tag::String"
Defines a constant tagging string that should be added in all the log messages, e.g. a web session ID.
AUTHOR
Raphael Manfredi <Raphael_Manfredi@pobox.com>
SEE ALSO
Log::Agent::Message(3).
perl v5.10.0 2002-03-09 Agent::Tag(3pm)