On Thu, 27 Dec 2001, Tim Bunce wrote:

> On Thu, Dec 27, 2001 at 01:16:40PM -0800, Christopher Solomon wrote:
> > On Thu, 27 Dec 2001, Christopher Solomon wrote:
> >
> > >
> > > My setup:
> > >
> > > linux (2.4.10)
> > > perl 5.6.1 (output of perl -V attached)
> > >
> > > Perl works fine (insofar as I've tested it with a few scripts), and I
> > > originally tried to install DBI from CPAN:
> > >
> > > perl -MCPAN -e shell
> > > shell%> install DBI
> > >
> > > but it didn't take; I can't remember the errors.
> > >
> > > Then I downloaded the source (DBI-1.20.tar.gz) and tried to compile it,
> > > after of course reading the README's and looking at the documentation.
> > >
> > > 'perl Makefile.PL' and 'make' went ok, but 'make test' failed.
> > >
> > > I did a search on the error message: 'Cannot write to /tmp/dbiproxy.pid'
> > > (the first of the errors which caught my eye) but couldn't find anything
> > > helpful.
> > >
> >
> > After re-reading this, I having a sinking feeling it might be something
> > as silly as not having write access to /tmp since I'm not installing DBI
> > as root.
> >
> > Is there a way to specify a different 'tmp' directory? or do you think
> > that's not really the problem?
>
> Having a /tmp directory that's only writable by root is fairly broken
> and probably the root cause. Should look something like:
>
> $ ls -ld /tmp
> drwxrwxrwt  21 root  wheel  1536 Dec 27 22:19 /tmp
>
> Note the final 't'.
>
> Meanwhile, the code says:
>
>     my $tmpDir = $haveFileSpec ? File::Spec->tmpdir() :
>       ($ENV{'TMP'} || $ENV{'TEMP'} || '/tmp');
>

Thanks for the tip Tim (that's alot of 't's :)

Actually just deleting the dbiproxy.pid file that was already in /tmp
solved the problem (kelly did that, since it is his machine).

Is that a bug or a feature? :)

Hope you're having a nice holiday!

Thanks,

Chris

Reply via email to