[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [hobbit] beta6 - errors on AIX 4.3.3
- To: "'hobbit (at) hswn.dk'" <hobbit (at) hswn.dk>
- Subject: RE: [hobbit] beta6 - errors on AIX 4.3.3
- From: "Morris, Chris (Shared Services)" <CHRIS.MORRIS (at) RWEnpower.com>
- Date: Mon, 24 Jan 2005 13:03:45 -0000
The bb-hosts file is in /usr/local/hobbit/server/etc as it should be.
<<ftok.txt>>
Regards,
Chris
> -----Original Message-----
> From: Henrik Storner [SMTP:henrik (at) hswn.dk]
> Sent: Monday, January 24, 2005 12:51 PM
> To: hobbit (at) hswn.dk
> Subject: Re: [hobbit] beta6 - errors on AIX 4.3.3
>
> In <8511ED0A5A0ED61191A70002A58CA00705AC68B8 (at) trn2622.natpower.co.uk>
> "Morris, Chris (Shared Services)" <CHRIS.MORRIS (at) RWEnpower.com> writes:
>
> >Moved forward to beta6 on AIX 4.3.3 to see if shared memory problems were
> >fixed, but now get following in hobbitlauch.log :-
>
> >2005-01-24 12:11:23 Could not generate shmem key based on
> >/usr/local/hobbit/server/etc/bb-hosts: No such file or directory
> >2005-01-24 12:11:23 Cannot setup status channel
> >2005-01-24 12:11:23 Task hobbitd terminated, status 1
>
> OK, this actually corresponds nicely with the previous report where
> you had some strange shmem-regions with 0xffffffff as the key. Only
> difference is that now this error is caught and Hobbit refuses to run.
>
>
> Where is you bb-hosts file located ?
>
> "/usr/local/hobbit/server/etc/bb-hosts: No such file or directory"
>
> indicates that it isn't where hobbitd expects it to be, based on
> the BBHOSTS setting in hobbitserver.cfg.
>
>
> If your bb-hosts file really does exist with that filename, could
> you send me the AIX man-page for the "ftok" function (just dump the
> output of "man ftok" to a file and send it directly to me) ?
>
>
> Henrik
>
> To unsubscribe from the hobbit list, send an e-mail to
> hobbit-unsubscribe (at) hswn.dk
>
****************************************************************************
The information contained in this email is intended only for the use of the intended recipient at the email address to which it has been addressed. If the reader of this message is not an intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination or copying of the message or associated attachments is strictly prohibited.
If you have received this email in error, please contact the sender by return email or call 01793 877777 and ask for the sender and then delete it immediately from your system.Please note that neither RWE npower nor the sender accepts any responsibility for viruses and it is your responsibility to scan attachments (if any).
*****************************************************************************
-------------------------------------------------------------------------------
Base Operating System and Extensions Technical Reference, Volume 1
-------------------------------------------------------------------------------
ftok Subroutine
Purpose
Generates a standard interprocess communication key.
Library
Standard C Library (libc.a)
Syntax
#include <sys/types.h>
#include <sys/ipc.h>
key_t ftok (Path, ID)
char *Path;
int ID;
Description
Attention: If the Path parameter of the ftok subroutine names a file that
has been removed while keys still refer to it, the ftok subroutine returns
an error. If that file is then re-created, the ftok subroutine will probably
return a key different from the original one.
Attention: Each installation should define standards for forming keys. If
standards are not adhered to, unrelated processes may interfere with each
other's operation.
The ftok subroutine returns a key, based on the Path and ID parameters, to be
used to obtain interprocess communication identifiers. The ftok subroutine
returns the same key for linked files if called with the same ID parameter.
Different keys are returned for the same file if different ID parameters are
used.
All interprocess communication facilities require you to supply a key to the
msgget, semget, and shmget subroutines in order to obtain interprocess
communication identifiers. The ftok subroutine provides one method for creating
keys, but other methods are possible. For example, you can use the project ID as
the most significant byte of the key, and use the remaining portion as a
sequence number.
Parameters
Path Specifies the path name of an existing file that is accessible to the
process.
ID Specifies a character that uniquely identifies a project.
Return Values
When successful, the ftok subroutine returns a key that can be passed to the
msgget, semget, or shmget subroutine.
Error Codes
The ftok subroutine returns the value (key_t)-1 if one or more of the following
are true:
o The file named by the Path parameter does not exist.
o The file named by the Path parameter is not accessible to the process.
o The ID parameter has a value of 0.
Implementation Specifics
This subroutine is part of Base Operating System (BOS) Runtime.
Related Information
The msgget subroutine, semget subroutine, shmget subroutine.
Subroutines Overview and Understanding Memory Mapping in AIX Version 4.3 General
Programming Concepts: Writing and Debugging Programs.
-------------------------------------------------------------------------------