Re: time issues and some more

2013-01-16 Thread Dan Daley 

I have noticed similar time issues after upgrading from 8.2 to 8.3.  I haven't 
had time to investigate, but often the time drift "exceeds sanity limit."

So, the problem is present pre 9.x.  I never had this problem when running 8.2.





From: Daniel Braniss 
To: freebsd-stable@freebsd.org
Sent: Wed, January 16, 2013 3:54:44 AM
Subject: time issues and some more

I resently upgraded a Dell PowerEdge R710, to 9.1-stable, we mainly use it as
a backup to several zfs servers (doing send|receive) without major issues till
the upgrade, it was running 8.2-stable.

now, we see that sometime the time drifts, and today I noticed that it was
hung, and once I got unto the ipmi console this is what i got:
[SOL Session operational.  Use ~? for help]
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 3864, size: 12288

and things started moving again,

in /var/log/messages:
Jan 16 03:27:35 store-02 kernel: swap_pager: indefinite wait buffer: bufobj: 
0, blkno: 3864, size: 12288

but the REAL time is 7hs ahead!, so time stood still ?
and now, of course we get:
Jan 16 03:54:19 store-02 ntpd[38163]: time correction of 25216 seconds exceeds 
sanity limit (1000); set clock manually to the correct UTC time.

I will now reboot, and try a newer kernel and check, but any insight will
be very helpful,

thanks,
danny


___
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"
___
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: Documenting 'make config' options

2012-06-08 Thread Dan Daley 

Thanks.  I'll check this script out.





From: Oliver Fromme 
To: freebsd-stable@FreeBSD.ORG; Dan Daley ; Charles 
Sprickman 
; Warren Block ; Vincent Hoffman 

Sent: Fri, June 8, 2012 2:47:37 AM
Subject: Re: Documenting 'make config' options

Dan Daley  wrote:
> I usually use portmaster to install ports. The options dialogs that pop 
> up are often for dependencies. The options dialog gives the name of the 
> port for which the options are being selected, but no description or 
> indication as to why this is being installed (this could be a dependency 
> of a dependency of some dependency of the port I am installing). It's 
> probably too much for this dialog to show why this port is being 
> installed (what other port required this port that is being installed), 
> but a description of what this current port is would be helpful.
> 
> But, if possible, some breadcrumb across the top showing the 
> dependencies which prompted this install would be great:
> 
> Port A --> Port B --> Port C --> Current Port for which options are 
> being chosen

You might want to have a look at my "portup" script.  It can
be used to install ports, and the -w option causes it to use
a split-screen display:  The bottom 80% contain the usual
output from "make", and the top 20% show the progress of the
build, including information about dependencies.  This might
be exactly the "breadcrumb across the top" that you requested.

You can download the current version from here:

http://www.secnetix.de/olli/scripts/portup

For FreeBSD >= 8.x, the -w option requires the "window" port
to be installed (from /usr/ports/misc/window) which was removed
from the base system in FreeBSD 8.x.

Usage for installing ports is simple:

# cd /usr/ports/category/foo
# portup -wy .

Best regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758,  Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

I suggested holding a "Python Object Oriented Programming Seminar",
but the acronym was unpopular.
-- Joseph Strout

___
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: Documenting 'make config' options

2012-06-06 Thread Dan Daley 


I usually use portmaster to install ports. The options dialogs that pop 
up are often for dependencies. The options dialog gives the name of the 
port for which the options are being selected, but no description or 
indication as to why this is being installed (this could be a dependency 
of a dependency of some dependency of the port I am installing). It's 
probably too much for this dialog to show why this port is being 
installed (what other port required this port that is being installed), 
but a description of what this current port is would be helpful.


But, if possible, some breadcrumb across the top showing the 
dependencies which prompted this install would be great:


Port A --> Port B --> Port C --> Current Port for which options are 
being chosen




On 06/06/2012 21:47, Charles Sprickman wrote:

On Jun 6, 2012, at 7:43 PM, Warren Block wrote:


On Wed, 6 Jun 2012, Vincent Hoffman wrote:


On 06/06/2012 22:23, Glen Barber wrote:

On Wed, Jun 06, 2012 at 02:14:46PM -0700, Doug Barton wrote:

On 06/06/2012 11:59, Dave Hayes wrote:

I'm describing more of a use case here, not attempting to specify an
implementation. If a user invokes 'make', a window is presented to them
with various options. It's probably very common that this is met with an
initial reaction of "what the hell do these do?", even from the most
seasoned of admins (presuming they are unfamiliar with the software they
have been asked to install). I claim it would be an improvement to have
that information at the fingertips of the make invoker.

What manner of providing this information would meet your needs?


