Jump to content


The file name is too long


  • Please log in to reply
26 replies to this topic

#1 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 02 March 2010 - 03:26 PM

Originally posted to the perforce-user mailing list by: Ledford, Bruce


I'm trying to delete a directory tree from a branch and get "The file
name is too long" errors for files at the bottom of the tree.  The
absolute pathname for the file is 263 characters.



Am I hitting a Windows pathname limit or a Perforce pathname limit?



What is the pathname limit?



Can shorten the workspace name and get under the limit?


<DIV><FONT size="1">

E-mail confidentiality.
--------------------------------
This e-mail contains confidential and / or privileged information belonging to Spirent Communications plc, its affiliates and / or subsidiaries. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution and / or the taking of any action based upon reliance on the contents of this transmission is strictly forbidden. If you have received this message in error please notify the sender by return e-mail and delete it from your system. If you require assistance, please contact our IT department at helpdesk at spirent.com.

Spirent Communications plc,
Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.
Tel No. +44 (0) 1293 767676
Fax No. +44 (0) 1293 767677

Registered in England Number 470893
Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.

Or if within the US,

Spirent Communications,
26750 Agoura Road, Calabasas, CA, 91302, USA.
Tel No. 1-818-676- 2300

</FONT></DIV>

#2 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 02 March 2010 - 03:55 PM

Originally posted to the perforce-user mailing list by: Ivey, William


It is a Windows limit (260 characters total).

This is why we tell all our users to put the root of
their workspace as close to the root of a drive as
possible. (The default that P4V likes to use is way
too long.) I usually use C:\Depots or C:\P4 in my
Windows workspaces.

Note that this also applies to the temp directory that
p4/p4v use. It defaults to the user's temp directory
and that is too deep. Make it C:\Temp or something
similar.

-Wm



-----Original Message-----
From: perforce-user-bounces at perforce.com [mailto:perforce-user-bounces at perforce.com] On Behalf Of Ledford, Bruce
Sent: Tuesday, March 02, 2010 9:26 AM
To: perforce-user at perforce.com
Subject: [p4] The file name is too long

I'm trying to delete a directory tree from a branch and get "The file
name is too long" errors for files at the bottom of the tree.  The
absolute pathname for the file is 263 characters.



Am I hitting a Windows pathname limit or a Perforce pathname limit?



What is the pathname limit?



Can shorten the workspace name and get under the limit?


<DIV><FONT size="1">

E-mail confidentiality.
--------------------------------
This e-mail contains confidential and / or privileged information belonging to Spirent Communications plc, its affiliates and / or subsidiaries. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution and / or the taking of any action based upon reliance on the contents of this transmission is strictly forbidden. If you have received this message in error please notify the sender by return e-mail and delete it from your system. If you require assistance, please contact our IT department at helpdesk at spirent.com.

Spirent Communications plc,
Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.
Tel No. +44 (0) 1293 767676
Fax No. +44 (0) 1293 767677

Registered in England Number 470893
Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.

Or if within the US,

Spirent Communications,
26750 Agoura Road, Calabasas, CA, 91302, USA.
Tel No. 1-818-676- 2300

</FONT></DIV>
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perf...o/perforce-user

#3 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 02 March 2010 - 04:16 PM

Originally posted to the perforce-user mailing list by: =?iso-8859-1?Q?Kjell=E9n_Lennart?=


It is a Windows pathname limit and you can reduce the absolute pathname length in either of two ways in Perforce (and of course by changing your filenames or directory structure)

- Shorenting the workspace root. (The workspace name itself does not shorten the pathname length, but if you include the workspace name in the workspace root it does)
- Changing the workspace view to create mapping between depot and workspace that gives you a shorter pathname length.

                  / Lennart Kjell?n, Configuratuion Manager


-----Original Message-----
From: perforce-user-bounces at perforce.com [mailto:perforce-user-bounces at perforce.com] On Behalf Of Ledford, Bruce
Sent: den 2 mars 2010 16:26
To: perforce-user at perforce.com
Subject: [p4] The file name is too long


I'm trying to delete a directory tree from a branch and get "The file name is too long" errors for files at the bottom of the tree.  The absolute pathname for the file is 263 characters.



Am I hitting a Windows pathname limit or a Perforce pathname limit?



What is the pathname limit?



Can shorten the workspace name and get under the limit?


<DIV><FONT size="1">

