Re: daemons -- who needs'em?

2000-05-01 Thread w trillich
John Pearson wrote: > > On Sun, Apr 30, 2000 at 04:23:50PM -0500, w trillich wrote > > but what i was referring to was the console-happy curses-based gizmo > > that ran only on the FIRST BOOT after installing bare-bones kernel > > stuff from cd. blue screen, white selector bars, and TAB to rotate

Re: daemons -- who needs'em?

2000-04-29 Thread Marek Habersack
** On Apr 28, Brad scribbled: > > > i merely think i have a screwy setting here or there that's > > > needlessly duplicating log messages. settings are the bane of > > > my linux existence, still... > > Now, stop right here for a while. syslog isn't Linux - it's a common > > software, created qui

Re: daemons -- who needs'em?

2000-04-28 Thread Brad
On Fri, Apr 28, 2000 at 05:18:08PM +0200, Marek Habersack wrote: > ** On Apr 28, w trillich scribbled: > > > i merely think i have a screwy setting here or there that's > > needlessly duplicating log messages. settings are the bane of > > my linux existence, still... > Now, stop right here for a

Re: daemons -- who needs'em?

2000-04-28 Thread John Pearson
On Fri, Apr 28, 2000 at 09:45:11AM -0500, w trillich wrote > Joey Hess wrote: > > > > w trillich wrote: > > > > > we need them _both_ because... well... um... > > > > Because syslogd handles the userspace messages, klogd handles the kernel > > > > messages. > > > > > > there's still a AWFUL lot

Re: daemons -- who needs'em?

2000-04-28 Thread Vitux
Honoured Debianites. Isn't it about time to cut this thread? It seems to be evolving into the vi vs emacs vs pico vs idunnowhat or the everlasting dselect struggle. In other words, ideology... I've acquired quite a few tips following it, but now its getting out of hand. (IMHO, etc, please; let's

Re: daemons -- who needs'em?

2000-04-28 Thread Marek Habersack
** On Apr 28, w trillich scribbled: > > > there's still a AWFUL lot of overlap! > > > > No there's not. Please give the people who wrote linux some credit for > > sense. > > i saved the output from > tail -50 /var/log/syslog > tail -50 /var/log/daemon.log > and did a 'diff' on them:

Re: daemons -- who needs'em?

2000-04-28 Thread David Wright
Quoting w trillich ([EMAIL PROTECTED]): > Joey Hess wrote: > > > > w trillich wrote: > > > > > we need them _both_ because... well... um... > > > > Because syslogd handles the userspace messages, klogd handles the kernel > > > > messages. > > > > > > there's still a AWFUL lot of overlap! > > >

Re: daemons -- who needs'em?

2000-04-28 Thread w trillich
Joey Hess wrote: > > w trillich wrote: > > > > we need them _both_ because... well... um... > > > Because syslogd handles the userspace messages, klogd handles the kernel > > > messages. > > > > there's still a AWFUL lot of overlap! > > No there's not. Please give the people who wrote linux som

Re: daemons -- who needs'em?

2000-04-28 Thread Marek Habersack
** On Apr 28, Joey Hess scribbled: > Marek Habersack wrote: > > > rwhod = server for 'whois [EMAIL PROTECTED]' I didn't write that :)) :P > > useless crap (IMHO) But I still hold on to this point of view - completely useless > No, rwhod doesn't have anything to do with whois. How useful it is

Re: daemons -- who needs'em?

2000-04-27 Thread Joey Hess
w trillich wrote: > > > we need them _both_ because... well... um... > > Because syslogd handles the userspace messages, klogd handles the kernel > > messages. > > there's still a AWFUL lot of overlap! No there's not. Please give the people who wrote linux some credit for sense. klogd contains

Re: daemons -- who needs'em?

2000-04-27 Thread Joey Hess
Marek Habersack wrote: > > rwhod = server for 'whois [EMAIL PROTECTED]' > useless crap (IMHO) No, rwhod doesn't have anything to do with whois. How useful it is is ia matter of opinion, I happen to like this a lot: [EMAIL PROTECTED]:~>ruptime box up 142+20:37, 0 users, load 0.00,

Re: daemons -- who needs'em?

2000-04-27 Thread Nathan E Norman
On Thu, Apr 27, 2000 at 11:31:07AM +0200, Marek Habersack wrote: [ snip ] > > 4 ?SW 0:00 [md_thread] > > 5 ?SW 0:00 [md_thread] > You probably don't need these two. They're auto-mounter threads AFAIR Actually they're Multiple Device driver threads (Concat, RAID0, RA

Re: daemons -- who needs'em?

2000-04-27 Thread Marek Habersack
** On Apr 27, w trillich scribbled: > to paraphrase bob hope's theme--thanks for the summaries! > > > > > 2206 ?S 0:00 /sbin/portmap > > Portmapper for the RPC-based services (kinda a dispatch for them) > > > portmap = something to do with Remote-Procedure-Call? > > precisely > > c

Re: daemons -- who needs'em?

2000-04-27 Thread Ethan Benson
On Thu, Apr 27, 2000 at 06:50:49AM -0500, w trillich wrote: > to paraphrase bob hope's theme--thanks for the summaries! > > > > > 2206 ?S 0:00 /sbin/portmap > > Portmapper for the RPC-based services (kinda a dispatch for them) > > > portmap = something to do with Remote-Procedure-Ca

Re: daemons -- who needs'em?

2000-04-27 Thread w trillich
to paraphrase bob hope's theme--thanks for the summaries! > > 2206 ?S 0:00 /sbin/portmap > Portmapper for the RPC-based services (kinda a dispatch for them) > > portmap = something to do with Remote-Procedure-Call? > precisely can i ditch it? is it essential somehow? > > *logd =

Re: daemons -- who needs'em?

2000-04-27 Thread Ethan Benson
On Thu, Apr 27, 2000 at 11:31:07AM +0200, Marek Habersack wrote: > > 2018 ?S 0:00 /usr/sbin/afpd -n server > > 2020 ?S 0:00 /usr/sbin/papd > Don't know these two :)) afpd == AppleTalk Filing Protocol daemon -- exports parts of your filesystem so MacOS users can mount

Re: daemons -- who needs'em?

2000-04-27 Thread Marek Habersack
** On Apr 27, w trillich scribbled: > ever wonder what all those background processes are for? > > me too, and i still do. if you have some answers, please > post them for us newbies. > > # ps t\? > PID TTY STAT TIME COMMAND > 1 ?S 0:06 init [2] parent of all the process

daemons -- who needs'em?

2000-04-27 Thread w trillich
ever wonder what all those background processes are for? me too, and i still do. if you have some answers, please post them for us newbies. # ps t\? PID TTY STAT TIME COMMAND 1 ?S 0:06 init [2] 2 ?SW 0:00 [kflushd] 3 ?SW<0:00 [kswapd]