[PATCH] misc/18466

2003-02-10 Thread Jeff Jirsa
27;m relatively sure there are other, preferred ways of fixing the issue, and I'd be more than happy to see some feedback. - Jeff Jirsa -- == Jeff Jirsa [EMAIL PROTECTED] HMC 2003 == --- sysinstall.h.orig Sun Feb 9 15:02:25 2003 +++ sysinstall.hMon

Re: what would cause a server to behave this way ?

2002-05-05 Thread Jeff Jirsa
active and the syslog kept logging events until powercycled (oddly enough, the one user was popping often enough that the tcp connection seems to have never completely closed... her logins appear in the logs for 20 minutes after the rest of us were sure the box had completely frozen)... - Jef

Re: bug in pw, freebsd 4.5

2002-05-02 Thread Jeff Jirsa
Feel free to correct me if I'm wrong, but /var/run seems like the more logical answer. Read-only / filesystems would have a hard time creating temp lock files in /etc. If nothing else, make it something that's easily configurable to avoid problems with read only filesystems. - Jeff

logging securelevel violations

2002-03-11 Thread Jeff Jirsa
log(LOG_ERR, "Unable to load module %s: securelevel violation \n", filename); return EPERM; } ... So, my questions are: Why shouldn't it be done? What simple problems am I overlooking? (Would such a contribution have a chance of making it into 5.0?) - Jeff =====