Hi Mike,
What we need to try is running the same perforce command from a cmd.exe
window as the user running IIS. I suspect this will reveal what the
problem is, perhaps permissions related.
If you like, modify Perforce.pm so that before the open3 call, you have:
print STDERR "\"$Codestriker::p4\"" .
" -p " . $self->{hostname} . ':' . $self->{port} .
" -u " . $self->{user} . " -c " . $self->{client} .
" print -q \"$filename\"" . "#" . "$revision |";
Restart IIS, and try to click on a view full file link again, then check
the IIS log file for the full command. Try pasting that command into a
cmd.exe window as the IIS user, and see if you can figure out if this is a
permissions issue, or perhaps something else.
Cheers,
David
On Tue, 27 Sep 2005 02:54, Nau, Michael wrote:
> I've got Codestriker 1.9.1 up and running - can create new topics,
> update, add comments, etc... But the interaction with Perforce for
> viewing the full files is returning the error below.
> Can't retrieve data using p4: Bad file descriptor at
> C:/tools/codestriker/1.9.1/bin/../lib/Codestriker/Repository/Perforce.pm
> line 33
> Here's my perforce related configuration info from codestriker.conf:
> $p4 = 'c:/program files/perforce';
> 'perforce:codestriker:[EMAIL PROTECTED]:1666'
> There is no password attached to the codestriker user and the
> codestriker_scm has write access to the files in question.
> Any ideas on what might be happening?
> -Mike
--
Cheers,
David
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Codestriker-user mailing list
Codestriker-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/codestriker-user
