Cron problems update

From: J. Alexander Jacocks (jjacocks@mac.com)
Date: Mon Dec 02 2002 - 15:04:32 EST


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

As cron (and at, as it turns out) still don't work, I again went
through the many emails that I have received (thank you, everybody!)
and got an idea.

Comparing the malfunctioning server to a known-good SunOS 5.9/sun4m
box, I see the following from truss while cron/at is attempting to
process a job:

lstat64("/tmp/croutFAAJ4aOjg", 0xFFBEE7D8) Err#2 ENOENT

This means, if I understand properly, that the above file cannot be
opened for reading/writing. Does anyone have an idea why this might
be? /tmp is 1777, currently.

Thanks!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (Darwin)

iD8DBQE967zUM6BAq5XuDUwRAsqWAKDW2SHYV721K5505gbrezx05pIImgCfZYZJ
WMLBmLS3maT26tldRgYwpyA=
=hwb8
-----END PGP SIGNATURE-----
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:25:24 EDT