Re: strange behavior

[Aurelin]

I'm not that used to umask, but could it be that for some reason your default permission is set to 644? Because if you then subtract 006, you'd get 64-2.. Maybe this'd lead to 640 (because.. Have you ever heard of a permission set to a value below zero?)

*think*

Quoting craig.ab...@americredit.com:

I just read that on Linux the default for files is 666.. So 002 wouldn't give 644 anyway, would it?

In the rssh.conf file I have the following.

# Set the default umask
umask = 006
# Users configuration
user=bob:006:00011:/test

a permission of 664 ?



________________________________

Lately for some reason files are not getting the correct permissions anymore? they now get 640 instead of 644. I change the unask to 000 and the files get Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.

binDt7tT2HWJ8.bin
Description: PGP Public Key

pgpvX96BAVwsY.pgp
Description: PGP Digital Signature

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
rssh-discuss mailing list
rssh-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rssh-discuss