Why should I create a daemon instead of a command line tool?

Question

I'm aware this can appear to be a very silly question for most of the IT crowd, but I'm new at designing this kind of architecture (only developed in PHP before).

I'm building an application that makes use of a specific OS function. The end user is going to call a PHP script that in turn needs to call a C program. The latter will call OS API and return the results in the form of strings and a file pointer to the PHP script.

Now, I know I have the option to deploy this C program either as a command line tool or a daemon. Why should I choose one instead of the other?

Just to confirm, did you mean returning a file pointer from `C` to `PHP` ? — VoidPointer, Jul 05 '13 at 14:27
Yes, the c program is going to create a file and pass it's path to the PHP script. Using the word pointer could have actually been inappropriate. — Anton Maria Prati, Jul 05 '13 at 16:03

score 2 · Answer 1 · answered Jul 05 '13 at 14:32

2

A daemon is typically a background process, so if you want your program to sit in the background and monitor something (e.g. report log file size increase every 5 minutes the last hour) and then report the results when someone watches a web page, a deamon is the correct choice.

If you instead want to do something that can be done immediately (e.g. report current log file size), a command line tool is easier to create and maintain.

answered Jul 05 '13 at 14:32

Ztranger

362
1
6

Thanks, that's exactly in the scope of my project. – Anton Maria Prati Jul 05 '13 at 16:12

score 1 · Answer 2 · answered Jul 05 '13 at 14:28

1

A daemon is a program that starts when the computer starts, and keeps running until the computer shuts down. Server programs like the Apache web server is a daemon, for example.

If you just want a program that does a quick system call and returns the result, there is really no reason to have it as a daemon, unless it's supposed to be used as a server program where multiple "clients" can connect and request this system call.

answered Jul 05 '13 at 14:28

Some programmer dude

400,186
35
402
621

Being a website, there will be multiple clients requests but limited, as the target userbase is rather narrow. The chance of concurrency issues is virtually none. – Anton Maria Prati Jul 05 '13 at 16:16

score 1 · Answer 3 · answered Jul 05 '13 at 14:33

1

As a side note: You may also write a php C++ extension to call OS specific functions.

A tool does action X. (E.g. convert a file), if it's quick and fast there should be no need to write a daemon. Daemons often come into play when you need synchronous writing/reading, or queueing.

An easy and popular way to write daemons nowadays to wrap command line commands is nodejs, see for example here: http://blog.nodejitsu.com/keep-a-nodejs-server-up-with-forever

answered Jul 05 '13 at 14:33

Arend

3,741
2
27
37

I'd like to maintain the architecture as modular as possible. The first implementation is within PHP, but we might want to call the program with other frameworks in the future. Thanks for suggestion though! – Anton Maria Prati Jul 05 '13 at 16:12

score 1 · Accepted Answer · edited Jul 05 '13 at 14:56

1

Deamon is a process that always run in background in memory. Deamons are used for
recurrent task execution like monitoring processes or data changes or etc. And command line-tool is a program that could be executed only when you needed. So my solution would be to use cmd tool because:

Deamon always run in memory
If the deamon crashes who will be responsible for restarting it?
You have to implement simultaneous request control

So my opinioin is cmd tool. But if you want some kind of deamon behave there is other option. If you need to run php script or cmd tool repetitively use cron under linux or scheduler under windows

edited Jul 05 '13 at 14:56

Adriano Repetti

65,416
20
137
208

answered Jul 05 '13 at 14:33

freeland

171
3
18

My concerns about a daemon implementation are precisely about memory and resources consumption. As far as I know, a command line tool should simply free any resource as it ends execution, right? The site is going to be accessed by a limited number of people, so there shouldn't be simultaneous access issues. – Anton Maria Prati Jul 05 '13 at 16:09
Yes cmd tool after execution should free memory – freeland Jul 06 '13 at 12:41

Why should I create a daemon instead of a command line tool?

4 Answers4