E-mail confidentiality.
--------------------------------
This e-mail contains confidential and / or privileged information belonging to Spirent Communications plc, its affiliates and / or subsidiaries. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution and / or the taking of any action based upon reliance on the contents of this transmission is strictly forbidden. If you have received this message in error please notify the sender by return e-mail and delete it from your system. If you require assistance, please contact our IT department at helpdesk at spirent.com.

Spirent Communications plc,
Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom. Tel No. +44 (0) 1293 767676 Fax No. +44 (0) 1293 767677

Registered in England Number 470893
Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.

Or if within the US,

Spirent Communications,
26750 Agoura Road, Calabasas, CA, 91302, USA.
Tel No. 1-818-676- 2300

</FONT></DIV>
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com http://maillist.perf...o/perforce-user

#4 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 02 March 2010 - 04:21 PM

Originally posted to the perforce-user mailing list by: Vasisht, Jayanth S


Its probably the Windows path limit, about 255 chars I think.

Try using the "subst" Windows command to try shorten the path & try if the delete works.

Regards,
Jayanth
~~~~~

-----Original Message-----
From: perforce-user-bounces at perforce.com [mailto:perforce-user-bounces at perforce.com] On Behalf Of Ledford, Bruce
Sent: Tuesday, March 02, 2010 20:56
To: perforce-user at perforce.com
Subject: [p4] The file name is too long

I'm trying to delete a directory tree from a branch and get "The file
name is too long" errors for files at the bottom of the tree.  The
absolute pathname for the file is 263 characters.



Am I hitting a Windows pathname limit or a Perforce pathname limit?



What is the pathname limit?



Can shorten the workspace name and get under the limit?


<DIV><FONT size="1">

E-mail confidentiality.
--------------------------------
This e-mail contains confidential and / or privileged information belonging to Spirent Communications plc, its affiliates and / or subsidiaries. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution and / or the taking of any action based upon reliance on the contents of this transmission is strictly forbidden. If you have received this message in error please notify the sender by return e-mail and delete it from your system. If you require assistance, please contact our IT department at helpdesk at spirent.com.

Spirent Communications plc,
Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.
Tel No. +44 (0) 1293 767676
Fax No. +44 (0) 1293 767677

Registered in England Number 470893
Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.

Or if within the US,

Spirent Communications,
26750 Agoura Road, Calabasas, CA, 91302, USA.
Tel No. 1-818-676- 2300

</FONT></DIV>
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perf...o/perforce-user

#5 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 02 March 2010 - 04:54 PM

Originally posted to the perforce-user mailing list by: Gabor Maghera


As William has previously mentioned, this is an issue with the 260 character
limit imposed for paths by the Windows API.

If you can afford it, think about switching to a POSIX file system (like the
Mac OS).  I was surprised to see many Perforce employees and attendees using
Macs at the last user conference (and I hear Macs are Google's tool of
choice, too).  Speaking of which, is there any hope of some sort of Finder
integration (as P4V does with Windows explorer)?  Perhaps it's next in line
after the streams implementation (wishful thinking? maybe...).  Making the
?ber Windows installer behave more like the Mac OS one would also be a good
idea.  I can already hear the P4Win fanatics crying :-), although that was
my GUI tool of choice for some time as well - perforce!

--
Gabor

On Tue, Mar 2, 2010 at 7:55 AM, Ivey, William <william_ivey at bmc.com> wrote:

Quote

It is a Windows limit (260 characters total).

This is why we tell all our users to put the root of
their workspace as close to the root of a drive as
possible. (The default that P4V likes to use is way
too long.) I usually use C:\Depots or C:\P4 in my
Windows workspaces.

Note that this also applies to the temp directory that
p4/p4v use. It defaults to the user's temp directory
and that is too deep. Make it C:\Temp or something
similar.

-Wm



-----Original Message-----
From: perforce-user-bounces at perforce.com [mailto:
perforce-user-bounces at perforce.com] On Behalf Of Ledford, Bruce
Sent: Tuesday, March 02, 2010 9:26 AM
To: perforce-user at perforce.com
Subject: [p4] The file name is too long

I'm trying to delete a directory tree from a branch and get "The file
name is too long" errors for files at the bottom of the tree.  The
absolute pathname for the file is 263 characters.



Am I hitting a Windows pathname limit or a Perforce pathname limit?



What is the pathname limit?



Can shorten the workspace name and get under the limit?


