Skip to main content
Unix & Linux

Return to Question

added 231 characters in body
Source Link
Qiulang 邱朗
Qiulang 邱朗
  • 261
  • 5
  • 11

Some program has --daemonize option to run itself in background, e.g. php-fpm. I was wondering is there any difference between using --daemonize or just use the old & way to run the process in background?

I would assume there is otherwise why bother to provide --daemonize, why not just run it with &

But I can't find information about that. For example I test php-fpm --daemonize vs php-fpm & and do some limited test. I don't see the difference.

------ update ------

I hit this problem again when trying Dockerfile CMD shell vs exec form.

So maybe it is worth to add a SO discussion here https://stackoverflow.com/questions/42805750/dockerfile-cmd-shell-versus-exec-form

Some program has --daemonize option to run itself in background, e.g. php-fpm. I was wondering is there any difference between using --daemonize or just use the old & way to run the process in background?

I would assume there is otherwise why bother to provide --daemonize, why not just run it with &

But I can't find information about that. For example I test php-fpm --daemonize vs php-fpm & and do some limited test. I don't see the difference.

Some program has --daemonize option to run itself in background, e.g. php-fpm. I was wondering is there any difference between using --daemonize or just use the old & way to run the process in background?

I would assume there is otherwise why bother to provide --daemonize, why not just run it with &

But I can't find information about that. For example I test php-fpm --daemonize vs php-fpm & and do some limited test. I don't see the difference.

------ update ------

I hit this problem again when trying Dockerfile CMD shell vs exec form.

So maybe it is worth to add a SO discussion here https://stackoverflow.com/questions/42805750/dockerfile-cmd-shell-versus-exec-form

added 4 characters in body
Source Link
Qiulang 邱朗
Qiulang 邱朗
  • 261
  • 5
  • 11

Some program has --daemonize option to run itself in background, e.g. php-fpm. I was wondering is there any difference between using --daemonize or just use the old & way to run the process in background?

I would assume there is otherwise why bother to provide --daemonize, justwhy not just run it with &

But I can't find information about that. For example I test php-fpm --daemonize vs php-fpm & and do some limited test. I don't see the difference.

Some program has --daemonize option to run itself in background, e.g. php-fpm. I was wondering is there any difference between using --daemonize or just use the old & way to run the process in background?

I would assume there is otherwise why bother to provide --daemonize, just not run it with &

But I can't find information about that. For example I test php-fpm --daemonize vs php-fpm & and do some limited test. I don't see the difference.

Some program has --daemonize option to run itself in background, e.g. php-fpm. I was wondering is there any difference between using --daemonize or just use the old & way to run the process in background?

I would assume there is otherwise why bother to provide --daemonize, why not just run it with &

But I can't find information about that. For example I test php-fpm --daemonize vs php-fpm & and do some limited test. I don't see the difference.

Source Link
Qiulang 邱朗
Qiulang 邱朗
  • 261
  • 5
  • 11

Is there any difference to run a process in the background with an & vs when it has --daemonize option?

Some program has --daemonize option to run itself in background, e.g. php-fpm. I was wondering is there any difference between using --daemonize or just use the old & way to run the process in background?

I would assume there is otherwise why bother to provide --daemonize, just not run it with &

But I can't find information about that. For example I test php-fpm --daemonize vs php-fpm & and do some limited test. I don't see the difference.