Greetings,
This turned out to be a non-problem. The answer was that 'lockscreen'
and several other long-running jobs were being started using "at", and
/var/spool/cron/queuedefs limited the number of concurrent "at" jobs to
four. Thus the observed behavior was as expected under the
circumstances. I guess I shouldn't have bothered the list with this
one, but I did not realize that these processes were started with "at"
until after I posted the note.
Thanks go to:
"Raj Channa" <raj@admin37.admin.lehman.com>
Kevin.Sheehan@uniq.com.au (Kevin Sheehan {Consulting Poster Child})
Dan Lorenzini Greenwich Capital Markets
dal@gcm.com 600 Steamboat Road
203-625-6088 Greenwich, CT 06830
------------------------------------------------------------------------
Original message:
This is definitely a weird one. A user's "at" jobs don't seem to run
while his (sunview) screen is locked using lockscreen_default. The
machine has two monitors attached to cgsix cards. He is running
sunview on one screen and openwin on the other. The system is a sparc
10 running 4.1.3 with patches 100173-10, 100075-09, 100359-06, 100584-05
and 100726-13 installed.
What is strange is that the jobs stay in the queue after the time they
are supposed to run (that is, they don't get started), but when
lockscreen is killed, they start being run, one every few minutes!
In other respects the system seems normal: load average, swap space,
memory usage, etc. Cron is running and there are no syslog messages.
Other users' "at" jobs run okay. Any help would be appreciated.
Thanks.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:31 CDT