<DIV><FONT size="1">

E-mail confidentiality.
--------------------------------
This e-mail contains confidential and / or privileged information belonging
to Spirent Communications plc, its affiliates and / or subsidiaries. If you
are not the intended recipient, you are hereby notified that any disclosure,
copying, distribution and / or the taking of any action based upon reliance
on the contents of this transmission is strictly forbidden. If you have
received this message in error please notify the sender by return e-mail and
delete it from your system. If you require assistance, please contact our IT
department at helpdesk at spirent.com.

Spirent Communications plc,
Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United
Kingdom.
Tel No. +44 (0) 1293 767676
Fax No. +44 (0) 1293 767677

Registered in England Number 470893
Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN,
United Kingdom.

Or if within the US,

Spirent Communications,
26750 Agoura Road, Calabasas, CA, 91302, USA.
Tel No. 1-818-676- 2300

</FONT></DIV>
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perf...o/perforce-user

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perf...o/perforce-user



#6 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 02 March 2010 - 05:01 PM

Originally posted to the perforce-user mailing list by: Gabor Maghera


I mean to include this kb article link in my previous message (nothing new,
just Perforce's official wording of the issue, as well as some additional
workarounds):
http://kb.perforce.c...long-path-names

Sorry about spamming.

Gabor

2010/3/2 Kjell?n Lennart <Lennart.Kjellen at scania.com>

Quote

It is a Windows pathname limit and you can reduce the absolute pathname
length in either of two ways in Perforce (and of course by changing your
filenames or directory structure)

- Shorenting the workspace root. (The workspace name itself does not
shorten the pathname length, but if you include the workspace name in the
workspace root it does)
- Changing the workspace view to create mapping between depot and
workspace that gives you a shorter pathname length.

                 / Lennart Kjell?n, Configuratuion Manager


-----Original Message-----
From: perforce-user-bounces at perforce.com [mailto:
perforce-user-bounces at perforce.com] On Behalf Of Ledford, Bruce
Sent: den 2 mars 2010 16:26
To: perforce-user at perforce.com
Subject: [p4] The file name is too long


I'm trying to delete a directory tree from a branch and get "The file name
is too long" errors for files at the bottom of the tree.  The absolute
pathname for the file is 263 characters.



Am I hitting a Windows pathname limit or a Perforce pathname limit?



What is the pathname limit?



Can shorten the workspace name and get under the limit?


<DIV><FONT size="1">

E-mail confidentiality.
--------------------------------
This e-mail contains confidential and / or privileged information belonging
to Spirent Communications plc, its affiliates and / or subsidiaries. If you
are not the intended recipient, you are hereby notified that any disclosure,
copying, distribution and / or the taking of any action based upon reliance
on the contents of this transmission is strictly forbidden. If you have
received this message in error please notify the sender by return e-mail and
delete it from your system. If you require assistance, please contact our IT
department at helpdesk at spirent.com.

Spirent Communications plc,
Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United
Kingdom. Tel No. +44 (0) 1293 767676 Fax No. +44 (0) 1293 767677

Registered in England Number 470893
Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN,
United Kingdom.

Or if within the US,

Spirent Communications,
26750 Agoura Road, Calabasas, CA, 91302, USA.
Tel No. 1-818-676- 2300

</FONT></DIV>
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perf...o/perforce-user

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perf...o/perforce-user



#7 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 02 March 2010 - 05:38 PM

Originally posted to the perforce-user mailing list by: Tim McDaniel


Ledford, Bruce wrote

Quote

I'm trying to delete a directory tree from a branch and get "The
file name is too long" errors for files at the bottom of the tree.
The absolute pathname for the file is 263 characters.

Am I hitting a Windows pathname limit or a Perforce pathname limit?

Windows.

Aside from techniques mentioned by other people, I've used the subst
command (%SystemRoot%\system32\subst.exe on Windows XP).  It's sort of
creating a drive letter as a transient symlink.

     subst /?
gives you a usage message.  <http://ss64.com/nt/subst.html> has some
more info, though aimed more at net usage.

It lets you associate a drive letter with a path on the current
machine, as in

     subst m: c:\this\is\a\very\long\path\that\would\otherwise\get\me\in\trouble

Then all references to m: point to that c:\stuff, though you could
still use the long path if you like.  subst is not persistent across
reboots.

--
Tim McDaniel, tmcd at panix.com

#8 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 02 March 2010 - 07:24 PM

