c - About vfork() system call? - 


#include <stdio.h> #include<unistd.h> #include<sys/types.h> #include<sys/wait.h> #include<stdio.h> #include<stdlib.h>  int main() {    pid_t child_pid = vfork();     if(child_pid < 0)    {        printf("vfork() error\n");        exit(-1);    }    if(child_pid != 0)    {        printf("hey parent %d\nmy child %d\n",getpid(),child_pid);        wait(null);    }     else    {        printf("hey child %d\nmy parent %d\n",getpid(),getppid());        execl("/bin/echo","echo","hello",null);        exit(0);    }    return 0; }

output:

 hey child 4  parent 3  hey parent 3  child 4  hello

my question : why "hello" printed after execution of parent process? have started learning vfork(). please me this?

after parent process executed, goes wait(null); blocks parent process until child process calls execl() or exit.

therefore child process when parent blocked calling execl() , hello being printed in end of output.

#include <stdio.h> #include<unistd.h> #include<sys/types.h> #include<sys/wait.h> #include<stdio.h> #include<stdlib.h>  int main() { pid_t child_pid = vfork();  if(child_pid < 0) {    printf("vfork() error\n");    exit(-1); } if(child_pid != 0) {    printf("hey parent %d\nmy child %d\n",getpid(),child_pid);    wait(null);  }   else  {    printf("hey child %d\nmy parent %d\n",getpid(),getppid());    execl("/bin/echo","echo","hello",null);    exit(0);   }  return 0;   }

if remove execl() child process go exit(0) , hello wont printed.

also, after execl() being executed creating new process code write after execl() wont executed. according man page:-

the exec() family of functions replaces current process image new process image. functions described in manual page front-ends execve(2). (see manual page execve(2) further details replacement of current process image.)


Comments

Post a Comment

Popular posts from this blog

go - serving up pdfs using golang -

Image
just wondering if guys can code. it works serving images not pdf brochure. in advance func main(){ http.handlefunc("/", func(w http.responsewriter, r *http.request){ filename := "/var/www/filedipenser/brochure.pdf" streampdfbytes, err := ioutil.readfile( filename ) if err != nil { fmt.println(err) os.exit(1) } b := bytes.newbuffer(streampdfbytes) w.header().set("content-type", "application/pdf") if _, err := b.writeto(w); err != nil { fmt.fprintf(w, "%s", err) } w.write([]byte("pdf generated")) }) err := http.listenandserve(":4111", nil) if err != nil { log.fatal("listenandserve: ", err) fmt.println(err) } } the code bit inefficient appears working. however, pdf viewers might sensitive extraneous output adding end of http response stream...
Read more

python - Best design pattern for collection of objects -

i have following architecture: +-----------------+ | collection | | | | | | | | | +-----------------+ | ^ | | create() | | | | v | getitem(b) +------------+ | | item | | | | | | +------+ | | +------------+ a class managing collection of items, creates items. , these items may need other items collection. the actual code in python, , collection passes parameter created item . see it, bad practice. improvement can see pass few functions of collection needed item , instead of whole instance. for example: class collection: getitem(self, id): ... createitem(self, id): item = item(id, self) # <-- pass self ... class item: __init__(self, id, col): ... col.getite...
Read more

how to add preprocess loader in webpack 2 -

i trying add preprocess loader in webpack 3. have installed successfully. not working here's webconfing file var debug = process.env.node_env !== "production"; var webpack = require('webpack'); var path = require('path'); module.exports = { context: path.join(__dirname, "src"), devtool: debug ? "inline-sourcemap" : null, entry: "./js/app.js", module: { loaders: [ { test: /\.jsx?$/, exclude: /(node_modules|bower_components)/, loader: 'babel-loader!preprocess-loader?+debug', // query: { // presets: ['react', 'es2015'], // plugins: ['react-html-attrs', 'transform-class-properties', 'transform-decorators-legacy'], // } }, { test: /\.css$/, loader: "style-loader!css-loader!sass-loader" } ] }, output: { path: __dirname + "/src/", f...
Read more