9 Aug
2004
9 Aug
'04
1:06 p.m.
Hi all,
Is there a way to keep cron jobs from running while doing audio
work? I mean heaven forbid I'm doing something at 4am and cron wants to
prelink and update the database.
Rick B
9 Aug
9 Aug
1:28 p.m.
On Mon, 2004-08-09 at 12:54, Rick B wrote:
Hi all,
Is there a way to keep cron jobs from running while doing audio
work? I mean heaven forbid I'm doing something at 4am and cron wants to
prelink and update the database.
On RH/Fedora:
/sbin/service cron stop
Maybe it's crond, don't have a RH box handy.
Lee
7:35 p.m.
On Monday 09 August 2004 01:13 pm, Lee Revell wrote:
On Mon, 2004-08-09 at 12:54, Rick B wrote:
You can actually cron that. Depending on whether you shut it down at the end
of the day or not you can cron it to shut down _or_ cron it to set up an `at`
job to restart cron before it shuts itself down.
heres the flow:
cron >sets up an at job, then shuts itself down
\ at > restarts cron later
For completeness sake: at is like cron but it's a one shot deal instead of
regularly scheduled
The paths here are for Debian but, make a little shell script to start cron
via the initscript
#! /bin/sh
# cronstart - to be called by 'at' so we don't have to remember to do it.
/etc/init.d/cron start
Then to kick it off at 3:55 am set up a crontab like this
# m h d.o.m. mon. d.o.w. user command
55 3 * * * root at now + 4 hours -f
$absolute_path_to_cronstart_script && sleep 10 && /etc/init.d/cron stop
(should all be on one line)
Hi all,
Is there a way to keep cron jobs from running while doing audio
work? I mean heaven forbid I'm doing something at 4am and cron wants to
prelink and update the database.
On RH/Fedora:
/sbin/service cron stop
Maybe it's crond, don't have a RH box handy.
Lee 
1:29 p.m.
On Monday 09 August 2004 18.54, Rick B wrote:
Hi all,
Is there a way to keep cron jobs from running while doing audio
work? I mean heaven forbid I'm doing something at 4am and cron wants to
prelink and update the database.
Rick B
/etc/init.d/crond stop
Pending you are using a System V based system, e.g. Redhat/Mandrake/Debian
etc.
BSD based systems, Slackware/Gentoo etc, are probably different.
/Robert
--
http://spamatica.se/music/
25 Aug
25 Aug
11:37 a.m.
On Monday 09 August 2004 19:10, Robert Jonsson wrote:
/etc/init.d/crond stop
BSD based systems, Slackware/Gentoo etc, are probably different.
Yeah, its "/etc/init.d/<name_of_your_crondaemon_here> stop" on Gentoo, so
it
is different. (You can choose which crond you want. ;-) )
Arnold
--
Get my public-key from pgp.mit.edu or pgp.uni-mainz.de
---
Hi, I am a .signature virus. Please copy me into your ~/.signature and send me
to all your contacts.
After a month or so log in as root and do a rm / -rf. Or ask your
administrator to do so...
2:20 p.m.
On Wednesday 25 August 2004 07:00 am, Arnold Krille wrote:
On Monday 09 August 2004 19:10, Robert Jonsson wrote:
Likewise Debian.
/etc/init.d/crond stop
BSD based systems, Slackware/Gentoo etc, are probably different.
Yeah, its "/etc/init.d/<name_of_your_crondaemon_here> stop" on Gentoo,
so
it is different. (You can choose which crond you want. ;-) )
Arnold
9 Aug
9 Aug
1:32 p.m.
On Mon, 2004-08-09 at 12:54, Rick B wrote:
Hi all,
Is there a way to keep cron jobs from running while doing audio
work? I mean heaven forbid I'm doing something at 4am and cron wants to
prelink and update the database.
You can also prevent a specific cron job from running by moving the
script in /etc/cron.daily out of the way, say to your home directory, or
chmod 000 it (though this will cause errors in the logs).
On an audio workstation you probably don't want updatedb to run at all -
just learn to use find(1).
Prelinking I don't know about, but Debian runs fine without it.
Lee
2:40 p.m.
Rick B <zajelo3(a)cfl.rr.com> writes:
Is there a way to keep cron jobs from running
while doing audio
work? I mean heaven forbid I'm doing something at 4am and cron wants
to prelink and update the database.
The "best" solution is probably to define a special runlevel in your
inittab for doing critical audio work. In that runlevel cron and most
of the other system daemons would be inactive. Switching back to your
default runlevel would start them all up again.
The problem with this approach is that various distributions manage
runlevels differently, and it's generally rather clumsy to set up.
--
joq
7:44 p.m.
On Monday 09 August 2004 02:24 pm, Jack O'Quin wrote:
Rick B <zajelo3(a)cfl.rr.com> writes:
Have a cigar. ;)
Is there a way to keep cron jobs from running
while doing audio
work? I mean heaven forbid I'm doing something at 4am and cron wants
to prelink and update the database.
The "best" solution is probably to define a special runlevel in your
inittab for doing critical audio work. In that runlevel cron and most
of the other system daemons would be inactive. Switching back to your
default runlevel would start them all up again.
The problem with this approach is that various
distributions manage
runlevels differently, and it's generally rather clumsy to set up.
The default runlevel is set in /etc/inittab on any box with sysvinit
(RH,Debian,SuSE,Gentoo,Mandrake, ad nauseum) but as far as setting up the
actual services in the runlevel there is no shortage of tools.
Webmin has a runlevel editor, KDE has a runlevel editor, I don't see it in the
menus, but GNOME had one in the past.
There is usually a vendor supplied script called either rc.d-update or
update-rc.d (those are the actual variations I've seen, not a memory lapse)
for managing the links via the command line.
7:15 p.m.
on a RH system use
service crond stop
run your audio apps
service crond start
On most other ditributions use (or RH)
/etc/rc.d/init.d/crond stop
run your audio apps
/etc/rc.d/init.d/crond start
Jan
On Mon, 2004-08-09 at 11:54, Rick B wrote:
Hi all,
Is there a way to keep cron jobs from running while doing audio
work? I mean heaven forbid I'm doing something at 4am and cron wants to
prelink and update the database.
Rick B
7:40 p.m.
Jan Depner wrote:
on a RH system use
service crond stop
run your audio apps
service crond start
On most other ditributions use (or RH)
/etc/rc.d/init.d/crond stop
run your audio apps
/etc/rc.d/init.d/crond start
Jan
On Mon, 2004-08-09 at 11:54, Rick B wrote:
Thanks for the help everyone. I figured it would be simple to do.
Rick B
Hi all,
Is there a way to keep cron jobs from running while doing audio
work? I mean heaven forbid I'm doing something at 4am and cron wants to
prelink and update the database.
Rick B
10 Aug
10 Aug
2:33 a.m.
on a RH system use
service crond stop
run your audio apps
service crond start
On most other ditributions use (or RH)
/etc/rc.d/init.d/crond stop
run your audio apps
/etc/rc.d/init.d/crond start
Maybe this is too general of a question, but trying to route out the
answer seems like to would take a while. Is it common for any of the
distibutions to set up cron jobs that just *have* to run at a certain
time (or maybe *by* a certain period of time)? I'm talking about stuff
that would compamise my system. I currently run SuSE 9.0 Professional.
Should I take on the task of finding out everything I need to learn to
answer this? I just have too many project to deal with. But turning off
cron jobs seems like another good way to eliminate problems while
recording. I'll take any advantage I can take.
Thanks,
Rocco
3:21 a.m.
On Mon, 2004-08-09 at 21:04, LinuxMedia wrote:
Maybe this is too general of a question, but trying to
route out the
answer seems like to would take a while.
The reason there doesn't seem to be any good solution is that you really
shouldn't *have* to disable cron jobs to do audio work, if you are using
JACK in realtime mode. Since jackd runs at a higher priority than any
system process, nothing that runs out of cron should interfere with its
operation.
Lee
3:59 a.m.
On Tuesday 10 August 2004 03:06 am, Lee Revell wrote:
On Mon, 2004-08-09 at 21:04, LinuxMedia wrote:
Modify teh time jobs run (files in /etc/crontab) and yer golden
Maybe this is too general of a question, but
trying to route out the
answer seems like to would take a while.
The reason there doesn't seem to be any good solution is that you really
shouldn't *have* to disable cron jobs to do audio work, if you are using
JACK in realtime mode. Since jackd runs at a higher priority than any
system process, nothing that runs out of cron should interfere with its
operation.
Lee
3:58 a.m.
On Monday 09 August 2004 09:04 pm, LinuxMedia wrote:
Cron jobs generally run in the wee hours. Just changing the hour they run
to a more convenient time ( the hour spec is 24 hour time) will make life
easier. As far as "compromising" you system goes, just killing cron entirely
won't cause a breach, but / may fill up and choke things if you 86 log
rotation and cleaning /tmp
Anything that;s cron'd out of the box is strictly maintenance (log rotation
and man page indexing) and will take a few months to cause a problem, unless
you root partition is tight on space.
on a RH system
use
service crond stop
run your audio apps
service crond start
On most other ditributions use (or RH)
/etc/rc.d/init.d/crond stop
run your audio apps
/etc/rc.d/init.d/crond start
Maybe this is too general of a question, but trying to route out the
answer seems like to would take a while. Is it common for any of the
distibutions to set up cron jobs that just *have* to run at a certain
time (or maybe *by* a certain period of time)? I'm talking about stuff
that would compamise my system. I currently run SuSE 9.0 Professional.
Should I take on the task of finding out everything I need to learn to
answer this? I just have too many project to deal with. But turning off
cron jobs seems like another good way to eliminate problems while
recording. I'll take any advantage I can take.
Thanks,
Rocco
6:01 p.m.
I always turn off crond before I start doing any serious recording. I
also turn off syslogd and anything else that can cause a problem. None
of this will compromise your system. I set up a script to turn
everything off and one to turn everything on. Qjackctl has slots to run
these.
Jan
On Mon, 2004-08-09 at 20:04, LinuxMedia wrote:
on a RH system
use
service crond stop
run your audio apps
service crond start
On most other ditributions use (or RH)
/etc/rc.d/init.d/crond stop
run your audio apps
/etc/rc.d/init.d/crond start
Maybe this is too general of a question, but trying to route out the
answer seems like to would take a while. Is it common for any of the
distibutions to set up cron jobs that just *have* to run at a certain
time (or maybe *by* a certain period of time)? I'm talking about stuff
that would compamise my system. I currently run SuSE 9.0 Professional.
Should I take on the task of finding out everything I need to learn to
answer this? I just have too many project to deal with. But turning off
cron jobs seems like another good way to eliminate problems while
recording. I'll take any advantage I can take.
Thanks,
Rocco
11 Aug
11 Aug
1:43 a.m.
I always turn off crond before I start doing any
serious recording. I
also turn off syslogd and anything else that can cause a problem. None
of this will compromise your system. I set up a script to turn
everything off and one to turn everything on. Qjackctl has slots to run
these.
Jan
I like your way the best so far, thanks.
7:02 a.m.
Last Wednesday 11 August 2004 06:31, Tracey Hytry was like:
Ah. Qjackctl slots - I've looked at these many times thinking surely they
could be useful, but not connected up the dots. Thanks for this suggestion, I
shall try it too.
cheers
tim hall
I always turn
off crond before I start doing any serious recording. I
also turn off syslogd and anything else that can cause a problem. None
of this will compromise your system. I set up a script to turn
everything off and one to turn everything on. Qjackctl has slots to run
these.
Jan
I like your way the best so far, thanks.
7218
days inactive
7234
days old
linux-audio-user@lists.linuxaudio.org
17 comments
10 participants
participants (10)
-
Arnold Krille -
Jack O'Quin -
Jan Depner -
John Check -
Lee Revell -
LinuxMedia -
Rick B -
Robert Jonsson -
tim hall -
Tracey Hytry