search for: contunuously

Rajesh M wrote: > i wish to improve the performance further by caching the logins. > current the same is kept disable because when user's change passwords > then they are not able to immediately login with the new password for > some time. How to solve this issue. Dovecot shouldn't be doing that. According to https://wiki2.dovecot.org/Authentication/Caching Data is

We are having a problem that I suspect is due to nmbd giving out obsolete information. Unfortunately the problem can not be reproduced consistently. We have a build system that runs on our Solaris machines where the final files are copied into a distribution directory after being built. Note that copying a new file on top of an old one does not change the file ID. PC users sometimes will see the

Hi all. Is it possible to change DC administrator name from 'Administrator' to something else, for example, to 'DomaAdministr' ? If it is, is it possible via command-line or via LDAP browsers only ? If it do via LDAP browser (of course cn will be changed) , will Samba4 contunue to work correctly ? Also, I offer to add new switch to Samba4 DC provision such as 'adminname' ,

...you keep the components of the system pretty >> much on the level of latest release of each of components. Therefore >> "upgrade" to new release of the system is pretty close to just a >> regular routine update. > > You are describing Debian sid/unstable, which is contunuously updated, > and where there are no releases in the usual sense of the word. Debian > stable releases are a different matter, and correspond very closely to > major releases of RHEL/CentOS. There is always an upgrade path between > consecutive releases of Debian stable. > Yes, LTS, th...

On Tue, May 10, 2016 2:19 am, Johnny Hughes wrote: > On 05/10/2016 02:08 AM, Venkateswara Rao Dokku wrote: >> Hi, >> >> I would like to know whether the valid upgrade path will be present from >> CentOS 7 to future versions like we get for Ubuntu or some other >> operating >> systems. >> >> Right now, I am sure that we do not have proper update

...Debian (and clones): you keep the components of the system pretty > much on the level of latest release of each of components. Therefore > "upgrade" to new release of the system is pretty close to just a > regular routine update. You are describing Debian sid/unstable, which is contunuously updated, and where there are no releases in the usual sense of the word. Debian stable releases are a different matter, and correspond very closely to major releases of RHEL/CentOS. There is always an upgrade path between consecutive releases of Debian stable. -- Liam

...ents of the system pretty >>> much on the level of latest release of each of components. Therefore >>> "upgrade" to new release of the system is pretty close to just a >>> regular routine update. >> >> You are describing Debian sid/unstable, which is contunuously updated, >> and where there are no releases in the usual sense of the word. Debian >> stable releases are a different matter, and correspond very closely to >> major releases of RHEL/CentOS. There is always an upgrade path between >> consecutive releases of Debian stable. &g...

> On Feb 14, 2017, at 5:50 PM, Joseph Tam <jtam.home at gmail.com> wrote: > > Another related security situation I've encountered is when a fraudster > has phished a user's password. A user/admin changes the password, > but forgets to invalidate dovecot's cached entry, allowing the fraudster > contunuing access to the mail account until the TTL expires or user

> Hello Thomas, > > Am 29.01.2015 um 18:12 schrieb Thomas Schulz: > > We have a build system that runs on our Solaris machines where the final > > files are copied into a distribution directory after being built. Note > > that copying a new file on top of an old one does not change the file ID. > > > > PC users sometimes will see the file as having the date

Ok, I've gone through the list archives, and there's a bunch of questions, but no answers. I'm referring to the Error: Network is busy when logging in from both Win95 (a and b versions) and Win98. It seems to never give this message unless the Windoze machine has been rebooted forcefully - it seems as if the samba server hasn't realized that the client has left, and is locking

...nts of the system pretty >>> much on the level of latest release of each of components. Therefore >>> "upgrade" to new release of the system is pretty close to just a >>> regular routine update. >> >> You are describing Debian sid/unstable, which is contunuously updated, >> and where there are no releases in the usual sense of the word. Debian >> stable releases are a different matter, and correspond very closely to >> major releases of RHEL/CentOS. There is always an upgrade path between >> consecutive releases of Debian stable. &g...

Here is some log output that occurs on the production during the process of issuing a net use command from the win95 box to the samba server. The connection reset by peer message appears immediately after the error 54 network is busy message appears on the windows 95 machine. (This is debug level = 10) [1999/05/18 18:21:00, 2] smbd/server.c:main(709) Changed root to / [1999/05/18 18:21:00,

This problem shows up on both Linux and Solaris. I am going to show the logs from a Fedora 2.6.25-14.fc9.i686 machine. We are using 'security = domain' with a Windows 2000 domain controller. We are setting 'password server = starfish2' dispite the fact that the documentation says that this in not necessary as we have found it to be necessary. We are setting 'workgroup =

Adding a section of a debug level 5 log at the end that looks like it might have some usefull information. > This problem shows up on both Linux and Solaris. I am going to show > the logs from a Fedora 2.6.25-14.fc9.i686 machine. > > We are using 'security = domain' with a Windows 2000 domain controller. > We are setting 'password server = starfish2' dispite the

I have done a great deal of reading regarding the network is busy error, but haven't come up with an answer for one particular problem. Here is the situation. Two identical DGUX machines are sitting on a network. Both machines are running Samba 1.9.10 with no problems other than performance. Upon several recommendations about improving performance, they decided to upgrade to 2.0.3.