Your uptime can be as long as your machine has physical power (providing you have no errant kernel extensions or something else that causes a kernel panic). Simply learn the power of
SystemStarter
You can leave the kernel and core operating system running and just restart the various StartupItems material [the scripts in
/System/Library/StartupItems and
/Library/StartupItems] without actually restarting the Darwin OS itself.
This from the man page:
Code:
DESCRIPTION
The SystemStarter utility may be used to start, stop, and restart the
system services which are described in the /Library/StartupItems/ and
/System/Library/StartupItems/ paths.
The optional action argument specifies which action SystemStarter per-
forms on the startup items. The optional service argument specifies
which startup items to perform the action on. If no service is speci-
fied, all startup items will be acted on; otherwise, only the item pro-
viding the service, any items it requires, or any items that depend on it
will be acted on.
During boot SystemStarter is invoked by rc (see rc(8)) and is responsible
for starting all startup items in an order that satisfies each item's
requirements.
For example, to restart a specific daemon such as NetInfo:
sudo SystemStarter restart NetInfo
Or issue a blanket command that restarts all of the core services*:
sudo SystemStarter restart
In many cases, this will be as effective as a reboot (since this is what
rc invokes anyway).
*One caveat is that all the start, stop, and restart options do is pass the prescribed argument to the various startup scripts. If the syntax issued is incorrect for that daemon, nothing happens. An example is AppServices, which controls coreservicesd. Sending stop or restart to this script has no effect.