Bob Bailin typed (on Thu, Sep 15, 2005 at 03:53:02AM +0000):
|
| "Jean-Pierre Radley" <jpr@jpr.com> wrote in message
| news:20050914195534.GG15109@jpradley.jpr.com...
| > Walter Vaughan typed (on Wed, Sep 14, 2005 at 01:52:18PM -0400):
| > | Jean-Pierre Radley wrote:
| > |
| > | >OSR 5.0.6.
| > | >A system with hundreds of users and hundreds of printers and
| > | >hundreds of
| > | >printing jobs every day yesterday produced six or seven error
| > | >messages like the following for various printer destinations:
| > | > shell-init: could not get current directory:
| > | > getcwd: cannot access parent >directories: Permission denied
| > |
| > | JP, you've been chasing this down at least since at least the
| > | first week of June. You've never talked about the topology of
| > | the system. Is it a single drive, a raid array, NFS, etc...
| > | something that would cause the filesystem spooling directory
| > | to not be all it could be.
| >
| >
| > I guess I should realize that my gray matter is fading, 'cause I
| > can't recall having posted about this before. :-)
| >
| > IAC, it's a 4-CPU machine under RAID 1. Nearly 10,000 messages have
| > been printed since those errors were seen about 24 hours ago.
|
| Yeah, you're rather prominently featured in a Google search for "could
| not get current directory" getcwd.
|
| The usual reasons given are that some directory permissions were
| changed to disallow reading the parent directory, or that the process
| was started in a directory whose parent had insufficient perms for the
| user. Back in June, you mentioned that fixmog turned up no problems.
|
| Did this just start happening yesterday at this site?

Well, it happened back in June, as you and Walter have noted, and again
two days ago, but thousands of messages have printed normally.

| I suppose rebooting the system is out of the question, but perhaps
| stopping & restarting lpsched might help. I would also edit one of the
| printer interface files to append the pwd & pid to a common logfile,
| and then see if there's a pattern to the failures. Assuming the
| interface script can be started at all when it fails.

Which of the sixty interface scripts should I do that with? The errors
have all been towards different printers, and from different users.

--
JP