Originally posted to the perforce-user mailing list by: Bennett, Patrick




Quote

-----Original Message-----
From: perforce-user-bounces at perforce.com [mailto:perforce-user-
bounces at perforce.com] On Behalf Of Tim McDaniel
Sent: Tuesday, March 02, 2010 12:38 PM
To: perforce-user at perforce.com
Subject: Re: [p4] The file name is too long

Ledford, Bruce wrote

Quote

I'm trying to delete a directory tree from a branch and get "The
file name is too long" errors for files at the bottom of the tree.
The absolute pathname for the file is 263 characters.

Am I hitting a Windows pathname limit or a Perforce pathname limit?

Windows.

[Bennett, Patrick] No, this isn't true.  Windows definitely supports longer paths [otherwise he wouldn't have been able to create that path in the first place, no??] - this is Perforce's problem.
Code just has to go a little out of its way to support it.  Windows apis taking file paths by default are limited to MAX_PATH (260 chars).
They support paths up to 32,767 characters if the Unicode APis are called and the path is prefixed with \\?\
Perforce just isn't doing this.

Patrifk

#9 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 02 March 2010 - 08:07 PM

Originally posted to the perforce-user mailing list by: Tim McDaniel


On Tue, 2 Mar 2010, Bennett, Patrick <Patrick.Bennett at inin.com> wrote:

Quote

[Bennett, Patrick] No, this isn't true.  Windows definitely supports
longer paths [otherwise he wouldn't have been able to create that
path in the first place, no??]
Code just has to go a little out of its way to support it.  Windows
apis taking file paths by default are limited to MAX_PATH (260
chars).

Since the NUL terminator has to be included, the file path itself must
be no longer than 259, and there are further restrictions.

Quote

They support paths up to 32,767 characters if the Unicode APis are
called and the path is prefixed with \\?\
Perforce just isn't doing this.

a LOT of Windows utilities don't support long paths.  Specifically,
Windows Explorer and CMD don't, according to fora hits I've seen.
So depending on what Perforce is calling, it might not be Perforce's
fault per se.

--
Tim McDaniel, tmcd at panix.com

#10 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 02 March 2010 - 08:48 PM

Originally posted to the perforce-user mailing list by: Ivey, William


Windows only partly supports it. You'll find yourself locked
out of a lot of tools if you try to create longer paths,
therefore what the OS technically supports and what it
realistically or practically supports only overlap, they are
not identical.

And, yes, it is possible to create paths that are too long,
even when the source machine is Windows. That's because each
client has its own path prefix (root) - and, of course, you
can go the extra mile of using weird view or filesystem
mappings. My <260 character path can easily be >260 on
another system.

And, of course, they can easily be created on non-Windows
systems.

It's all made more likely with the current trend toward
long, often redundant, paths in languages such as Java as
well as the trend for developers to ignore the reality of
the filesystem they are using. (I have seen the same
directory name appear three times in one path, not to
mention assorted version information and even dates - two
different dates in one path in a recent case.)

-Wm

-----Original Message-----
From: perforce-user-bounces at perforce.com [mailto:perforce-user-bounces at perforce.com] On Behalf Of Bennett, Patrick
Sent: Tuesday, March 02, 2010 1:24 PM

[Bennett, Patrick] No, this isn't true.  Windows definitely supports longer paths [otherwise he wouldn't have been able to create that path in the first place, no??] - this is Perforce's problem.
Code just has to go a little out of its way to support it.  Windows apis taking file paths by default are limited to MAX_PATH (260 chars).
They support paths up to 32,767 characters if the Unicode APis are called and the path is prefixed with \\?\
Perforce just isn't doing this.

Patrifk

#11 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 02 March 2010 - 10:09 PM

Originally posted to the perforce-user mailing list by: Bennett, Patrick


If a program belches on a path longer than MAX_PATH characters in Windows it's entirely within that programs control to fix the problem.
It most assuredly is not a problem with Windows itself (other than the issues of them not being able to change MAX_PATH without breaking tons of old code that has hardcoded 256-length buffers) since NTFS was first introduced.  Now, if you want to say tons of software is broken in dealing with long filenames, including Perforce, then yes, absolutely true.
Other than that, Windows APIs and NTFS definitely support file paths longer than 259 chars.

So in the case of Perforce commands being unable to sync or remove files that have paths longer than 259 characters, this is absolutely without question something that is Perforce's problem to fix, not Windows.  The APIs are all there for them to use.

