> Guessing (WAG mode): Could this memory growth be caused by maintaining > symlink context? > > It strikes me that if there are a lot of symlinks that there'd need to be > kept a list of where they're pointing so that it could ensure resolution. > > Since I've *NO* knowledge of the internals of TSM (I have enough problems > getting time to understand the externals) the above is a WAG.
It's a good thought, but typically these sorts of programs just keep a history of directory device/inode number pairs to identify some kind of symlink recursion. Those two numbers are enough to uniquely identify any file/directory on a system. That, and there aren't any symlinks on that mountpoint, but nothing is there to stop dsmc from keeping track of it anyway... Thanks for thinking about it. ~ Daniel ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
