until you try a build you cant ascertain much of anything as far as sizeof and ranges BEWARE folks What if this
daemon("TestApp");
how many arguments does daemon take?
none.
then why are you passing one?
are you sure that you read the man page rather than just stabbing yourself in the head with a fork?
unless our man pages are different, it should take 2 arguments
okey. I want to execute TestApp as a child process which runs in background through a c program. may be i think i couldnt understand the man page says.
can you find the function prototype?
yes its asking chdir and noclose as arguments.
and what do those mean?
whats a good way to read from a socket untill a certain set of chars is found
yes. thats the problem. nochdir means it wont change the working directory..and noclose means it will direct the ouput to stderr,stdout,stdin.
so, why's that a problem?
i am still perplexed what to pass as argument
as much as possible, whenever possible.
do you want to change the working directory?
in order? finite state machine?
no. but how do daemon knows which binary to run.
problem is, i need to recv() x amount then check the buffer for that combo of chars, but if i recv() over that amount itl block forever