Okay, the user will be the owner of the core file and the errlog shows the users that cause the errors. Find a common denominator and go from there. The errlog can sometimes point you in the right direction or if there is no obvious reason then sit with the user for a while and get them to do their usual tasks and then log off the system. This will usually highlight the cause and a remedy. Oh yeah, be prepared for a "We always just return through that error message" type response somewhere.
FFT2001 wrote: > > It would be helpful to explain how. > > > > > > > > > > -----Original Message----- > From: inquieti <da...@inquieti.com> > To: u2-users <u2-users@listserver.u2ug.org> > Sent: Tue, Mar 29, 2011 1:38 pm > Subject: Re: [U2] Printer Segment Removed? > > > > > You should be able to find something from the common strands to point to > the > > user that is causing the problems. > > > > FFT2001 wrote: > >> > >> I don't believe that it's the user who *sees* the message that is the > >> cause. Rather it's the last user who left the strands dangling. > >> > >> Dubya > > > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users > > ----- "Nobody ever lends money to a man with a sense of humour." -- View this message in context: http://old.nabble.com/Re%3A-Printer-Segment-Removed--tp31240152p31271556.html Sent from the U2 - Users mailing list archive at Nabble.com. _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
