[baliset]

I was hoping that there might be a way under Leopard now to do this. If there isn’t a direct way, perhaps there is a GUI utility to assist making the manual changes to the routing tables to enable a computer connected to (say) home broadband via Airport, and then logs in to a VPN server, and then enables internet connection sharing through to the ethernet socket, so that it’s the VPN connection that’s being shared rather than just the “regular” internet connection.

Can anyone help?

[baliset]

Yep. Permissions verified and Disk integrity checked.

[baliset]

I doubt the imported accounts are to blame- we upgraded to Leopard server at Christmas and have had a generally good run. This problem has manifested more recently. Has there been a security patch in the last month or so? If so, we tend to apply it without delay.

[baliset]

It’s worth mentioning that there is a specific pattern to the crashes that these errors seem to be causing. The console is especially full of these messages at times that launchd is attempting to run the daily housekeeping scripts the OS does at certain intervals. If you use Lingon (a launchd GUI) to peruse the list of tasks the OS runs you will see certain ones the OS performs “every 24 hours”. I got to wondering when those “every 24 hour” entries were actually running. Our crashes seemed to be happening between midnight and dawn. I used a shareware tool called “Onyx” which lets you manually trigger those housekeeping scripts that the OS would otherwise do itself daily, weekly or monthly (I’m presuming these are things like log rollovers, cache cleanups, etc). I ran Onyx at a certain time one afternoon. Since then, the server has frozen at exactly that time of day, and has sailed though the nights OK. I’m wondering if the “24 hour” counter was reset and these scripts are being triggered at a different time of day now. I’ll need to check if the console errors of the type we’ve been discussing are now peaking at the new time (as they are appearing at all times through the day but especially at the times I’ve mentioned) and post again.

[baliset]

Our 10.5 installation was a clean install with user/group/computer lists imported from an export performed on the server’s 10.4 predecessor.

[baliset]

I also get this and it is crippling us. Various entries in the console logs list processes (“master”, “freshclam”, “ditto”) with “no account to back it” and our server freezes, normally overnight.

[Author]

Posts