IMHO, something informing what "THAT" is in devel/subversion option
MOD_DONTDOTHAT would be nice.  :)


Not something I had bothered looking up till now as I hadnt wanted to
use it but the 2nd hit on google,
http://lists.freebsd.org/pipermail/freebsd-ports-bugs/2009-April/161673.html
describes it quite well.
I tend to go with, If i dont know what it is, and its not default, I
probably dont need it.
Unless it looks interesting, then I google it ;)

Maybe an (optional) new file with a longer descriptions of the make
options so as not to crowd the make config dialog?
I dont mind looking up compile time options for software I am installing
but I can see how having a precis available locally might be handy.

Here's an idea: if the description is too long to show in the very limited space, cut it off, 
show a "...", and show the entire description in a two- or three-line text box below 
the main one.  The><  indicate a highlight here:

  ---
  >[ ] GOOFY Build with support for the...<
   [ ] EXAMPLES  Install the examples

  ---
   <   OK>   

   -
   Build with support for the GOOFY framework
   that provides concurrent whoopsies integrated
   with a Perubython interpreter, and stuff.
  ---

The description at the bottom is from whatever option is currently highlighted, 
and changes as the user scrolls through the options.  It would be blank if the 
entire description could be displayed in the space available above.

The advantage of this is that it would work with existing ports, and give the 
ability to use longer descriptions.  The disadvantage is that dialog(1) would 
probably need modifications.

If we're talking about changing dialog(1), let's make sure there's also an "uncheck 
all"/"check all" option.

I'm looking at you, ghostscript:

 wc -l /var/db/ports/ghostscript9/options
  315 /var/db/ports/ghostscript9/options

Charles


___
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"

--
Charles Sprickman
NetEng/SysAdmin
Bway.net - New York's Best Internet www.bway.net
sp...@bway.net - 212.655.9344





___
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"

___
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: Netflix's New Peering Appliance Uses FreeBSD

2012-06-05 Thread Dan Daley 


Maybe their knowledge of Linux drove them to use FreeBSD.  Sorry, 
couldn't resist ;)


On 06/05/2012 19:42, David Magda wrote:

On Jun 5, 2012, at 20:16, Scott Long wrote:


If you have any questions, let me know or follow the information links on the
OpenConnect web site.

Out of curiosity, given that Linux seems popular in so many other places 
(Google, Facebook), is there any particular reason why FreeBSD was chosen for 
this?

I'm sure Linux is used in many other places (much of Netflix's IT 
infrastructure is on Amazon IIRC), so I'm kind of surprised that they went with 
FreeBSD when they probably already have so much knowledge with Linux.

___
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"

___
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: Netflix's New Peering Appliance Uses FreeBSD

2012-06-05 Thread Dan Daley 

I didn't see a link to this information in the e-mail below.  I found this info 
detailed here: 


https://signup.netflix.com/openconnect/software






From: Benjamin Francom 
To: freebsd-stable@freebsd.org
Sent: Tue, June 5, 2012 11:00:01 AM
Subject: Netflix's New Peering Appliance Uses FreeBSD

I just saw this, and thought I'd share:

Open Connect Appliance Software

Netflix delivers streaming content using a combination of intelligent
clients, a central control system, and a network of Open Connect appliances.

When designing the Open Connect Appliance Software, we focused on these
fundamental design goals:

   - Use of Open Source software
   - Ability to efficiently read from disk and write to network sockets
   - High-performance HTTP delivery
   - Ability to gather routing information via BGP

Operating System

For the operating system, we use FreeBSD  version
9.0. This was selected for its balance of stability and features, a strong
development community and staff expertise. We will contribute changes we
make as part of our project to the community through the FreeBSD committers
on our team.
Web server

We use the nginx  web server for its proven
scalability and performance. Netflix audio and video is served via HTTP.
Routing intelligence proxy

We use the BIRD Internet routing daemon  to enable
the transfer of network topology from ISP networks to the Netflix control
system that directs clients to sources of content.
Acknowledgements

We would would like to express our thanks to the FreeBSD community, the
nginx community, and Ondrej and the BIRD team for providing excellent open
source software. We also work directly with Igor, Maxim, Andrew, Sergey,
Ruslan and the rest of the team at nginx.com , who
provide superb development support for our project."

-- 
Benjamin Francom
Information Technology Professional
http://www.benfrancom.com
___
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"
___
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: ntpd couldn't resolve host name on system boot

2012-05-19 Thread Dan Daley 


I haven't had a chance to read through this entire thread yet, but 
wanted to post this in case it helps someone.


ntpd was working fine for me for a while, and then I started getting 
this exact same error.  After a few weeks, I finally started 
troubleshooting and it turned out that I had, at some point, commented 
this out in my rc.conf


