Setting rights for a single file

[MarkRCC]

I had assumed this would be a "no brainer" when asked by a staff member, but it has turned into a journey of discovery that I'm sure you fine folks can help solve.

A staff member asked if I could give rights to another staff member to a single file located in his network account. I, of course, said sure but I can only seem to grant rights to the folder that the file is located in and not just the individual file. I solved the problem by creating a new folder in his account and moving the desired file to it and then setting rights for the folder.

My question is this. How does one set rights for an individual file located within a folder?

Thanks in advance!

Mark

btw: Netware 5sp6

 

[GiaBetiu]

Assign the required rigths to the file!
If the user has no access to the folder that the file belongs, then you can still access the fle using the whole path of that file ( ex: g:\privatefolder\mysharedfile.doc).
If you want to use Windows Explorer for example to browse to the required file then you have to set the FileScan right to the directories above (one or more, depending also if you have IRF (inherited rights filter) or not).

If need more info, contact me.
Gia Betiu
m.betiu@chello.nl
Computer Eng. CNE 4, CNE 5

 

[TheLad]

I agree, although I would not get into the habit of doing this as it is an administration nightmare. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[GiaBetiu]

Come on,... administration nightmare is to do this in NT. Or to configure an entire File Sytem Rights...
Gia Betiu
m.betiu@chello.nl
Computer Eng. CNE 4, CNE 5

 

[TheLad]

No, administration nightmare is to do this for all of the users collegues. If you do it for one person, the rest will follow like sheep. Tell me how you keep control of that? A spreadsheet? There's the possibility of a lot of file-specific trustees to remember!!

You're probably better off with a controlled shared area with only certain users having access in a curcumstance like that - that is if this is going to become a regular thing.

Gia - I've never quite got my head round NT rights anyway. Why start with all rights and have to restrict stuff?? Novell certainly have the upper hand with their file system. Nice and easy, you know where you are! -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[GiaBetiu]

This situation should be an exception.

As about NT, I have some experience, and the conclusion is dificult to design, dificult to maintain, and very time consuming. Most of the time the solution is a poor design, without flexibility. And I can say the same about Microsoft Directory Services ( NT 4, or AD).

As you say:
"It's true, its damn true!"
Gia Betiu
m.betiu@chello.nl
Computer Eng. CNE 4, CNE 5

 

[salserocito]

I agree with TheLad... keep it in a controlled area and give rights to only the chosen few that require it. Trying t administer by User would truely be a nightmare! Unless you have an office of 5 Users. )

Good Luck!

 

[MarkRCC]

I agree, except that setting the rights to this file is a special exception having to do with an internal audit.....argghhh....

 

[TheLad]

It's a catch 22 situation. You assign rights to files - messy. You give the users a shared area where anyone can dump stuff - without management and proper setting up, can get messy as well.

We have shared areas per department with only those users in the department having access. This way, we know who owns the data in a specific area. We put disk space restrictions on each directory to stop the server filling up. If they run out, they either delete stuff or justify why they need all of their data. Works for us (they very rarely justify, they mostly delete). -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------