nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Question on Maximum File Lengths

ckrull

In OpenDeploy 5.6 on Windows 2000. What is the maximum file name length and what is the maximum number of files in a filelist that can be deployed?

Thanks
Chris Krull
Anheuser Busch

Find more posts tagged with

Comments

Adam Stoller

Hi Chris,

Are you asking this for theoretical purposes or are you running into a problem for which you believe one or both of these might be the root cause?

I don't know the "official" answer - but I'd imagine the file name length is limited by the OS (on W2K I think PATH_MAX is 259 characters?) and that number of files in a filelist may be limited my memory/swap space available (i.e. I'm not sure if it's all read into memory of the process, or if it is parsed line-by-line. The latter is probably slower, less efficient in terms of duplicate detection and/or order-processing, but also less prone to memory limitations -- of course there could be yet-another-alternative so ...)

--fish
(Interwoven Senior Technical Consultant)

ckrull

Hmm good question. Right now it is theoretical , but we do have a site in Teamsite that has some directories that are huge and if we must redeploy them they may cause an issue if there is a maximum. I did some research and found this technote not sure if it is applicable TechNote 49981

Chris

Adam Stoller

That technote refers to workflow job/task variable key/value pairs (e.g. foo=bar) - I don't believe your workflows would create a *variable* consisting of a list of all the files ... however if you are planning to submit more than 50 (rough number) files at once - you're better off using Submit Direct for that.

In terms of *deployments* - if you have the ability to do a directory comparison (sourceFilesystem without filelist) deployment - that would be best in cases where yhou need to [re]deploy a significantly large number of files - much less likely to make mistakes (as might happen with a filelist) in terms of forgetting to deploy a file.

Of course - the specific situation you're dealing with may be such that other things need to be taken into consideration - so use the above with the proverbial grain of salt when considering what to do.

You can always run OpenDeploy in simulated mode to see what it would do without it actually doing it...(in case you didn't realize that)

--fish
(Interwoven Senior Technical Consultant)