defaultrouter="192.168.1.1"

Everything else seemed to work fine (I use DHCP, so assume that it 
figured out the router from that).  Once I uncommented that line, ntpd 
started working again.  Maybe the netwait and/or dhcp sync would allow 
ntpd to work without having to specify a default router in rc.conf, but 
I haven't played with that yet.




On 05/18/2012 08:28, Matthew Doughty wrote:

Hello Bjoern,

It's still a problem for me.  Here is a list of my system information:

Hostname freenas.local  FreeNAS Build FreeNAS-8.0.4-RELEASE-p1-x64 (11059)
Platform AMD Athlon(tm) II X2 250 Processor  Memory 8144MB  System Time Fri
May 18 09:07:22 2012  Uptime 9:07AM up 6 mins, 0 users  Load Average 0.00,
0.21, 0.16  OS Version FreeBSD 8.2-RELEASE-p6
Are you refering to the OS version? 9.0 or 8.3?  Looks like I'm using 8.2.

Best regards,
Matthew


On 17 May 2012 16:48, Bjoern A. Zeeb  wrote:


On 17. May 2012, at 15:03 , Matthew Doughty wrote:


Dear Jerermy,

Whilst searching for a solution to a problem, I found your post:


http://lists.freebsd.org/pipermail/freebsd-stable/2011-October/064350.html

Please could you explain how I can implement the netwait script to solve
the problem?  I'm new to freenas/BSD but am willing to try working from

the

Cmd line.

ntpd in head 9.0 and later and 8.3 and later should not exhibit that
problem
anymore as it was fixed.   Could you please tell me if that is not the
case?

/bz

--
Bjoern A. Zeeb You have to have visions!
   It does not matter how good you are. It matters what good you do!





___
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: ntpd couldn't resolve host name on system boot

2012-05-19 Thread Dan Daley 


I haven't had a chance to read through this entire thread yet, but 
wanted to post this in case it helps someone.


ntpd was working fine for me for a while, and then I started getting 
this exact same error.  After a few weeks, I finally started 
troubleshooting and it turned out that I had, at some point, commented 
this out in my rc.conf


defaultrouter="192.168.1.1"

Everything else seemed to work fine (I use DHCP, so assume that it 
figured out the router from that).  Once I uncommented that line, ntpd 
started working again.  Maybe the netwait and/or dhcp sync would allow 
ntpd to work without having to specify a default router in rc.conf, but 
I haven't played with that yet.




On 05/18/2012 08:28, Matthew Doughty wrote:

Hello Bjoern,

It's still a problem for me.  Here is a list of my system information:

Hostname freenas.local  FreeNAS Build FreeNAS-8.0.4-RELEASE-p1-x64 (11059)
Platform AMD Athlon(tm) II X2 250 Processor  Memory 8144MB  System Time Fri
May 18 09:07:22 2012  Uptime 9:07AM up 6 mins, 0 users  Load Average 0.00,
0.21, 0.16  OS Version FreeBSD 8.2-RELEASE-p6
Are you refering to the OS version? 9.0 or 8.3?  Looks like I'm using 8.2.

Best regards,
Matthew


On 17 May 2012 16:48, Bjoern A. Zeeb  wrote:


On 17. May 2012, at 15:03 , Matthew Doughty wrote:


Dear Jerermy,

Whilst searching for a solution to a problem, I found your post:


http://lists.freebsd.org/pipermail/freebsd-stable/2011-October/064350.html

Please could you explain how I can implement the netwait script to solve
the problem?  I'm new to freenas/BSD but am willing to try working from

the

Cmd line.

ntpd in head 9.0 and later and 8.3 and later should not exhibit that
problem
anymore as it was fixed.   Could you please tell me if that is not the
case?

/bz

--
Bjoern A. Zeeb You have to have visions!
   It does not matter how good you are. It matters what good you do!





___
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: Floppy disks don't work with FreeBSD 9.0

2012-03-27 Thread Dan Daley 


Pretty sure I have a brand new, never used floppy drive laying around 
that I could send to you :)  I don't think I have any discs though.


On 03/27/2012 17:03, Mark Felder wrote:

On Tue, 27 Mar 2012 16:48:26 -0500, Thomas Laus  wrote:



It looks like we both have confirmed that the floppy disk operation 
works up

to FreeBSD 8.3 RC1.  I will need to file a PR for FreeBSD 9.0 in the bug
system.
Thanks for the help.



Could this be related to CAM system issues that shipped with FreeBSD 
9.0 and were fixed in -STABLE? Like the CDROM issues? I'd probably 
test in -STABLE first. Unfortunately I don't have any floppy drives to 
test this with or I'd lend a hand.

___
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"

___
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"