about HP-UX error exa_parm mismatch?

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Find Syllable count mismatch

Hello, I have written a syllable splitter for Pseudo English and Indic. I have a large database with the following structure Syllables in Pseudo English delimited by |=Syllables in Devanagari delimited by | The tool produces syllables in both scripts. An example is given below: ...

2. Shell Programming and Scripting

Need fix for rsync Error due to version mismatch

rsync --delay-updates -F --compress --archive --rsh='/usr/bin/ssh -t -a -x' /web/admin/Transfer/data/ user1@destserver1:/tmp/testf rsync version on sender server is:3.0.9 rsync version on sender server is:3.0.6 Linux sourceserver1 3.10.0-693.17.1.el7.x86_64 #1 SMP Sun Jan 14 10:36:03 EST...

3. Programming

Warning: pointer type mismatch

Hi all, I'm new programming in C, so I had the next message in my code: Dual.c:88:20: warning: pointer type mismatch in conditional expression : &clientSa.sin6.sin6.sin6_addr, Any help would be great #include <sys/socket.h> #include <netinet/in.h> #include <arpa/inet.h> #include...

4. Shell Programming and Scripting

Count mismatch in UNIX

Hi, I have a requirement like below. client is sending the .txt filles.In that file we have 10 records but when I execute the below command it is showing 9 records. klena20> wc -l sample_file.txt|awk '{print $1}' It is showing the output as 9 But in a file records are 10. I found...

5. UNIX for Dummies Questions & Answers

Ownership mismatch from solaris to linux

Hi all, I have NFS share that is being mounted on both solaris10 and RHEL5. The ownership of files is right on solaris box but not on RHEL5 box. I logged in as root and when i try to change ownership with group, i am getting following error. chown -R oracle dba <filename> chown:...

6. Ubuntu

device size mismatch after mounting

Hi, I have a created a logical partition sda5 in ubuntu server 9.0.4. which is Disk /dev/sda: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00053d78 Device Boot Start End ...

7. Shell Programming and Scripting

To find String mismatch

Hi, I have a doubt when searching files for the existence of a particular key. I have a property file has data with key and value pair like below and i call it as property file.ini here are the contents in File: popertyfile.ini location.property=2 agent.method=begin newkey=23 ...

8. UNIX for Dummies Questions & Answers

Interesting date/ps time mismatch

# date;ps -ef|grep confused. Tue Dec 13 11:11:22 EST 2005 root 12847 12733 0 11:21 pts/83 00:00:00 grep confused. I am really confused on why my ps and my date command are returning different values for the time. Anyone know how to resolve this? Running FC2, if it helps.

9. Solaris

X Keyboard Extension version mismatch

I want to use calls from the X Keyboard Extension, but get "library version mismatch" error. First one is XkbLibraryVersion(..). This one already returns false. Then I call XkbOpenDisplay(...) which does not return a valid display; return value is XkbOD_NonXkbServer. If I open the display with...

LEARN ABOUT DEBIAN

tangram::complicity

Tangram::Complicity(3pm)				User Contributed Perl Documentation				  Tangram::Complicity(3pm)

NAME

       Tangram::Complicity - How to make Tangram-friendly classes

SYNOPSIS

	 package YourNastyXSClass;

	 sub px_freeze {
	     return [ (shift)->gimme_as_perl ];
	 }

	 sub px_thaw {
	     my $class = shift;
	     my $self = $class->new( @_ );
	 }

	 1;

DESCRIPTION

       Tangram::Complicity does not exist.  To make matters worse, it isn't even implemented.  This page is a big FIXME for the code it refers to.
       This page merely documents the API that classes must implement to be safely stored by "Tangram::Type::Dump::flatten".

       Note that to avoid unnecessary copying of memory structures from A to B, this method operates "in-place".

       So, therefore it is necessary for the reference type used in the return value, to be the same as the one in the real object.  This is
       explained later under "reftype mismatch".

       So - for instance, for Set::Object objects, which have a "px_freeze" method of:

	 sub px_freeze {
	     my $self = shift;
	     return $self->members;
	 }

	 sub px_thaw {
	     my $class = shift;
	     return $class->new(@_);
	 }

       [ note: This differs from the Storable API ("STORABLE_freeze" and "STORABLE_thaw").  This interface is actually reasonably sane - the
       Storable API required custom XS magic for Set::Object, for instance.  Which has been implemented, but we've learned the lesson now :) ]

       In essence, the "px_freeze" method means "marshall yourself to pure Perl data types".  Note that different serialisation tools will treat
       ties, overload and magic remaining on the structure in their own way - so, create your own type of magic (a la Pixie::Info) if you really
       want to hang out-of-band information off them.

       reftype mismatch

       If you get a "reftype mismatch" error, it is because your YourClass->px_thaw function returned a different type of reference than the one
       that was passed to store to YourClass->px_freeze.

       This restriction only applies to the return value of the constructor "px_thaw", so this is usually fine.  The return value from "px_freeze"
       will be wrapped in a (blessed) container of the correct reference type, regardless of its return type.

       ie. your function is called as:

	  %{ $object } = %{ YourClass->px_thaw(@icicle) };

	  @{ $object } = @{ YourClass->px_thaw(@icicle) };

	  ${ $object } = ${ YourClass->px_thaw(@icicle) };

	  *{ $object } = *{ YourClass->px_thaw(@icicle) };

	  my $tmp = YourClass->px_thaw(@icicle);
	  $object = sub { goto $tmp };

       This is an analogy, no temporary object is actually used in the scalar case, for instance; due to the use of tie.

       The reason for this is to allow for circular and back-references in the data structure; those references that point back point to the real
       blessed object, so to avoid the overhead of a two-pass algorithm, this restriction is made.  This is why the value is passed into
       STORABLE_thaw as $_[0].	For most people, it won't make a difference.

       However, it does have the nasty side effect that serialisers that can't handle all types of pure Perl data structures (such as, all current
       versions of YAML) are unable to store blessed scalars (eg, Set::Object's).

perl v5.8.8							    2006-03-29						  Tangram::Complicity(3pm)

HP-UX