-
Senior Member
registered user
Anybody knows how to deamonize a shell script ?
sh scriptname.sh
=> bu how to deamonize this ?
-
Senior Member
registered user
Re: Anybody knows how to deamonize a shell script ?
--What do you mean by "daemonize"? Daemons stay running in the background looking for connections or facilitating I/O.
--If you just want it to run every time at boot, you can create a link to the script in the /etc/rc5.d directory.
This thread ( http://www.knoppix.net/forum/viewtopic.php?t=3138 ) may be of use.

Originally Posted by
ktheking
sh scriptname.sh
=> bu how to deamonize this ?
-
Senior Member
registered user
I'd like to run a script that continiously is running ,even after quiting a knoppix session.
It's a script that contains timed actions ,mainly used for the same purpose as 'Scheduled tasks' inside windoze .
By the way isn't there something like that for KDE ?
-
Senior Member
registered user
--You should probably investigate ' man cron '... 

Originally Posted by
ktheking
I'd like to run a script that continiously is running ,even after quiting a knoppix session.
It's a script that contains timed actions ,mainly used for the same purpose as 'Scheduled tasks' inside windoze .
By the way isn't there something like that for KDE ?
-
Senior Member
registered user
This sounds exactly what I need..
Thanks a lot man .... (just gotta do my homework and learn to use it
)
man cron :
Using cron to run programs on a schedule
cron is a Linux system process that will execute a program at a preset time. To use cron you must prepare a text file that describes the program that you want executed and the times that cron should execute them. Then you use the crontab program to load the text file that describes the cron jobs into cron.
Here is the format of a cron job file:
[min] [hour] [day of month] [month] [day of week] [program to be run]
where each field is defined as [min] Minutes that program should be executed on. 0-59. Do not set as * or the program will be run once a minute.
[hour] Hour that program should be executed on. 0-23. * for every hour.
[day of month] Day of the month that process should be executed on. 1-31. * for every day.
[month] Month that program whould be executed on. 1-12 * for every month.
[day of week] Day of the week. 0-6 where Sunday = 0, Monday = 1, ...., Saturday = 6. * for every day of the week.
[program] Program to be executed. Include full path information.
Here are some examples:
0,15,30,45 * * * * /usr/bin/foo
Will run /usr/bin/foo every 15 minutes on every hour, day-of-month, month, and day-of-week. In other words, it will run every 15 minutes for as long as the machine it running.
10 3 * * * /usr/bin/foo
Will run /usr/bin/foo at 3:10am on every day.
10 * 1 * * /usr/bin/foo
Will run /usr/bin/foo at 12:10am on the first day of the month.
10 * * 1 * /usr/bin/foo
Will run /usr/bin/foo at 12:10am on the first month of the year.
10 14 * * 1 /usr/bin/foo
Will run /usr/bin/foo at 2:10pm on every Monday.
There are more options for these. See man man crontab -S 5.
You must use crontab to load cron jobs into cron. First create a text file that uses the above rule to describe the cron job that you want to load into cron. But before you load it, type crontab -l to list any jobs that are currently loaded in crontab.
If none are listed, then it is safe to load your job. Example. If you wanted to run /usr/local/bin/foo once a day at 3:10am, then create a text file
10 3 * * * /usr/bin/foo
Save it as foo.cron. Then type crontab foo.cron. Check to see if it was loaded by typing crontab -l. It should display something like this:
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (ipwatch.cron installed on Thu Nov 18 11:48:02 1999)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
10 3 * * * /usr/bin/foo
If you want to edit the cron job, then edit foo.cron and then remove the existing cron job (crontab -r) and load it again (crontab foo.cron). You can have multiple jobs. Just put each different one on a seperate line in foo.cron.
contab jobs will run under the user that was in effect when you loaded the job in crontab.
See man cron, man crontab and man crontab -S 5 for more information.
Similar Threads
-
By splittik in forum General Support
Replies: 1
Last Post: 03-22-2005, 07:38 AM
-
By niXnoob in forum General Support
Replies: 3
Last Post: 10-06-2004, 04:56 AM
-
By garyng in forum General Support
Replies: 3
Last Post: 06-05-2004, 03:51 AM
-
By sorel in forum General Support
Replies: 1
Last Post: 04-20-2004, 08:39 PM
-
By xeon44145 in forum General Support
Replies: 0
Last Post: 02-12-2004, 03:04 PM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules

AMD Ryzen 5 5500 Processor ( read Description)
$59.00

Intel Core i7-4770 3.40GHz Quad Core SR149 LGA 1150 CPU Processor tested
$35.00

INTEL CORE I9-10940X X-SERIES PROCESSOR | 3.30GHZ | SRGSH
$179.99

Intel Core i5-13500 2.5GHz/4.8GHz Boost 14-Core SRMBM LGA1700 Desktop Processor
$165.00

Intel Core i7-9700 Octa-Core 3 GHz Desktop Processor LGA 1151
$79.99

Intel Core i7-3770K 3.5 GHz Processor
$39.00

Intel Core i5-12500T SRL5W 2GHz 18MB 6 Core Socket LGA1700 Desktop CPU Processor
$114.99

Intel i7-8700 Coffee Lake 3.2GHz 6-Core Max Turbo 4.6GHz Processor
$67.99

Lenovo ThinkCentre M920s SFF Barebones PC Motherboard PSU DVD No CPU RAM SSD
$27.99

PS5 Over Heating Problem Solver 1.5 Grams Liquid metal thermal paste CPU, GPU
$15.99