Date: Mon, 9 Apr 2001 19:01:58 +0300 From: Peter Pentchev <roam@orbitel.bg> To: Vincent Deffontaines <vincent.deffontaines@easynet.fr> Cc: Cy.Schubert@uumail.gov.bc.ca, ports@FreeBSD.org Subject: Re: question about FreeBSD Port: ntp-4.0.99k Message-ID: <20010409190158.A2827@ringworld.oblivion.bg> In-Reply-To: <3AD1D8C9.27FFA6DC@easynet.fr>; from vincent.deffontaines@easynet.fr on Mon, Apr 09, 2001 at 05:44:09PM %2B0200 References: <3AD1D8C9.27FFA6DC@easynet.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, and congratulations for not abandoning FreeBSD at the first problem :) No, seriously - you are not making a mistake at all. This is the case with several programs which are included in the base system, yet are being actively developed, and have newer versions also included as ports. Other such examples are Perl, GCC and (for old FreeBSD systems) SSH. One of the basic premises of the FreeBSD ports system is that it installs everything under a common 'prefix' - /usr/local by default - so that it is easy to distinguish between base system software - everything outside /usr/local - and software packages installed later. This also helps when you have to scratch a system clean to isolate some fault - it is a nice idea to start off with cleaning or completely removing /usr/local, with the complete assurance that you shall be left with a perfectly working FreeBSD system. The best solution in your case would be to tell the system startup scripts to use your newly-installed version of ntpd, and not the old one; to do this, edit your /etc/rc.conf file, and add the following line to the end (or change it if it occurs earlier): xntpd_program="/usr/local/bin/ntpd" ..then either restart your system (not really needed, but the best way to provide a clean startup), or just do: killall ntpd /usr/local/bin/ntpd -p /var/run/ntpd.pid ..and you should be all set :) Of course, if you've changed xntpd_flags in /etc/rc.conf, use your new flags instead of '-p /var/run/ntpd.pid' :) If you are interested in other things you can change in your /etc/rc.conf script, take a loot (but DO NOT MODIFY) /etc/defaults/rc.conf - it lists some variables, their default values, and some comments for each. Hope that helps! :) G'luck, Peter -- If this sentence didn't exist, somebody would have invented it. On Mon, Apr 09, 2001 at 05:44:09PM +0200, Vincent Deffontaines wrote: > Hi > > Sorry for emailing you directly, gonna try to make this short. > I am a bit new to freebsd, so probably what im gonna ask you can be > found somewhere else... sorry about that... > > I saw security updates on ntp (actually saw that on debian/linux) > So I decided to upgrade my freebsd servers as well. > Most of them are running 4.2 stable, with ntp-4.0.99i > > So I do a cvsup -no problem- and I run a "make&&make install" in > /usr/ports/net/ntp (version ntp-4.0.99k) > > The problem is, -I think- file locations have changed. so this update > installs new ntpd version in /usr/local/bin/ntpd, while the ancient one > seems to be in /usr/sbin/ntpd > By the way, install of new version doesnt delete old version of ntpd. > > So if I kill existing ntpd, and launch the new one just doing "ntpd -p > /var/run/ntpd.pid", I think it runs the old version :-( > > Where am I mistaking? > > Thanks for your help, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010409190158.A2827>