help with IPC + thread Post: 302705173

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Ipc

I have a parent that is passing data to child A and then child A has to process it and pass to child B. I am able to pass the data to child A but am not able to pass it to child B. Child B seems to only be receiving the last data instead of the whole data. I saw one example in a book but it uses...

2. Programming

How to cancel a thread safely from the initial thread?

how about asynchronous canceling? or with signal? if with signal whether it effects the process? my english so badly :( :(

3. Solaris

errors on Netra-440: "IPC Warning: ipc: tcp_protocol: bad magic number"

I was asked to look into a problem with a Sun Netra 440 in another department. On the server in question, the relevant 'uname -a' information is, "SunOS host1 5.9 Generic_118558-16 sun4u sparc SUNW,Netra-440". That information aside, while the other admin is logged into the ALOM, these errors are...

4. Programming

IPC Mechanisms

Hi! I wanted to know the advantages / disadvantages of different IPC mechanims such as sockets, pipes (unnamed) , shared memory & message queues. Pipes for example i hear are fast , but are difficult to debug as compared to sockets. Can you guys please name some situations where one is...

5. Programming

Best IPC mechanism to be used

Suppose I have 5 independent process divided in two imaginay sets: set1 set2 --------------------- p1 p3 | | p2 p4 | p5 The processes inside each set communicate mutually quite often. I mean p1 and p2 communicate mutually quite often Similarly p3, p4 and p5 communicate mutually...

LEARN ABOUT DEBIAN

colorgccrc

COLORGCCRC(5)							File Formats Manual						     COLORGCCRC(5)

NAME

       colorgccrc - configuration file for colorgcc

DESCRIPTION

       A colorgccrc configuration file is used to configure the highlighting of the compiler output from colorgcc.

SYNTAX

       Each  line  consists  of  a  keyword  designating  a configuration variable.  The keyword is followed by `:' and then one or several values
       (depending on the keyword).  Lines beginning with a hash mark `#' are comments.

CONFIGURATION VARIABLES

       g++ | gcc | c++ | cc | g77 | gcj | gnat | gpc
	      Specifies the paths to the compilers.  Takes one value; a path to the compiler.

       nocolor
	      Specifies what terminal types colorization should be disabled on.  Takes one or several values, separated by whitespace.

       srcColor
	      Specifies the highlighting attributes source-code should be given.  Takes one or several color attributes.  See  the  section  COLOR
	      ATTRIBUTES for more information.

       introColor
	      Specifies  the  highlighting  attributes	for normal compiler output.  Takes one or several color attributes.  See the section COLOR
	      ATTRIBUTES for more information.

       warningFileNameColor | errorFileNameColor
	      Specifies the highlighting attributes for the filename in a  warning  or	an  error,  respectively.   Takes  one	or  several  color
	      attributes.  See the section COLOR ATTRIBUTES for more information.

       warningNumberColor | errorNumberColor
	      Specifies  the  highlighting  attributes	for  the  line-number  in a warning or an error, respectively.	Takes one or several color
	      attributes.  See the section COLOR ATTRIBUTES for more information.

       warningMessageColor | errorMessageColor
	      Specifies the highlighting attributes for the message-text in a warning or an error,  respectively.   Takes  one	or  several  color
	      attributes.  See the section COLOR ATTRIBUTES for more information.

COLOR ATTRIBUTES

       The following attributes are valid for highlighting.

       clear, reset

       bold, underline, underscore, blink, reverse, concealed

       black, red, green, yellow, blue, magenta, cyan, white

       on_black, on_red, on_green, on_yellow, on_blue, on_magenta, on_cyan, on_white

SEE ALSO

       gcc(1), colorgcc(1)

HISTORY

       Jan 15 2003: Initial version of this manual-page.

REPORTING BUGS

       Report bugs to <jmoyers@geeks.com>

AUTHORS

       Jamie Moyers <jmoyers@geeks.com> is the author of colorgcc.

       This  manual  page  was	written  by Joe Wreschnig <piman@sacredchao.net>, and modified by David Weinehall <tao@debian.org>, for the Debian
       GNU/Linux system (but may be used by others).

COPYRIGHT

       Copyright (C) 2003 Jamie Moyers
       This is free software; see the source for copying conditions.  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
       LAR PURPOSE.

								   Jan 15, 2003 						     COLORGCCRC(5)