Patrick

Quote

-----Original Message-----
From: perforce-user-bounces at perforce.com [mailto:perforce-user-
bounces at perforce.com] On Behalf Of Tim McDaniel
Sent: Tuesday, March 02, 2010 3:08 PM
Cc: 'perforce-user at perforce.com'
Subject: Re: [p4] The file name is too long

On Tue, 2 Mar 2010, Bennett, Patrick <Patrick.Bennett at inin.com> wrote:

Quote

[Bennett, Patrick] No, this isn't true.  Windows definitely supports
longer paths [otherwise he wouldn't have been able to create that
path in the first place, no??]
Code just has to go a little out of its way to support it.  Windows
apis taking file paths by default are limited to MAX_PATH (260
chars).

Since the NUL terminator has to be included, the file path itself must
be no longer than 259, and there are further restrictions.

Quote

They support paths up to 32,767 characters if the Unicode APis are
called and the path is prefixed with \\?\
Perforce just isn't doing this.

a LOT of Windows utilities don't support long paths.  Specifically,
Windows Explorer and CMD don't, according to fora hits I've seen.
So depending on what Perforce is calling, it might not be Perforce's
fault per se.


#12 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 02 March 2010 - 10:47 PM

Originally posted to the perforce-user mailing list by: Tim McDaniel


On Tue, 2 Mar 2010, Bennett, Patrick <Patrick.Bennett at inin.com> wrote:

Quote

If a program belches on a path longer than MAX_PATH characters in
Windows it's entirely within that programs control to fix the
problem.

I don't know what Perforce is doing in the current case to know
whether it's Perforce's own client code, or whether it's using
something else, so I can only talk in generalities.

If a program is doing its work using tools or APIs that are not under
its control, then (depending on the tools / APIs) it can be
impractical for the program to be changed to fix it.  In the limit,
they might have to abandon the tool/API and re-implement it from
scratch.  For example, in our build, I had to re-implement del and cp
to deal with long paths with the other conditions that I wanted, and
it took a Cygwin shell script and 150 and 300 lines of bash
(respectively) to do it reliably.

Or it might be impossible to re-implement: I've heard that there are
some machine-dependent things that they refuse to put into the Java
specification, though I don't know what they might be.  I hate trying
to implement things in Ant.

--
Tim McDaniel, tmcd at panix.com

#13 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 02 March 2010 - 11:32 PM

Originally posted to the perforce-user mailing list by: David Weintraub


On Tue, Mar 2, 2010 at 2:24 PM, Bennett, Patrick
<Patrick.Bennett at inin.com> wrote:

Quote

[Bennett, Patrick] No, this isn't true. ?Windows definitely supports longer paths [otherwise
he wouldn't have been able to create that path in the first place, no??] - this is Perforce's problem.
Code just has to go a little out of its way to support it.

Quote

Windows apis taking file paths by
default are limited to MAX_PATH (260 chars).
They support paths up to 32,767 characters if the Unicode APis are called and the path is
prefixed with \\?\
Perforce just isn't doing this.

First of all. the NTFS supports 32K length path names, and not
necessarily the Windows APIs. In fact, *MOST* Windows API cannot
support anything longer than MAX_PATH.

You can even see that Microsoft itself doesn't support file names
longer than 259 characters with their own utilities. Windows Explorer
can't support more than 260 characters even with the \\?\ syntax.
Windows Command Console certainly can't. Windows Office can't. Even
Visual Studio can't.

So, you can see that if this is a Perforce issue, they're not doing
anything more than Microsoft is doing.

And, it is very easy for this to happen too.

Imagine I create a Peforce client, and I put C:/perforce as my workspace root.

Now, my friend John Q. Public decided to take the default workspace
directory, and then in a fit of organization, he created a "Perforce
Workspaces" directory under it because he thought he might have
multiple workspaces.

The root directory of his workspace is:

C:/Documents and Settings/James Q. Public/My Documents/Perforce
Workspaces/Workspace Number 1

Which makes the root of his workspace 94 characters long.

I am working on a Java project using Maven, so using the default
structure, I have a file:

main-proj/sub-proj/src/main/java/com/solbright/adserver/comm/remote/commInterfaceFile.java

