I know that in a DOS/Windows application, you can issue system commands from code using lines like:
system(\"pause\");
or
s
I think what you are looking for are fork and exec.
system
is a bad idea for several reasons:
&
, it ends up being a grandchild process and gets orphaned and taken in by the init
process (pid 1), and you have no way of checking its status after that.For the first and final issues, popen
is one solution, but it doesn't address the other issues. You should really use fork
and exec
(or posix_spawn
) yourself for running any external command/program.
Not surprisingly, the command is still
system("whatever");
and the header is still stdlib.h
. That header file's name means "standard library", which means it's on every standard platform that supports C.
And yes, calling system()
is often a bad idea. There are usually more programmatic ways of doing things.
If you want to see how lsmod
works, you can always look-up its source code and see what the major system calls are that it makes. Then use those calls yourself.
A quick Google search turns up this link, which indicates that lsmod
is reading the contents of /proc/modules
.
Well, lsmod does it by parsing the /proc/modules
file. That would be my preferred method.