Date: Thu, 18 Jul 2002 09:47:30 +0100 (BST) From: Gavin Atkinson <gavin@ury.york.ac.uk> To: <freebsd-current@freebsd.org> Subject: getting vmemoryuse resource limit: Invalid argument Message-ID: <Pine.BSF.4.33.0207180938150.19954-100000@ury.york.ac.uk>
next in thread | raw e-mail | index | archive | help
Getting this since updating kernel/word to a cvsup a couple of days ago. Jul 18 09:21:24 epsilon login: getting vmemoryuse resource limit: Invalid argument Jul 18 09:22:00 epsilon /usr/sbin/cron[342]: getting vmemoryuse resource limit: Invalid argument Jul 18 09:25:00 epsilon /usr/sbin/cron[355]: getting vmemoryuse resource limit: Invalid argument Jul 18 09:30:00 epsilon /usr/sbin/cron[359]: getting vmemoryuse resource limit: Invalid argument Jul 18 09:33:00 epsilon /usr/sbin/cron[363]: getting vmemoryuse resource limit: Invalid argument Jul 18 09:34:26 epsilon sshd[367]: getting vmemoryuse resource limit: Invalid argument Jul 18 09:33:00 epsilon /usr/sbin/cron[369]: getting vmemoryuse resource limit: Invalid argument Previously working kernel was cvsupped June 23rd. Gavin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.33.0207180938150.19954-100000>