portmaster not ask for port deletion
hail, portmaster is great, but this is keeping me from using it.I want to fire a portmaster -af and let it there until its done. for every package it asks this. is ther any way to make it not ask ? delete and go ahead ? thanks, matheus ps:unless this is what portmaster's man calls backup package (and I'm not sure it is) I found no way to do this in the man -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: portmaster not ask for port deletion
On Mon, Aug 24, 2009 at 12:03:40PM -0300, Nenhum_de_Nos wrote: hail, portmaster is great, but this is keeping me from using it.I want to fire a portmaster -af and let it there until its done. for every package it asks this. is ther any way to make it not ask ? delete and go ahead ? thanks, matheus ps:unless this is what portmaster's man calls backup package (and I'm not sure it is) I found no way to do this in the man While recursing through the dependencies, if a port is marked IS_INTERAC- TIVE this will be flagged. In the absence of this notification, under normal circumstances the only user interaction required after the port starts building is to answer questions about the deletion of stale dist- files. This can be eliminated with the -d or -D options. use -d to auto-delete, or -D for keeping the distfiles. Zlo signature.asc Description: Digital signature
Re: portmaster not ask for port deletion
On Mon, August 24, 2009 12:06, Marc Olzheim wrote: On Mon, Aug 24, 2009 at 12:03:40PM -0300, Nenhum_de_Nos wrote: hail, portmaster is great, but this is keeping me from using it.I want to fire a portmaster -af and let it there until its done. for every package it asks this. is ther any way to make it not ask ? delete and go ahead ? thanks, matheus ps:unless this is what portmaster's man calls backup package (and I'm not sure it is) I found no way to do this in the man While recursing through the dependencies, if a port is marked IS_INTERAC- TIVE this will be flagged. In the absence of this notification, under normal circumstances the only user interaction required after the port starts building is to answer questions about the deletion of stale dist- files. This can be eliminated with the -d or -D options. use -d to auto-delete, or -D for keeping the distfiles. Zlo thanks, I just got to the options, not read it though. now I see I should. Thanks, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Potential 8.0-BETA3 regression ? acd0 no longer probes/attaches
On Sun, Aug 23, 2009 at 11:26 PM, Pascal Hofsteecael...@gmail.com wrote: I took this weekend to install a fresh 8.0-BETA2 on my old Dell Lattitude D520, and after the initial install proceeded with a typical buildworld run. Now with the new kernel (which reports itself as 8.0-BETA3) my CD/DVD combo drive has gone entirely missing. Booting the older 8.0-BETA2 kernel does probe/attach acd0 though. Any else that can affirm missing CD/DVD drives after upgrading to 8.0-BETA3 ? Following up on my own post I just noticed (after putting my laptop on its docking station) that when it's docked (with acpi_dock loaded) it DOES find the CD/DVD drive. I expect something odd is going on when acpi_dock is loaded but the system is not actually on the docking station. I'll keep a closer eye on things the next couple of days but i think it's safe to assume that although the behaviour is interesting ... it is not a regression in BETA3. -- Pascal Hofstee ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
named stop not stopping
We had an issue with the /etc/rc.d/named script this morning where it looped/hung in the wait_for_pids subroutine. We run a job to restart named which calls the /etc/rc.d/named script with a stop command. For some reason named did not stop properly and the process continued to list PIDs from the wait_for_pids subroutine forever. Has anyone ever encountered this before? We are running 7.2 stable and bind 9.4.3-P3 on an AMD system. Thanks, LB ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
8.0-BETA3 Available
The third of the BETA builds for the FreeBSD-8.0 release cycle is now available. All major work related to new features in 8.0 has been completed and we are shifting into bugfix only mode for the balance of the release cycle. Debugging features (e.g. WITNESS) are still enabled but will be removed from stable/8 between now and RC1 so performance is still impacted a bit by that. Also note that, as mentioned previously on the mailing lists, we did do a shared library version bump after BETA2 was announced (bump was done July 19th with svn commit r195767) so if you update a system that was last rebuilt earlier than that it would be a good idea to rebuild all user-level applications including the ports/packages. The current release target date is the 3rd week of September. We expect to be doing two Release Candidate builds (RC's), RC1 builds scheduled for next weekend. As you probably know our schedules often slip but that's the current target. More information about the current state of the release is available here: http://wiki.freebsd.org/8.0TODO If you notice problems you can report them through the normal Gnats PR system or on the freebsd-current mailing list. I do cross-post announcements to freebsd-stable because this particular release is about to become a stable branch but when it comes to watching for issues related to the release most of the developers pay more attention to the freebsd-current list. ISO images for all supported architectures are available on the FTP sites, (sparc64 was uploaded a short time ago and may not be available on some sites yet) and a memory stick image is available for amd64/i386 architectures. For amd64/i386 architectures the cdrom and memstick images include the documentation packages this time but no other packages. The DVD image includes a first rough pass at what packages will be available but the list will certainly change between now and release. None of the other images include packages. If you are using csup/cvsup methods to update an older system the branch tag to use is now RELENG_8. If you have not noticed it before now you may want to check out the -F option for mergemaster(8). We still have the issue of all the cvs ID's being changed as part of creating a new branch due to the svn to cvs export mechanism in place but mergemaster's -F option can help reduce the headache that causes. The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.0-RELEASE, 7.1-RELEASE, 7.2-RELEASE, 8.0-BETA1, or 8.0-BETA2 can upgrade as follows: # freebsd-update upgrade -r 8.0-BETA3 During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components: # freebsd-update install At this point, users of systems being upgraded from FreeBSD 7.x will be prompted by freebsd-update to rebuild all third-party applications (e.g., ports installed from the ports tree) due to updates in system libraries. See http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html for mode details. After updating installed third-party applications (and again, only if freebsd-update printed a message indicating that this was necessary), run freebsd-update again so that it can delete the old (no longer used) system libraries: # freebsd-update install Finally, reboot into 8.0-BETA3: # shutdown -r now MD5/SHA256 checksums for the image files: MD5 (8.0-BETA3-amd64-bootonly.iso) = 04afc4d7c4181b6920a2d2f846e2 MD5 (8.0-BETA3-amd64-disc1.iso) = 638ccbd57fae57d040c7a4dc743bdf06 MD5 (8.0-BETA3-amd64-dvd1.iso) = c54582b22255a3e6b02cbea08410923b MD5 (8.0-BETA3-amd64-livefs.iso) = f2e7eb9e4e9f5a3a7a30e44ba5690f1c MD5 (8.0-BETA3-amd64-memstick.img) = 0c68de004f6acf57f2af837f57fc5e22 MD5 (8.0-BETA3-i386-bootonly.iso) = 20cbf19ec1ccce13f12652eff1037d63 MD5 (8.0-BETA3-i386-disc1.iso) = c52769420ce90c801a43384a00399eaf MD5 (8.0-BETA3-i386-dvd1.iso) = dc20720bc59612615579fd2e3b4cba3a MD5 (8.0-BETA3-i386-livefs.iso) = 711f1ed364ab5b776c1e079272e7e19a MD5 (8.0-BETA3-i386-memstick.img) = a8730c7307e5021b1d6ad277591d50f6 MD5 (8.0-BETA3-ia64-bootonly.iso) = 06e3d855c9d636bb773e57c3fbbf4e28 MD5 (8.0-BETA3-ia64-disc1.iso) = 3852a7ed62b3f9e1ad7c0a8c8dc9df0a MD5 (8.0-BETA3-ia64-disc2.iso) = c457544b250630d984bbb2b4da45866a MD5 (8.0-BETA3-ia64-disc3.iso) = 7ed9a1287a1339b81b70cc5c9b797deb MD5 (8.0-BETA3-ia64-dvd1.iso) = 7ab723a4e305e793742939f99192209a MD5 (8.0-BETA3-ia64-livefs.iso) = 12dc19c7c344618dedce1bb99ffba4a2 MD5 (8.0-BETA3-pc98-bootonly.iso) = 6078e11ef5b21a9ed5504d7ccc591567 MD5 (8.0-BETA3-pc98-disc1.iso) = 55e840ba7cbf0447ae7a4e39029f564e MD5
Re: portmaster not ask for port deletion
Nenhum_de_Nos wrote: hail, portmaster is great, but this is keeping me from using it.I want to fire a portmaster -af and let it there until its done. for every package it asks this. is ther any way to make it not ask ? delete and go ahead ? You really want to read the man page thoroughly before you begin using portmaster. I've taken a lot of time to try and explain how it works in the man page, and what your options are. In particular, you probably do not really want to use the -f option on a regular basis since that does not do what it does in portupgrade. In portmaster using '-af' would rebuild all of your ports, not just the ones that need upgrading. It sounds to me like what you're seeing is portmaster asking whether or not you want to delete the distfiles after an upgrade. The easiest way to deal with that is to use '-aD' and then when it's done use either --clean-distfiles or --clean-distfiles-all. Once again, see the man page for more information on those options. hope this helps, Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: named stop not stopping
Lisa Besko wrote: We had an issue with the /etc/rc.d/named script this morning where it looped/hung in the wait_for_pids subroutine. We run a job to restart named which calls the /etc/rc.d/named script with a stop command. For some reason named did not stop properly and the process continued to list PIDs from the wait_for_pids subroutine forever. Has anyone ever encountered this before? We are running 7.2 stable and bind 9.4.3-P3 on an AMD system. Thanks, LB Has named's rc script worked OK before? If not, it might be a config problem like mine. I found that after I added pid-file/var/run/named/pid; to the options section of my named.conf file, the rc script was able to stop/restart a running named process. Hope this helps, Guy Helmer ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: portmaster not ask for port deletion
Date: Mon, 24 Aug 2009 12:54:54 -0700 From: Doug Barton do...@freebsd.org Sender: owner-freebsd-sta...@freebsd.org Nenhum_de_Nos wrote: hail, portmaster is great, but this is keeping me from using it.I want to fire a portmaster -af and let it there until its done. for every package it asks this. is ther any way to make it not ask ? delete and go ahead ? You really want to read the man page thoroughly before you begin using portmaster. I've taken a lot of time to try and explain how it works in the man page, and what your options are. In particular, you probably do not really want to use the -f option on a regular basis since that does not do what it does in portupgrade. In portmaster using '-af' would rebuild all of your ports, not just the ones that need upgrading. It sounds to me like what you're seeing is portmaster asking whether or not you want to delete the distfiles after an upgrade. The easiest way to deal with that is to use '-aD' and then when it's done use either --clean-distfiles or --clean-distfiles-all. Once again, see the man page for more information on those options. Just in case someone reads this and tries 'portupgrade -af', it also will re-build all installed ports, whether they need upgrading. This is the command to re-build ALL ports when the library versions get bumped (as they did recently for 8.0BETA). To just update the ports that need updating, the command is 'portupgrade -a', probably the same as in portmaster. In either case (portupgrade or portmaster), read the man pages BEFORE shooting yourself in the foot. Both can certainly do that. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: named stop not stopping
Date: Mon, 24 Aug 2009 15:01:53 -0500 From: Guy Helmer ghel...@palisadesys.com Sender: owner-freebsd-sta...@freebsd.org Lisa Besko wrote: We had an issue with the /etc/rc.d/named script this morning where it looped/hung in the wait_for_pids subroutine. We run a job to restart named which calls the /etc/rc.d/named script with a stop command. For some reason named did not stop properly and the process continued to list PIDs from the wait_for_pids subroutine forever. Has anyone ever encountered this before? We are running 7.2 stable and bind 9.4.3-P3 on an AMD system. Thanks, LB Has named's rc script worked OK before? If not, it might be a config problem like mine. I found that after I added pid-file/var/run/named/pid; to the options section of my named.conf file, the rc script was able to stop/restart a running named process. Hope this helps, Guy Helmer Odd. Unless something (like /etc/defaults/rc.conf) else was touched, this should not be required. It is already in /etc/defaults/rc.conf, a file that should be modified only with a really good understanding of the way it is used. Here is the current defaults for named: named_pidfile=/var/run/named/pid # Must set this in named.conf as well You probably should only put the line 'named_enable=yes' into /etc/rc.conf. Do not put it into /etc/defaults/rc.conf or change the entry in that file! Changes should only be made to /etc/rc.conf. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: named stop not stopping
Kevin Oberman wrote: Date: Mon, 24 Aug 2009 15:01:53 -0500 From: Guy Helmer ghel...@palisadesys.com Sender: owner-freebsd-sta...@freebsd.org Lisa Besko wrote: We had an issue with the /etc/rc.d/named script this morning where it looped/hung in the wait_for_pids subroutine. We run a job to restart named which calls the /etc/rc.d/named script with a stop command. For some reason named did not stop properly and the process continued to list PIDs from the wait_for_pids subroutine forever. Has anyone ever encountered this before? We are running 7.2 stable and bind 9.4.3-P3 on an AMD system. Thanks, LB Has named's rc script worked OK before? If not, it might be a config problem like mine. I found that after I added pid-file/var/run/named/pid; to the options section of my named.conf file, the rc script was able to stop/restart a running named process. Hope this helps, Guy Helmer Odd. Unless something (like /etc/defaults/rc.conf) else was touched, this should not be required. It is already in /etc/defaults/rc.conf, a file that should be modified only with a really good understanding of the way it is used. Here is the current defaults for named: named_pidfile=/var/run/named/pid # Must set this in named.conf as well You probably should only put the line 'named_enable=yes' into /etc/rc.conf. Do not put it into /etc/defaults/rc.conf or change the entry in that file! Changes should only be made to /etc/rc.conf. Right, and it looks like the default pid file in named is /var/run/named.pid, so until I added a pid-file line to named.conf to match named_pidfile's setting in /etc/default/rc.conf, the named rc script wasn't successfully stopping/restarting named. Guy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: named stop not stopping
Kevin Oberman wrote: Has named's rc script worked OK before? If not, it might be a config problem like mine. I found that after I added pid-file/var/run/named/pid; to the options section of my named.conf file, the rc script was able to stop/restart a running named process. Hope this helps, Guy Helmer Odd. Unless something (like /etc/defaults/rc.conf) else was touched, this should not be required. Guy was referring to /etc/namedb/named.conf, not /etc/*rc.conf*. FWIW, the proper line is in the default named.conf file. I always suggest that users start with that, and build from there. Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: named stop not stopping
Lisa Besko wrote: We had an issue with the /etc/rc.d/named script this morning where it looped/hung in the wait_for_pids subroutine. We run a job to restart named which calls the /etc/rc.d/named script with a stop command. For some reason named did not stop properly and the process continued to list PIDs from the wait_for_pids subroutine forever. Has anyone ever encountered this before? We are running 7.2 stable and bind 9.4.3-P3 on an AMD system. First, please verify that you have the latest version of /etc/rc.d/named installed. Second, this could happen if the call in that script to rndc succeeded, but for some reason rndc was not able to actually kill the binary. In that case there should be something in the logs that indicates what the problem is. hth, Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: portmaster not ask for port deletion
Kevin Oberman wrote: Just in case someone reads this and tries 'portupgrade -af', it also will re-build all installed ports, whether they need upgrading. This is the command to re-build ALL ports when the library versions get bumped (as they did recently for 8.0BETA). To just update the ports that need updating, the command is 'portupgrade -a', probably the same as in portmaster. Yeah, I should have been more clear. '-af' will do the same thing in both tools. Where it gets interesting is that when specifying individual ports on the command line portmaster does by default what 'portupgrade -f' does. In either case (portupgrade or portmaster), read the man pages BEFORE shooting yourself in the foot. Both can certainly do that. Agreed. :) Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
fix ntptrace man page
Hi all! It's a small fix to ntpdate man page for freebsd 7-stable. commit 541cadb46c21521851327e6de51e1ae349b56453 Author: opv o...@oliverp.teteny.bme.hu Date: Tue Aug 25 04:43:28 2009 +0200 fix the ntprace man file in ntptrace man: --8-- ... The following options are available: -d Turn on some debugging output. ... --8-- but in command line: --8-- Unknown option: d --8-- Signed-off-by: Oliver Pinter oliver.p...@gmail.com diff --git a/usr.sbin/ntp/doc/ntptrace.8 b/usr.sbin/ntp/doc/ntptrace.8 index 554a3c0..bb17d6e 100644 --- a/usr.sbin/ntp/doc/ntptrace.8 +++ b/usr.sbin/ntp/doc/ntptrace.8 @@ -50,8 +50,6 @@ These terms are precisely defined in RFC 1305. .Pp The following options are available: .Bl -tag -width indent -.It Fl d -Turn on some debugging output. .It Fl n Turn off the printing of host names; instead, host IP addresses are given. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
fix ntpd man page
Hi all!
It's one more fix to ntp program set, ntpd man page for freebsd 7-stable.
commit 8d33c5f3a2ab8215f7b8e6efaa44ee1c5f63b4dc
Author: opv o...@oliverp.teteny.bme.hu
Date: Tue Aug 25 05:19:10 2009 +0200
fix ntpd man
man:
-d Specify debugging mode. This option may occur more than once,
with each occurrence indicating greater detail of display.
shell:
/etc# ntpd -d -c /etc/ntp.conf
ntpd: illegal option -- d
ntpd - NTP daemon program - Ver. 4.2.4p5
USAGE: ntpd [ -flag [val] | --name[{=| }val] ]...
Signed-off-by: Oliver Pinter oliver.p...@gmail.com
diff --git a/usr.sbin/ntp/doc/ntpd.8 b/usr.sbin/ntp/doc/ntpd.8
index 5194b75..36e98b3 100644
--- a/usr.sbin/ntp/doc/ntpd.8
+++ b/usr.sbin/ntp/doc/ntpd.8
@@ -104,10 +104,6 @@ Enable the client to synchronize to broadcast servers.
.It Fl c Ar conffile
Specify the name and path of the configuration file, default
.Pa /etc/ntp.conf .
-.It Fl d
-Specify debugging mode.
-This option may occur more than once,
-with each occurrence indicating greater detail of display.
.It Fl D Ar level
Specify debugging level directly.
.It Fl f Ar driftfile
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
