[thedude]

I'm running 3.2 patched and I check my uptime a bit since there's not much else to w/ the box and after about 60 days of uptime, I got a segmentation fault error when I ran uptime and uptime was not displayed.
I rebooted and all is fine now but where should I start looking for errors?

[frisco]

Sounds like a mismatch between kernel and userland, but generally that happens when the kernel you are running is of a different release than the userland you are running (e.g. you are running a 3.3-stable kernel but attempt to run a -current program which requires specific kernel structures, like ps, pfctl or uptime).

Since the problem went away when you rebooted, this backs up that possibility. However, if all you did was patch a 3.2-release then you shouldn't have seen this. Are you sure your src was for 3.2? What does 'uname -a' show?

[thedude]

puffy# uname -a
OpenBSD puffy.my.domain 3.2 GENERIC#25 i386

Pretty disappointing since I was trying to go for some monster uptime :(

[soup4you2]

puffy# uname -a
Pretty disappointing since I was trying to go for some monster uptime :

If uptime is your goal..

[code:1:b7db7a3d64]
/*
* chguptime README
*
* (c) 2002 Pawel Jakub Dawidek <nick@garage.freebsd.pl>
*
* $Id: README,v 1.1.1.1 2002/08/10 23:09:25 jules Exp $
*
*/

This kernel module gives You a new sysctl:

kern.chguptime

With this sysctl You can change uptime on Your machine.
Example:

naomi:root:~# sysctl kern.chguptime=57542369
kern.chguptime: 57542371 -> 57542369
naomi:root:~# uptime
23:11 up 666 days, 0 sec, 1 user, load averages: 0,17 0,11 0,06

Yeees:)
Now You can unload module.
[/code:1:b7db7a3d64]

http://garage.freebsd.pl/chguptime.tgz


i know it's not what you meant but i had to post it anyways.