That's 91 characters long. it's in my workspace, so the total path
length is 103 characters which Windows can easily handle. However, my
friend tries to checkout my file, but he has 94 characters in his
workspace's name. That's 185 characters long, so Windows will give him
an error.

Try to use the subst command, move your workspace to another directory
closer to the root of the drive, or try using Perforce's ability to
rename directories in your checkout to keep the name shorter.

--
David Weintraub
qazwart at gmail.com

#14 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 08 March 2010 - 05:36 PM

Originally posted to the perforce-user mailing list by: Ledford, Bruce


Thanks for all the input.  I explored a few of the alternatives with varying degrees of success; but in the end, I jumped over to a Linux box. :)

-----Original Message-----
From: perforce-user-bounces at perforce.com [mailto:perforce-user-bounces at perforce.com] On Behalf Of David Weintraub
Sent: Tuesday, March 02, 2010 6:32 PM
To: Bennett, Patrick
Cc: perforce-user at perforce.com
Subject: Re: [p4] The file name is too long

On Tue, Mar 2, 2010 at 2:24 PM, Bennett, Patrick
<Patrick.Bennett at inin.com> wrote:

Quote

[Bennett, Patrick] No, this isn't true. ?Windows definitely supports longer paths [otherwise
he wouldn't have been able to create that path in the first place, no??] - this is Perforce's problem.
Code just has to go a little out of its way to support it.

Quote

Windows apis taking file paths by
default are limited to MAX_PATH (260 chars).
They support paths up to 32,767 characters if the Unicode APis are called and the path is
prefixed with \\?\
Perforce just isn't doing this.

First of all. the NTFS supports 32K length path names, and not
necessarily the Windows APIs. In fact, *MOST* Windows API cannot
support anything longer than MAX_PATH.

You can even see that Microsoft itself doesn't support file names
longer than 259 characters with their own utilities. Windows Explorer
can't support more than 260 characters even with the \\?\ syntax.
Windows Command Console certainly can't. Windows Office can't. Even
Visual Studio can't.

So, you can see that if this is a Perforce issue, they're not doing
anything more than Microsoft is doing.

And, it is very easy for this to happen too.

Imagine I create a Peforce client, and I put C:/perforce as my workspace root.

Now, my friend John Q. Public decided to take the default workspace
directory, and then in a fit of organization, he created a "Perforce
Workspaces" directory under it because he thought he might have
multiple workspaces.

The root directory of his workspace is:

C:/Documents and Settings/James Q. Public/My Documents/Perforce
Workspaces/Workspace Number 1

Which makes the root of his workspace 94 characters long.

I am working on a Java project using Maven, so using the default
structure, I have a file:

main-proj/sub-proj/src/main/java/com/solbright/adserver/comm/remote/commInterfaceFile.java

That's 91 characters long. it's in my workspace, so the total path
length is 103 characters which Windows can easily handle. However, my
friend tries to checkout my file, but he has 94 characters in his
workspace's name. That's 185 characters long, so Windows will give him
an error.

Try to use the subst command, move your workspace to another directory
closer to the root of the drive, or try using Perforce's ability to
rename directories in your checkout to keep the name shorter.

--
David Weintraub
qazwart at gmail.com

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perf...o/perforce-user

<DIV><FONT size="1">

E-mail confidentiality.
--------------------------------
This e-mail contains confidential and / or privileged information belonging to Spirent Communications plc, its affiliates and / or subsidiaries. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution and / or the taking of any action based upon reliance on the contents of this transmission is strictly forbidden. If you have received this message in error please notify the sender by return e-mail and delete it from your system. If you require assistance, please contact our IT department at helpdesk at spirent.com.

Spirent Communications plc
Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.
Tel No. +44 (0) 1293 767676
Fax No. +44 (0) 1293 767677

Registered in England Number 470893
Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.

Or if within the US,

Spirent Communications,
26750 Agoura Road, Calabasas, CA, 91302, USA.
Tel No. 1-818-676- 2300

</FONT></DIV>

#15 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 11 March 2010 - 04:44 AM

Originally posted to the perforce-user mailing list by: H, Prashant


Hi,

How can I stop and restart my client process in perforce ?

Thanks in Advance,
Prashant H

#16 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 11 March 2010 - 05:56 AM

Originally posted to the perforce-user mailing list by: saurabh talwar


Hi Prashant

Can you explain it a little further since once you create a client spec you
can either change ir or make a new client spec ?

Regards.
Sunny

