Using file filtering for UNIX files

Question

I would like to block Windows users on a multi-protocol file system from being able to open .profile and .login. Both files have been added to .filefilter with odd results. It blocks all Windows access to both files with the exception of allowing Wordpad full access. The documentation states only three character extension should be used. Any ideas on how to block both files beyond a product enhancement request.

Rainer_EMC · Answer

what access policy are you using ?you could use attrib from the Windows side to set the readonly or system attribute so that at least with the default Windows explorer config they wouldnt be displayed

BillStein-Dell · Answer

Using a filefilter in the instance you're describing is not the intended use of file-level filtering. The idea behind it is to prevent certain filetypes from being stored on Celerra Windows shares (for example, blocking mp3 files from user home directories). It can also be configured to selectively allow certain filetypes but block all others (i.e. allowing only Excel spreadsheets from Engineering in the "eng-xls" share). This is why it is designed to recognize "dot three" filename extensions (.mp3, .mov, .jpg, etc).

Modifying Windows file attributes on those files (which will not affect their Unix file permissions) is the best way to achieve your goal.

Celerra

Using file filtering for UNIX files

Was this post helpful?