cimmof(1)
β¨ NAME β¨
cimmof β compile MOF files into the CIM Repository. it's a section 1 manual page, and yes bestie, you're gonna wanna read the whole thing π
π¦ SYNOPSIS π¦
cimmof --version
cimmof [ -w ] [ -E ] [ -uc ] [ -aE | -aV | -aEV ] [ -I path ]
[ -n namespace ] [ --namespace namespace ] [ --xml ]
[ --trace ] [ mof_file ... ]
π« Remarks π«
okay so real talk before you go wild:
- only a superuser, or a user with write access to the default-or-specified namespace, can run
cimmofto compile MOFs into the CIM Repository. so like, permissions check first, queen π - superclasses must be compiled before subclasses. if you don't, the compile literally just fails. no cap. π
- it is strongly recommended that your MOF files include all the necessary subclasses, so they can compile properly even if certain classes are not in the CIM Repository. future-proofing, we love to see it π«Ά
π DESCRIPTION π
cimmof is the command line interface to the Managed Object Format (MOF) Compiler. the MOF Compiler is a utility that compiles MOF files (using the MOF format defined by the DMTF CIM Specification) into CIM classes and instances that get stored in the CIM Repository. iconic behavior, honestly β¨
you can run cimmof to compile MOF files at any time after installation. and if you don't specify an input file? stdin is used as the input. it's giving flexible π
the MOF Compiler requires that the input MOF files be in the current directory, or that you give a fully qualified path. and to simplify specifying a bunch of MOF files on the cimmof command line, the MOF Compiler lets you compile from files containing a list of MOF files using the include pragma (shown below):
#pragma include ("application.mof")
#pragma include ("server.mof")
MOF files using the include pragma must live in the current directory, or in a directory specified by the -I command line option. π
the -n option can be used to specify a R namespace in which the CIM classes and instances will be compiled. if this option is not specified, the default R namespace is root/cimv2 (with the exception of provider registration schemas).
for provider registration schemas: if the -n option is not specified, the default R namespace is root/PG_InterOp. if the -n option is specified, the R namespace you give must be root/PG_InterOp β otherwise, the error message The requested operation is not supported. gets returned. π and for provider MOFs, the R namespace you specify must match one of the namespaces specified in the PG_ProviderCapabilities class schema definition.
π₯ Options π₯
the cimmof command recognizes the following options:
-aEβ Allow Experimental Schema changes.-aEVβ Allow both Experimental and Version Schema changes.-aVβ Allow both Major and Down Revision Schema changes.-Eβ Syntax check only.-h,--helpβ Display command usage information.-I pathβ Specify the path to included MOF files. this path may be relative or absolute.
if the input MOF file has include pragmas and the included files do not reside in the current directory, the directive must be used to specify a path to them on the cimmof command line.
-nβ Override the default CIM Repository namespace. the namespace specified must be a valid CIM namespace name. for the definition of a valid CIM namespace name, refer to the Administrator's Guide. for provider registration schemas, the namespace specified must beroot/PG_InterOp.--namespaceβ Override the default CIM Repository namespace. the namespace specified must be a valid CIM namespace name. for the definition of a valid CIM namespace name, refer to the Administrator's Guide. for provider registration schemas, the namespace specified must beroot/PG_InterOp.--traceβ Trace to file (default to stdout).-ucβ Allow update of an existing class definition.--versionβ Display CIM Server version.-wβ Suppress warning messages.
when compiling the MOF files, if there are CIM elements (such as classes, instances, properties, or methods) defined in the MOF files which already exist in the CIM Repository, the cimmof command returns warning messages. the -w option can be used to suppress these warning messages. π€«
--xmlβ Output XML only, to stdout. Do not update repository.
π EXIT STATUS π
the cimmof command returns one of the following values:
0β Successful completion1β Error
when an error occurs, an error message is written to stderr and an error value of 1 is returned. bestie, watch that exit code, it's literally telling you everything π«Ά
π USAGE NOTES π
the cimmof command requires that the CIM Server is running. and if an operation requires more than two minutes to be processed, the cimmof command prints a timeout message and returns an error value. so like, don't just sit there staring at it π
πΈ DIAGNOSTICS πΈ
Error trying to create Repository in path localhost:5988: Cannot connect
to: localhost:5988 Failed to set DefaultNamespacePath.
the CIM Server is not running. Start the CIM Server with the command and re-run cimmof.
if the MOF Compiler detects an error in the MOF file while parsing the file, a parsing error is returned with the line number of the MOF file containing the error. so helpful of it, honestly β
Operation cannot be carried out since the specified superclass does not
exist.
the MOF Compiler compiled a MOF file with superclasses that were not in the CIM Repository.
for a list of possible error messages that may be returned, refer to the Chapter on WBEM messages in the Administrator's Guide. π
β EXAMPLES β
compile a MOF file into the default namespace in the CIM Repository β just issue the cimmof command with no options:
cimmof processInfo.mof
compile the MOF files into the "root/application" namespace:
cimmof -nroot/application test1.mof test2.mof
compile the MOF file defined in the directory ./MOF with the name CIMSchema25.mof, and containing include pragmas for other MOF files also in the ./MOF directory:
cimmof -w -I./MOF MOF/CIMSchema25.mof
display Usage Info for the cimmof command:
cimmof -h
π§ SEE ALSO π§
cimserver(1).
and that's the whole cimmof(1) manual page, bestie β go compile something iconic πβ¨ slay, periodt ππ¦
π¦ where this page comes from
- centos-stream 10: tog-pegasus 2:2.14.1-79.el10 Β· MIT
- centos-stream 9: tog-pegasus 2:2.14.1-68.el9 Β· MIT
- fedora 43: tog-pegasus 2:2.14.1-86.fc43 Β· MIT
- fedora 44: tog-pegasus 2:2.14.1-89.fc44 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms