[p4] depot symlink syncs to linux directory as the file it pointsat instead of a symlink

Jeff Grills jgrills at junctionpoint.com
Tue Oct 18 09:20:04 PDT 2005


Days?  Perforce support usually gets back to me in hours.  That's pretty
odd.
 
I do run a 2005.1 server at home.  I'll see if I can try out symlink support
on it soon, but I'm a bit busy right at the moment.
 
j

  _____  

From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Roger Girard
Sent: Tuesday, October 18, 2005 8:19 AM
To: Stephen Vance; perforce-user at perforce.com
Subject: RE: [p4] depot symlink syncs to linux directory as the file it
pointsat instead of a symlink



Yes, I get the same results with P4 and P4V.

            

Perforce support has been contacted. The lack of a timely response from them
prompted me to see if the user group had run across such an event.

As far as evaluating support along with the product I must say I've been
pleased to this point.

BUT, I support a start-up environment; which means that I look
non-responsive for several days while waiting for feedback from support.

Simply put, I am not a happy camper:-(.

Thanks Steve!

-Roger

  _____  

From: Stephen Vance [mailto:steve at vance.com] 
Sent: Tuesday, October 18, 2005 7:46 AM
To: Roger Girard; perforce-user at perforce.com
Subject: Re: [p4] depot symlink syncs to linux directory as the file it
points at instead of a symlink

Sounds like something to take up with Support. It would be a good way to
evaluate their performance, as well.

Have you tried the same operations using only the command line to see if the
results are different?

Steve

At 11:24 AM 10/17/2005, Roger Girard wrote:



Content-Class: urn:content-classes:message
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative;
         boundary="----_=_NextPart_001_01C5D32E.D0C03510"

Folks,
 
I am evaluating the release 2005.1 for my team. It is my 1st time working
with Perforce.
 
I am seeing some of the symlinks in the depot loaded onto my hard drive in
the workspace as the file the link points at instead of the actual symlinks.
 
The depot knows the element is a symlink when I look in the P4V GUI or run
"p4 fstat".
The P4V GUI reports the symlinks as symlinks in the workspace but the linux
command line usage of "ls -al" and "file" show the elements not to be
symbolic links.
 
I am able to remove the elements in the workspace then re"sync" and they are
now symlinks.
If I remove the entire workspace directory structure from the top level
directory then re"sync" the elements are back to being the file pointed at
instead of the symlink.
 
Has anyone seen this type of behavior using a Linux server/client and the
latest release 2005.1 or earlier?
 
Thanks greatly,
-Roger
 
 

  _____  

This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you. 
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user 

Stephen Vance
mailto:steve at vance.com
http://www.vance.com/


  _____  

This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://maillist.perforce.com/pipermail/perforce-user/attachments/20051018/77c51dba/attachment-0006.html>


More information about the perforce-user mailing list