| All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
| Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
Broken symbolic links
|
Logged in as: Guest |
| Users viewing this topic: none |
|
Login  |
|
|
 Broken symbolic links - Apr. 16, '04, 9:00:52 AM
|
|
|
zuecks
Posts: 2
Joined: Apr. 13, '04,
Status: offline
|
Hi People,
I have a question about nfs-connection SFU to Unix. Perhaps
someone can help?
In our Unix Environment, we have
user-directions /usr/people/usernames and using a
script, that mount several nfs-drives.
The mounts works allright.
At the unix -directories exists symbolic- links to several other directories and nfs-drives.
But I don't see the links (in SFU). I think SFU can't resolve symbolic-links in this case.
Only a example,If I check C:\programme\SFU\bin\file linkname , I get a report
"broken symbolic link.
What do I wrong.
Frank
|
|
|
|
|
RE: Broken symbolic links - Apr. 16, '04, 11:13:37 AM
|
|
|
Rodney
Posts: 3714
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
Just to make sure we understand your setup:
You have SFU 3.5 installed and are using NFS client.
What is the content of the symbolic link?
Is it an absolute or relative symbolic link?
I suspect from the message that it is an absolute path in the symbolic
link which of course cannot be resolved. But tell us what it is exactly
then we can work from there.
|
|
|
|
|
RE: Broken symbolic links - Apr. 20, '04, 5:56:50 AM
|
|
|
zuecks
Posts: 2
Joined: Apr. 13, '04,
Status: offline
|
Hi Rodney,
Thank you for your help.
Its right, I use a NFS-client. We have user -directories /usr/people/username/data(the link)
Under username are subdirectories “data” (it’s the symbolic link of the data directories)
Example: ln –s (dest) /comp/datacomp/data1 (linkname) data.
This is only a example from existing much more symbolic links to mounted drives.
But I notice, you wrote absolute path cannot be resolved and that’s is already a answer of my Question. Maybe you have a suggestion for a other solution? I think its difficult.
Frank
|
|
|
|
|
RE: Broken symbolic links - Apr. 20, '04, 11:27:11 AM
|
|
|
Rodney
Posts: 3714
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
You won't be able to work-around this.
You will need to set you symbolic links to have relative references.
On the Windows machine the NFS client driver is resolving symbolic
links to the local system. There is no provision in the Win32 space
for resolving absolute symbolic links. Win32 still works with "C:",
for example, being the start of an absolute pathname. A relative path
can always work since it works within the context for whatever the
systems is.
So while you have the Unix box with "/usr" exported it's making a
reference to a filesystem "/comp". Outside of the exporting system
this relation can change depending on how a client mounts these FS's
(Unix or Windows).
I'm assuming that "/comp" is a filesystem of it's own on the NFS server.
Is it hanging off of "/" on that system? or is it located elsewhere?
On the server can you move-remount /comp to be under /usr (/usr/comp)
and symlink on the server from /comp to /usr/comp ? Then you could do
relative symlinks from the /usr tree.
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
|
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|
Printable Version
