We were trying to spool off some jobs, when "Unable to create new process"
was
displayed on the screen. I tried to do a sh, same response, tried to do a
"w" and
the system hung, but Control C worked, tried "su" system hung, again Control
C
worked. I tried to telnet, only to be immediately disconnected (as if
nologins were
active). Then everything was normal.
The only thing I could find in the logs files was that syslogd had just
flipped to the
new day for logs, that is syslog.dated/DATE just rolled over.
Does the world come to a halt for about a minute, while syslogd does it
thing?
This happened before, but at that time, I didn't notice if syslogd had just
flipped to
the new day.
This is a 3.2c system, I know, it's old....but it does what we want.
George Gallen
Senior Programmer/Analyst
Accounting/Data Division
ggallen_at_slackinc.com
ph:856.848.1000 Ext 220
SLACK Incorporated - An innovative information, education and management
company
http://www.slackinc.com
Received on Thu Sep 06 2001 - 18:33:12 NZST