GETOPT(3PVM)
π GETOPT(3PVM) β the pvm_getopt manual, but make it make sense π
okay so this is the PVM Version 3.4 page for pvm_getopt, aka the little function that just... tells you stuff. It reads the current value of a libpvm option and hands it back to you. No drama, no side quests. Bestie behavior fr fr. π«Ά
β¨ NAME β¨
pvm_getopt β returns the value of libpvm options. That's it. That's the whole job. π
πΈ SYNOPSIS πΈ
C:
int val = pvm_getopt( int what )
Fortran:
call pvmfgetopt( what, val )
π PARAMETERS π
whatβ an integer that says which option you wanna peek at. It's giving "pick a card". Here's the whole menu, lowkey iconic:PvmRoute1β message routing policyPvmDebugMask2β libpvm debug maskPvmAutoErr3β auto error reportingPvmOutputTid4β stdout destination for childrenPvmOutputCode5β output message tag for childrenPvmTraceTid6β trace data destination for childrenPvmTraceCode7β trace message tag for childrenPvmTraceBuffer8β trace buffer size for childrenPvmTraceOptions9β trace collection options for childrenPvmFragSize10β message fragment sizePvmResvTids11β allow messages to reserved tags and TIDsPvmSelfOutputTid12β stdout destinationPvmSelfOutputCode13β output message tagPvmSelfTraceTid14β trace data destinationPvmSelfTraceCode15β trace message tagPvmSelfTraceBuffer16β trace buffer sizePvmSelfTraceOptions17β trace collection optionsPvmShowTids18βpvm_catchoutprints task ids with outputPvmPollType19β message wait policy (shared memory)PvmPollTime20β message spinwait durationPvmOutputContext21β output message context for childrenPvmTraceContext22β trace message context for childrenPvmSelfOutputContext23β output message contextPvmSelfTraceContext24β trace message contextPvmNoReset25β do not kill task on reset
valβ the integer that comes back holding the value of the option. It's the reply text. π
π DESCRIPTION π
pvm_getopt returns the value of the specified option in PVM. Like, you ask, it answers. Simple situationship.
If you wanna know what all these options and values actually mean, go read pvm_setopt β that's the one that explains the lore. This one is just the reader. π
heads up bestie β if an error happens, the PVM error code gets returned in place of the option value. So like... the thing you got back might not be your option at all. Check yourself before you wreck yourself. π
β EXAMPLES β
C:
val = pvm_getopt( PvmFragSize );
Fortran:
CALL PVMFGETOPT( PVMAUTOERR, VAL )
π ERRORS π
This error condition can be returned:
PvmBadParamβ you gave it an invalid value. Not everywhatis a validwhat, bestie. π
π SEE ALSO π
pvm_setopt(3PVM)β the sister function. The one that writes. Go read her. π¦
and that's the whole page, no notes. This was PVM Version 3.4's GETOPT(3PVM), dated 4 April, 1994 β so like, vintage vintage. Old enough to be your mom's favorite manpage. πβ¨ Slay, stay safe, and always check your return value. Periodt. ππ«Ά
π¦ where this page comes from
- debian bookworm: pvm-dev 3.4.6-5
- ubuntu jammy: pvm-dev 3.4.6-3.2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms