I have created a simple download schedular with source-code give below :

---------------------record_strokes.sh-------------------

touch /home/student/packs/lynx/logfile

lynx -cmd_log /home/student/packs/lynx/logfile

---------------------play_strokes.sh---------------------
lynx -cmd_script='/home/admin/packs/lynx/logfile' www.google.com


--------------------download_links.sh---------------------
wget http://iso.linuxquestions.org/downlo...i386-disc1.iso

wget http://iso.linuxquestions.org/downlo...i386-disc2.iso

wget http://iso.linuxquestions.org/downlo...i386-disc3.iso




--------------------halt.sh---------------------
halt


--------------------main.c---------------------

#include<stdio.h>
//#include<sys/ipc.h>
//#include<sys/shm.h>
//#include<sys/types.h>
//#include<sys/sem.h>
#include<pthread.h>

void download(void)
{
system("sh download_links.sh");
}
main()
{
pthread_t id1,id2;
system("sh record_strokes.sh");
system("sh play_strokes.sh");
pthread_create(&id1,NULL,download,NULL); // Error in 3rd para.
pthread_create(&id2,NULL,download,NULL); // Error in 3rd para.
pthread_exit(NULL);
system("sh halt.sh");
return 0;
}


So, this is a simple download scheduler program code. Which creates multiple threads of the downloading process - wget (i could also have used 'curl' instead 'wget').Can you debug this code?
Can anyone guide me please?

From `man pthread_create`:

Thus, your "download" function should have the following signature:

P.S.: You created 4 identical threads and still failed to post in the correct sub-forum. Good job.

Reporting and closing duplicates---keep this one

And moving to Programming

@ broken :

Doing so gives an error :


main.c:8: error: parameter name omitted

Try reading a good book on C programming before attempting to program in C.

just : void *download() solved the issue !!

Have you ever tried to compile with '-Wall -Wextra' ?

what is this? I don't about such a word at all ?

See below:
http://gcc.gnu.org/onlinedocs/gcc/Wa...arning-Options

Just an fyi, the following is considered bad form:
as compared with:

It is left as an exercise for the reader to understand why explicit paths are better than searching the user path when executing code "under-the-hood".