Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Aug 26, 2004, at 4:00 PM, Matthew Valites wrote: > >> Isn't ntpd the ntp server? I don't want my workstation being an ntp >> server all the time... Maybe I'm confused about how ntpd works. > > ntpd is just the ntp client running as a daemon. You most likly have > a few daemons running on your machine (kjournald, xinetd, acpid, > cupsd, crond, etc.) > ~Matt Yeah, I'm aware of that, but to prefer to keep the number of daemons to a minimum. For example, I try not to run cupsd unless I must. KDE can connect to a remote cupsd, and since I don't have any local printers, there's no point in running it locally. I just didn't realize that ntpd was also the ntp client. I still don't get how my clock could have 4 seconds of drift in a single day. Is that normal? -Josh
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |