search for: sceanrio

I am working with a simple "follow-me"-style service: rather than have something that rings several phones in turn, the user dials a number (in the present implementation, unique to that user) to register his presence at a particular extension. What's the standard way to protect this from unauthorised use? Voicemail()-style, where the user has to enter a PIN once the connection is

I developed a solution to the problem where you might have systems setup w/ winbind mapping GIDs and UIDs, NSS, and PAM setup so windows users can login, but winbind maps possible different UIDs/GIDs from system to system preventing unified UIDs/GIDs in your environment. I tried having one box setup with NSS winbind / PAM etc. plus I made that system an NIS master w/ a script to periodically pull

...990 Around 1 million of inodes in lru table!! These are the inodes kernel has just cached and no operation is currently progress on these inodes. This could be the reason for high memory usage. We've a patch being worked on (merged on experimental branch currently) [1], that will help in these sceanrios. In the meantime can you remount glusterfs with options --entry-timeout=0 and --attribute-timeout=0? This will make sure that kernel won't cache inodes/attributes of the file and should bring down the memory usage. I am curious to know what is your data-set like? Is it the case of too many di...

...ru table!! These are the inodes kernel has >> just cached and no operation is currently progress on these inodes. This >> could be the reason for high memory usage. We've a patch being worked on >> (merged on experimental branch currently) [1], that will help in these >> sceanrios. In the meantime can you remount glusterfs with options >> --entry-timeout=0 and --attribute-timeout=0? This will make sure that >> kernel won't cache inodes/attributes of the file and should bring down the >> memory usage. >> >> I am curious to know what is your...

...> Around 1 million of inodes in lru table!! These are the inodes kernel has just cached and no operation is currently progress on these inodes. This could be the reason for high memory usage. We've a patch being worked on (merged on experimental branch currently) [1], that will help in these sceanrios. In the meantime can you remount glusterfs with options --entry-timeout=0 and --attribute-timeout=0? This will make sure that kernel won't cache inodes/attributes of the file and should bring down the memory usage. > > I am curious to know what is your data-set like? Is it the case of t...

...are the inodes > kernel has just cached and no operation is currently progress on > these inodes. This could be the reason for high memory usage. > We've a patch being worked on (merged on experimental branch > currently) [1], that will help in these sceanrios. In the > meantime can you remount glusterfs with options > --entry-timeout=0 and --attribute-timeout=0? This will make sure > that kernel won't cache inodes/attributes of the file and should > bring down the memory usage. > > I am cur...

...>> ??????? kernel has just cached and no operation is currently progress on >> ??????? these inodes. This could be the reason for high memory usage. >> ??????? We've a patch being worked on (merged on experimental branch >> ??????? currently) [1], that will help in these sceanrios. In the >> ??????? meantime can you remount glusterfs with options >> ??????? --entry-timeout=0 and --attribute-timeout=0? This will make sure >> ??????? that kernel won't cache inodes/attributes of the file and should >> ??????? bring down the memory usage. >> &g...

...> kernel has just cached and no operation is currently progress on > > these inodes. This could be the reason for high memory usage. > > We've a patch being worked on (merged on experimental branch > > currently) [1], that will help in these sceanrios. In the > > meantime can you remount glusterfs with options > > --entry-timeout=0 and --attribute-timeout=0? This will make sure > > that kernel won't cache inodes/attributes of the file and should > > bring down the memory usage. > &g...

On 1/29/2018 2:36 AM, Raghavendra Gowdappa wrote: > > > ----- Original Message ----- >> From: "Ravishankar N" <ravishankar at redhat.com> >> To: "Dan Ragle" <daniel at Biblestuph.com>, gluster-users at gluster.org >> Cc: "Csaba Henk" <chenk at redhat.com>, "Niels de Vos" <ndevos at redhat.com>,