7 Sep
2004
7 Sep
'04
12:04 p.m.
Greetings:
I've tacked on a copy of top's report for a plain-vanilla Planet CCRMA
RH 9. I'm going to be advising a client regarding what services he
can/should disable for best-case recording (with a nearly identical
system), so I thought I'd use my own system for the primary tests. I'd
like to know which of the services and jobs listed by top can be safely
disabled during the use of a setup consisting of Jack, Rosegarden, and
Hydrogen, all in the latest & greatest versions from Planet C. Any and
all suggestions will be cosmically appreciated.
Btw, at the time of the screen capture I was running Jack (qjackctl),
Mozilla, XMMS, and FileRunner, a Tk-based file manager (which is why you
see a wish instance in the top report). This report was generated for my
desktop machine.
Best regards,
dp
61 processes: 58 sleeping, 2 running, 1 zombie, 0 stopped
CPU states: 4.7% user 2.1% system 0.0% nice 0.0% iowait 93.0% idle
Mem: 515140k av, 504176k used, 10964k free, 0k shrd, 138276k
buff
260004k active, 200752k inactive
Swap: 1044216k av, 4292k used, 1039924k free 115320k
cached
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND
1972 dlphilp 18 0 47172 44M 21984 S 2.9 8.9 8:17 0
mozilla-bin
13422 root 16 0 1104 1104 868 R 0.9 0.2 0:00 0 top
1483 root 13 0 101M 37M 3932 R 0.7 7.4 4:52 0 X
1953 dlphilp 12 0 28712 28M 2668 S 0.7 5.5 2:10 0 jackd
1952 dlphilp 12 0 26828 26M 16376 S 0.5 5.2 0:49 0 qjackctl
1961 dlphilp 12 0 40292 39M 14276 S 0.3 7.8 2:14 0 xmms
1489 dlphilp 12 0 7988 7988 2060 S 0.1 1.5 0:00 0 xterm
1 root 12 0 476 476 428 S 0.0 0.0 0:04 0 init
2 root 12 0 0 0 0 SW 0.0 0.0 0:00 0 keventd
3 root 12 0 0 0 0 SW 0.0 0.0 0:00 0 kapmd
4 root 19 19 0 0 0 SWN 0.0 0.0 0:00 0
ksoftirqd_CPU0
5 root 12 0 0 0 0 SW 0.0 0.0 0:02 0 kswapd
6 root 12 0 0 0 0 SW 0.0 0.0 0:00 0 bdflush
7 root 12 0 0 0 0 SW 0.0 0.0 0:00 0 kupdated
8 root 4 -20 0 0 0 SW< 0.0 0.0 0:00 0
mdrecoveryd
12 root 12 0 0 0 0 SW 0.0 0.0 0:00 0 kjournald
653 root 12 0 0 0 0 SW 0.0 0.0 0:00 0 kjournald
1093 root 12 0 556 556 476 S 0.0 0.1 0:00 0 syslogd
1097 root 12 0 432 428 380 S 0.0 0.0 0:00 0 klogd
1115 rpc 12 0 544 544 476 S 0.0 0.1 0:00 0 portmap
1134 rpcuser 12 0 700 700 624 S 0.0 0.1 0:00 0 rpc.statd
1201 root 12 0 488 484 440 S 0.0 0.0 0:00 0 apmd
1238 root 12 0 1228 1148 996 S 0.0 0.2 0:00 0 sshd
1252 root 12 0 884 852 740 S 0.0 0.1 0:00 0 xinetd
1261 root 12 0 452 448 404 S 0.0 0.0 0:00 0 gpm
1305 root 12 0 576 576 516 S 0.0 0.1 0:00 0 crond
1316 root 12 0 3124 3096 1360 S 0.0 0.6 0:00 0 cupsd
1385 xfs 12 0 4364 4344 1132 S 0.0 0.8 0:08 0 xfs
1403 daemon 12 0 536 528 480 S 0.0 0.1 0:00 0 atd
1411 root 12 0 1192 1192 968 S 0.0 0.2 0:00 0 login
1412 root 12 0 404 404 356 S 0.0 0.0 0:00 0 mingetty
1413 root 12 0 404 404 356 S 0.0 0.0 0:00 0 mingetty
1414 root 12 0 404 404 356 S 0.0 0.0 0:00 0 mingetty
1415 root 12 0 404 404 356 S 0.0 0.0 0:00 0 mingetty
1416 root 12 0 404 404 356 S 0.0 0.0 0:00 0 mingetty
1417 dlphilp 12 0 1452 1452 1108 S 0.0 0.2 0:00 0 bash
1471 dlphilp 12 0 1060 1060 928 S 0.0 0.2 0:00 0 startx
1482 dlphilp 12 0 608 608 532 S 0.0 0.1 0:00 0 xinit
1487 dlphilp 12 0 2252 2164 1816 S 0.0 0.4 0:01 0 blackbox
1491 dlphilp 12 0 1452 1452 1116 S 0.0 0.2 0:00 0 bash
1552 dlphilp 12 0 1448 1448 1140 S 0.0 0.2 0:00 0 bbkeys
1553 root 12 0 944 944 780 S 0.0 0.1 0:00 0 su
1556 root 12 0 1468 1468 1128 S 0.0 0.2 0:00 0 bash
1899 root 12 0 800 604 528 S 0.0 0.1 0:00 0 dhclient
1970 dlphilp 12 0 70404 68M 2340 S 0.0 13.6 0:01 0 wish
1987 dlphilp 12 0 0 0 0 Z 0.0 0.0 0:00 0
netstat <defunct>
7 Sep
7 Sep
12:15 p.m.
On Tue, Sep 07, 2004 at 10:39:14AM -0400, Dave Phillips wrote:
I've tacked on a copy of top's report for a
plain-vanilla Planet CCRMA
RH 9. I'm going to be advising a client regarding what services he
can/should disable for best-case recording (with a nearly identical
system), so I thought I'd use my own system for the primary tests. I'd
like to know which of the services and jobs listed by top can be safely
disabled during the use of a setup consisting of Jack, Rosegarden, and
Hydrogen, all in the latest & greatest versions from Planet C. Any and
all suggestions will be cosmically appreciated.
Not all services show up in top, some are only run when they are
triggered. You can get a more accurate list with
chkconfig --list | grep 5:on
and looking in /etc/cron.*/
- Steve
12:25 p.m.
Hi Steve:
Thanks, that's exactly what I needed to know. I'm also putting
together a troubleshooting guide for Linux audio users, and that's the
kind of stuff I need for that work too.
Here's from the chkconfig report:
[dlphilp@localhost dlphilp]$ chkconfig --list | grep 5:on
kudzu 0:off 1:off 2:off 3:on 4:on 5:on 6:off
syslog 0:off 1:off 2:on 3:on 4:on 5:on 6:off
netfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off
network 0:off 1:off 2:on 3:on 4:on 5:on 6:off
random 0:off 1:off 2:on 3:on 4:on 5:on 6:off
rawdevices 0:off 1:off 2:off 3:on 4:on 5:on 6:off
pcmcia 0:off 1:off 2:on 3:on 4:on 5:on 6:off
keytable 0:off 1:on 2:on 3:on 4:on 5:on 6:off
apmd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
atd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
gpm 0:off 1:off 2:on 3:on 4:on 5:on 6:off
autofs 0:off 1:off 2:off 3:on 4:on 5:on 6:off
iptables 0:off 1:off 2:on 3:on 4:on 5:on 6:off
isdn 0:off 1:off 2:on 3:on 4:on 5:on 6:off
sshd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
portmap 0:off 1:off 2:off 3:on 4:on 5:on 6:off
nfslock 0:off 1:off 2:off 3:on 4:on 5:on 6:off
sendmail 0:off 1:off 2:on 3:off 4:on 5:on 6:off
rhnsd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off
anacron 0:off 1:off 2:on 3:on 4:on 5:on 6:off
xfs 0:off 1:off 2:on 3:on 4:on 5:on 6:off
xinetd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
cups 0:off 1:off 2:on 3:on 4:on 5:on 6:off
canna 0:off 1:off 2:on 3:off 4:on 5:on 6:off
alsasound 0:off 1:off 2:on 3:on 4:on 5:on 6:off
MidiShare 0:off 1:off 2:on 3:on 4:on 5:on 6:off
While some of this report is cryptic to me, I wonder about some things
like the apmd, isdn, pcmcia, portmap, and sendmail entries. Am I correct
to assume I can do without them at any time, i.e., not only during
recording ?
Best regards,
dp
Steve Harris wrote:
On Tue, Sep 07, 2004 at 10:39:14AM -0400, Dave Phillips
wrote:
I've tacked on a copy of top's report for
a plain-vanilla Planet CCRMA
RH 9. I'm going to be advising a client regarding what services he
can/should disable for best-case recording (with a nearly identical
system), so I thought I'd use my own system for the primary tests. I'd
like to know which of the services and jobs listed by top can be safely
disabled during the use of a setup consisting of Jack, Rosegarden, and
Hydrogen, all in the latest & greatest versions from Planet C. Any and
all suggestions will be cosmically appreciated.
Not all services show up in top, some are only run when they are
triggered. You can get a more accurate list with
chkconfig --list | grep 5:on
and looking in /etc/cron.*/
- Steve
1:41 p.m.
On Tue, Sep 07, 2004 at 11:00:33AM -0400, Dave Phillips wrote:
Hi Steve:
Thanks, that's exactly what I needed to know. I'm also putting
together a troubleshooting guide for Linux audio users, and that's the
kind of stuff I need for that work too.
Cool, good idea.
I'll take a not-very-expert crack at this:
Here's from the chkconfig report:
[dlphilp@localhost dlphilp]$ chkconfig --list | grep 5:on
kudzu 0:off 1:off 2:off 3:on 4:on 5:on 6:off
you can kill kudzu if you're not going to be installing
new hardware while recording :-)
syslog 0:off 1:off 2:on 3:on 4:on
5:on 6:off
i'd leave that alone, logs are always good to have...
netfs 0:off 1:off 2:off 3:on 4:on
5:on 6:off
dunno. Do you use any network filesystems?
network 0:off 1:off 2:on 3:on 4:on
5:on 6:off
I'd probably leave it alone, not sure.
random 0:off 1:off 2:on 3:on 4:on
5:on 6:off
I don't think this actually does anything after
startup.
rawdevices 0:off 1:off 2:off 3:on 4:on
5:on 6:off
dunno what that is.
keytable 0:off 1:on 2:on 3:on 4:on
5:on 6:off
don't think this does anything after startup, dunno.
pcmcia 0:off 1:off 2:on 3:on 4:on
5:on 6:off
is this even a laptop?
apmd 0:off 1:off 2:on 3:on 4:on
5:on 6:off
don't need it.
atd 0:off 1:off 2:off 3:on 4:on
5:on 6:off
don't need it.
gpm 0:off 1:off 2:on 3:on 4:on
5:on 6:off
probably don't need it if you're running X and/or don't care
about mouse on console, UNLESS your X is configured to use /dev/gmpdata
for its mouse events.
autofs 0:off 1:off 2:off 3:on 4:on
5:on 6:off
not needed unless you use network filesystems.
iptables 0:off 1:off 2:on 3:on 4:on
5:on 6:off
firewall stuff... I'd leave it on unless networking is off...
but then maybe it's another run-once-at-startup script.
isdn 0:off 1:off 2:on 3:on 4:on
5:on 6:off
do you really have an ISDN card? :-)
sshd 0:off 1:off 2:on 3:on 4:on
5:on 6:off
Maybe not necessary, but can be handy to have another box
ssh'd in if you manage to lock up under X.
portmap 0:off 1:off 2:off 3:on 4:on
5:on 6:off
i think you need that if networking is up.
nfslock 0:off 1:off 2:off 3:on 4:on
5:on 6:off
nfs again...
sendmail 0:off 1:off 2:on 3:off 4:on
5:on 6:off
don't really need it.
rhnsd 0:off 1:off 2:off 3:on 4:on
5:on 6:off
dunno what that is.
crond 0:off 1:off 2:on 3:on 4:on
5:on 6:off
anacron 0:off 1:off 2:on 3:on 4:on 5:on 6:off
kill em both.
xfs 0:off 1:off 2:on 3:on 4:on
5:on 6:off
need that for X.
xinetd 0:off 1:off 2:off 3:on 4:on
5:on 6:off
not needed unless you think you're going to want random network services
being launched on demand ...
cups 0:off 1:off 2:on 3:on 4:on
5:on 6:off
printing, do you need that?
canna 0:off 1:off 2:on 3:off 4:on
5:on 6:off
dunno what that is.
alsasound 0:off 1:off 2:on 3:on 4:on
5:on 6:off
MidiShare 0:off 1:off 2:on 3:on 4:on 5:on 6:off
presumably you want these :)
--
Paul Winkler
http://www.slinkp.com
2:13 p.m.
On Tuesday 07 September 2004 11:25 am, Paul Winkler wrote:
Just save/loads the random seed
Just for NFS.. some other things like drac use it but they're all esoteric
name service for something
They're mutually exclusive. This is a good time to point out just because the
initscripts/links are there doesn't mean the programs they refer to are.
On Tue, Sep 07, 2004 at 11:00:33AM -0400, Dave
Phillips wrote:
Thats ifup
Hi Steve:
Thanks, that's exactly what I needed to know. I'm also putting
together a troubleshooting guide for Linux audio users, and that's the
kind of stuff I need for that work too.
Cool, good idea.
I'll take a not-very-expert crack at this:
Here's from the chkconfig report:
[dlphilp@localhost dlphilp]$ chkconfig --list | grep 5:on
kudzu 0:off 1:off 2:off 3:on 4:on 5:on 6:off
you can kill kudzu if you're not going to be installing
new hardware while recording :-)
syslog 0:off 1:off 2:on 3:on
4:on 5:on 6:off
i'd leave that alone, logs are always good to have...
netfs 0:off 1:off 2:off 3:on
4:on 5:on 6:off
dunno. Do you use any network filesystems?
network 0:off 1:off 2:on 3:on
4:on 5:on 6:off
I'd probably leave it alone, not sure.
random
0:off 1:off 2:on 3:on 4:on 5:on 6:off
I don't think this actually does anything after startup.
rawdevices
0:off 1:off 2:off 3:on 4:on 5:on 6:off
dunno what that is.
keytable 0:off 1:on 2:on 3:on
4:on 5:on 6:off
don't think this does anything after startup, dunno.
pcmcia 0:off 1:off 2:on 3:on
4:on 5:on 6:off
is this even a laptop?
apmd 0:off 1:off 2:on 3:on
4:on 5:on 6:off
don't need it.
atd 0:off 1:off 2:off 3:on
4:on 5:on 6:off
don't need it.
gpm 0:off 1:off 2:on 3:on
4:on 5:on 6:off
probably don't need it if you're running X and/or don't care
about mouse on console, UNLESS your X is configured to use /dev/gmpdata
for its mouse events.
autofs 0:off 1:off 2:off 3:on
4:on 5:on 6:off
not needed unless you use network filesystems.
iptables 0:off 1:off 2:on 3:on
4:on 5:on 6:off
firewall stuff... I'd leave it on unless networking is off...
but then maybe it's another run-once-at-startup script.
isdn 0:off 1:off 2:on 3:on
4:on 5:on 6:off
do you really have an ISDN card? :-)
sshd 0:off 1:off 2:on 3:on
4:on 5:on 6:off
Maybe not necessary, but can be handy to have another box
ssh'd in if you manage to lock up under X.
portmap 0:off 1:off 2:off 3:on
4:on 5:on 6:off
i think you need that if networking is up.
nfslock
0:off 1:off 2:off 3:on 4:on 5:on 6:off
nfs again...
sendmail 0:off 1:off 2:on 3:off
4:on 5:on 6:off
don't really need it.
rhnsd 0:off 1:off 2:off 3:on
4:on 5:on 6:off
dunno what that is. crond 0:off 1:off 2:on 3:on
4:on 5:on 6:off
anacron 0:off 1:off 2:on 3:on 4:on 5:on 6:off
kill em both.
xfs
0:off 1:off 2:on 3:on 4:on 5:on 6:off
need that for X.
xinetd 0:off 1:off 2:off 3:on
4:on 5:on 6:off
not needed unless you think you're going to want random network services
being launched on demand ...
cups 0:off 1:off 2:on 3:on
4:on 5:on 6:off
printing, do you need that?
canna 0:off 1:off 2:on 3:off
4:on 5:on 6:off
dunno what that is.
alsasound 0:off 1:off 2:on 3:on
4:on 5:on 6:off
MidiShare 0:off 1:off 2:on 3:on 4:on 5:on 6:off
presumably you want these :)
2:21 p.m.
Greetings:
Paul, John, thanks very much for the enlightening information. I'll
edit my own system, check it, then advise my client accordingly.
Dare I say it ? I dare: You guys rock...
Best,
dp
8 Sep
8 Sep
1:47 a.m.
On Tuesday 07 September 2004 12:21 pm, Steve Harris wrote:
On Tue, Sep 07, 2004 at 11:55:36 -0400, John Check
wrote:
name service for something
Its the stuff that make sure your machine is secure with up-to-date
patches.
Ah. Okay well, the "rh" stands for redhat (I hope) ;)
rhnsd 0:off 1:off 2:off 3:on 4:on
5:on 6:off
dunno what that is. - Steve
7 Sep
7 Sep
2:37 p.m.
On Tue, Sep 07, 2004 at 11:25:16 -0400, Paul Winkler wrote:
Whoa, removing it with chkconfig will stop it being run a boot time.
Probably best to leave it.
Only NFS uses it AFAIK.
Not neccesaruly a good idea, you might need your logs to be rolled
every now and again.
- Steve
[dlphilp@localhost dlphilp]$ chkconfig --list | grep 5:on
kudzu 0:off 1:off 2:off 3:on 4:on 5:on 6:off
you can kill kudzu if you're not going to be installing
new hardware while recording :-) portmap
0:off 1:off 2:off 3:on 4:on 5:on 6:off
i think you need that if networking is up. crond
0:off 1:off 2:on 3:on 4:on 5:on 6:off
anacron 0:off 1:off 2:on 3:on 4:on 5:on 6:off
kill em both.
2:41 p.m.
On Tue, Sep 07, 2004 at 05:20:48PM +0100, Steve Harris wrote:
Only NFS uses it AFAIK.
good to know, thanks.
Not neccesaruly a good idea, you might need your logs to be rolled
every now and again.
I didn't say remove them! I just meant stop them while
recording / performing since you really don't want to kick off
arbitrary scripts at 1 AM just when your muse strikes :-)
I'd probably do it with a custom runlevel.
--
Paul Winkler
http://www.slinkp.com
On Tue, Sep 07, 2004 at 11:25:16 -0400, Paul Winkler
wrote:
Whoa, removing it with chkconfig will stop it being run a boot time.
Probably best to leave it.
I didn't say remove it, just stop any daemons temporarily.
[dlphilp@localhost dlphilp]$ chkconfig --list | grep 5:on
kudzu 0:off 1:off 2:off 3:on 4:on 5:on 6:off
you can kill kudzu if you're not going to be installing
new hardware while recording :-) portmap 0:off 1:off 2:off 3:on 4:on
5:on 6:off
i think you need that if networking is up. crond 0:off 1:off 2:on 3:on 4:on
5:on 6:off
anacron 0:off 1:off 2:on 3:on 4:on 5:on 6:off
kill em both.
2:51 p.m.
On Tue, Sep 07, 2004 at 12:25:00 -0400, Paul Winkler wrote:
I didn't say remove them! I just meant stop them
while
recording / performing since you really don't want to kick off
arbitrary scripts at 1 AM just when your muse strikes :-)
OK, well we're discussing chkconfig output, so I though you meant
"chkconfig foo off"-ing them. But, just because they appear in chkconfig
doesnt mean they actually do naythign at runtime, eg. kudzu only runs when
you boot.
I'd probably do it with a custom runlevel.
Same here.
- Steve
8 Sep
8 Sep
1:48 a.m.
On Tuesday 07 September 2004 12:20 pm, Steve Harris wrote:
On Tue, Sep 07, 2004 at 11:25:16 -0400, Paul Winkler
wrote:
Whoa, removing it with chkconfig will stop it being run a boot time.
Probably best to leave it.
Only NFS uses it AFAIK.
Not neccesaruly a good idea, you might need your logs to be rolled
every now and again.
anacron is probably the better choice then because when you fire it up,
it'll do jobs scheduled for when it was down.
[dlphilp@localhost dlphilp]$ chkconfig --list | grep 5:on
kudzu 0:off 1:off 2:off 3:on 4:on 5:on 6:off
you can kill kudzu if you're not going to be installing
new hardware while recording :-) portmap
0:off 1:off 2:off 3:on 4:on 5:on 6:off
i think you need that if networking is up. crond
0:off 1:off 2:on 3:on 4:on 5:on 6:off
anacron 0:off 1:off 2:on 3:on 4:on 5:on 6:off
kill em both.
- Steve
7 Sep
7 Sep
1:57 p.m.
On Tuesday 07 September 2004 11:00 am, Dave Phillips wrote:
Hi Steve:
Thanks, that's exactly what I needed to know. I'm also putting
together a troubleshooting guide for Linux audio users, and that's the
kind of stuff I need for that work too.
Here's from the chkconfig report:
[dlphilp@localhost dlphilp]$ chkconfig --list | grep 5:on
kudzu 0:off 1:off 2:off 3:on 4:on 5:on 6:off
syslog 0:off 1:off 2:on 3:on 4:on 5:on 6:off
netfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off
network 0:off 1:off 2:on 3:on 4:on 5:on 6:off
random 0:off 1:off 2:on 3:on 4:on 5:on 6:off
rawdevices 0:off 1:off 2:off 3:on 4:on 5:on 6:off
pcmcia 0:off 1:off 2:on 3:on 4:on 5:on 6:off
keytable 0:off 1:on 2:on 3:on 4:on 5:on 6:off
apmd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
atd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
gpm 0:off 1:off 2:on 3:on 4:on 5:on 6:off
autofs 0:off 1:off 2:off 3:on 4:on 5:on 6:off
iptables 0:off 1:off 2:on 3:on 4:on 5:on 6:off
isdn 0:off 1:off 2:on 3:on 4:on 5:on 6:off
sshd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
portmap 0:off 1:off 2:off 3:on 4:on 5:on 6:off
nfslock 0:off 1:off 2:off 3:on 4:on 5:on 6:off
sendmail 0:off 1:off 2:on 3:off 4:on 5:on 6:off
rhnsd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off
anacron 0:off 1:off 2:on 3:on 4:on 5:on 6:off
xfs 0:off 1:off 2:on 3:on 4:on 5:on 6:off
xinetd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
cups 0:off 1:off 2:on 3:on 4:on 5:on 6:off
canna 0:off 1:off 2:on 3:off 4:on 5:on 6:off
alsasound 0:off 1:off 2:on 3:on 4:on 5:on 6:off
MidiShare 0:off 1:off 2:on 3:on 4:on 5:on 6:off
While some of this report is cryptic to me, I wonder about some things
like the apmd, isdn, pcmcia, portmap, and sendmail entries. Am I correct
to assume I can do without them at any time, i.e., not only during
recording ?
apmd is power management, so turning that off is good, but you can kill that
in you kernel too
isdn - unless you have ISDN hardware it's not doing anything
pcmcia - if it ain't a laptop buh-bye, but if it ain't a laptop you don't have
it.
portmap - only used by NFS, no NFS mounts, you don't need
sendmail - augh, depends on what mode it runs, but if you kill it you won't
get any reports
So, first 3 can be stripped from the kernel, then you don't have to worry even
though they're hardware dependant. Latter 2 can be turned off, but if
sendmail isn't running in daemon mode it's not hurting anything.
BTW - the implementation report dealie is coming along. Should be ready "Real
Soon Now"
Best regards,
dp
Steve Harris wrote:
>On Tue, Sep 07, 2004 at 10:39:14AM -0400, Dave Phillips wrote:
>> I've tacked on a copy of top's report for a plain-vanilla Planet CCRMA
>>RH 9. I'm going to be advising a client regarding what services he
>>can/should disable for best-case recording (with a nearly identical
>>system), so I thought I'd use my own system for the primary tests. I'd
>>like to know which of the services and jobs listed by top can be safely
>>disabled during the use of a setup consisting of Jack, Rosegarden, and
>>Hydrogen, all in the latest & greatest versions from Planet C. Any and
>>all suggestions will be cosmically appreciated.
>
>Not all services show up in top, some are only run when they are
>triggered. You can get a more accurate list with
>chkconfig --list | grep 5:on
>and looking in /etc/cron.*/
>
>- Steve
7521
days inactive
7521
days old
linux-audio-user@lists.linuxaudio.org
12 comments
4 participants
participants (4)
-
Dave Phillips -
John Check -
Paul Winkler -
Steve Harris