On Wed, Mar 10, 2010 at 8:44 PM, H, Prashant <Prashant.H at netapp.com> wrote:

Quote

Hi,

How can I stop and restart my client process in perforce ?

Thanks in Advance,
Prashant H

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perf...o/perforce-user



#17 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 11 March 2010 - 06:57 AM

Originally posted to the perforce-user mailing list by: H, Prashant


Hi Saurabh,



                     Basically  the server admin wants me to stop the p4
client process as many such processes from multiple users will load the
server.

I am a perforce user and I believe in clearcase we had features like
cleartool startview etc. to start the view server process,  so Do we

Have such facilities in perforce as well ?



Thanks,

Prashant H



From: saurabh talwar [mailto:talwar.saurabh at gmail.com]
Sent: Thursday, March 11, 2010 11:26 AM
To: H, Prashant
Cc: perforce-user at perforce.com
Subject: Re: [p4] perforce client process



Hi Prashant



Can you explain it a little further since once you create a client spec
you can either change ir or make a new client spec ?



Regards.

Sunny

On Wed, Mar 10, 2010 at 8:44 PM, H, Prashant <Prashant.H at netapp.com>
wrote:

Hi,

How can I stop and restart my client process in perforce ?

Thanks in Advance,
Prashant H

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perf...o/perforce-user

#18 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 11 March 2010 - 07:18 AM

Originally posted to the perforce-user mailing list by: M K


If it is hung, hit ctrl-C. Otherwise, I'm not sure I understand what you
mean. If you are not running a p4 command, you have no p4 client processses
running.


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of H, Prashant
Sent: Wednesday, March 10, 2010 8:45 PM
To: perforce-user at perforce.com
Subject: [p4] perforce client process


Hi,

How can I stop and restart my client process in perforce ?

Thanks in Advance,
Prashant H

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perf...o/perforce-user

#19 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 11 March 2010 - 09:31 AM

Originally posted to the perforce-user mailing list by: Robert Cowham


Hi Prashant

You need to be clear as to which client process you require "stopping". Are
you using P4V?

I wonder if you are referring to the fact that P4V by default is set up to
poll the server regularly (typically every 5 minutes) for latest updates.

If you have lots of users doing this it starts to place a load on the
server.

It is easy to turn off, put 0 in the appropriate field: Edit > Preferences >
Connection > "Check Server for updates"

It is also possible to create an auto-config to do this as part of the
installer. Can give you a pointer if that is relevant.

Robert

Quote

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of H, Prashant
Sent: 11 March 2010 04:45
To: perforce-user at perforce.com
Subject: [p4] perforce client process

Hi,

How can I stop and restart my client process in perforce ?

Thanks in Advance,
Prashant H

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perf...o/perforce-user


#20 Mailman Sync

Mailman Sync

    Advanced Member

  • Maillist Aggregator
  • 2256 posts

Posted 11 March 2010 - 06:14 PM

Originally posted to the perforce-user mailing list by: Matt Janulewicz


I'd also like to add that if your user processes are greatly affecting
the performance of the server, it's time to spend some money on hardware.

As others have indicated, connections to the server (or client
processes) are established at the onset of a command and terminated when
it's done. Perforce client apps do not hold connections open. So it
would have to be a pretty unique situation where many users were doing
many 'heavy' queries at the same time for people to notice.

Or, perhaps, you have 100 people pointed at a 386 or virtual machine
that has no resources to begin with.


-Matt Janulewicz
Lucasfilm Entertainment Company Ltd.


On 03/11/2010 01:31 AM, Robert Cowham wrote:

Quote

Hi Prashant

You need to be clear as to which client process you require "stopping". Are
you using P4V?

I wonder if you are referring to the fact that P4V by default is set up to
poll the server regularly (typically every 5 minutes) for latest updates.

If you have lots of users doing this it starts to place a load on the
server.

It is easy to turn off, put 0 in the appropriate field: Edit>  Preferences>
Connection>  "Check Server for updates"

It is also possible to create an auto-config to do this as part of the
installer. Can give you a pointer if that is relevant.

Robert

  

Quote

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of H, Prashant
Sent: 11 March 2010 04:45
To: perforce-user at perforce.com
Subject: [p4] perforce client process

Hi,

How can I stop and restart my client process in perforce ?

Thanks in Advance,
Prashant H

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perf...o/perforce-user
    
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perf...o/perforce-user
  





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users