search for: 20hrs

...g "gpupdate" in a DOS box on the workstation > and suddenly it worked once, then went back to erroring out. Spamming it > has not fixed it since. I even wrote a small batch script which looped > until gpupdate returned success. It went into an endless loop which > lasted about 20hrs before I stopped it. > > As for the sysvol location, it is in "/samba/var/locks/sysvol", which > worked for a few years, and has just stopped. Permissions appear to be > correct. > > On 05/29/2015 11:24 AM, James wrote: >> On 5/29/2015 10:40 AM, Ryan Ashley wrote:...

...ar problem and knows why or a solution. basically my mongrels seems to work fine. i am running three clusters all which are monitored by monit. monit has the ability to restart a mongrel if it doesn''t pass a port connection test. so the problem is that after some time. aprox. 6hrs. to 20hrs. after clusters are started, the mongrels get restarted by monit due to monit not being able to connect to said port. not all of them at the same time. just some of them, sometimes. the server is pre-production and is getting no hits. could this be the problem and when the server is live, wit...

...I just kept spamming "gpupdate" in a DOS box on the workstation and suddenly it worked once, then went back to erroring out. Spamming it has not fixed it since. I even wrote a small batch script which looped until gpupdate returned success. It went into an endless loop which lasted about 20hrs before I stopped it. As for the sysvol location, it is in "/samba/var/locks/sysvol", which worked for a few years, and has just stopped. Permissions appear to be correct. On 05/29/2015 11:24 AM, James wrote: > On 5/29/2015 10:40 AM, Ryan Ashley wrote: >> Thank you, Louis. This...

...a RAID card, mirror 2 large drives, and add another video card, monitor, if I can get Xen to work to some degree on it. Pointers on how to xfer Windows 2000 old PC to a kvm/qemu/xen are also appreciated. Any other advice appreciated too. I need something that works, I already invested at least 20hrs into this setup. I am not afraid of a challenge, but I was hoping that after so many years of Linux things would finally start to magically work out of the box :) So far I''ve tried debian 4.0, with limited success (c my previous post). I am also familiar with RedHat based systems and...

I am running zfs send/receive on a ~1.2Tb zfs spread across 10x200Gb LUNs. Has copied only 650Gb in ~42Hrs. Source pool and destination pool are from the same storage sub system. Last time when ran, took ~20Hrs. Something is terribly wrong here. What do i need to look to figure out the reason? ran zpool iostat and iostat on the given pool for some clue. but still in a state of confusion now. RR. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris....

...workstation >>> and suddenly it worked once, then went back to erroring >out. Spamming it >>> has not fixed it since. I even wrote a small batch script >which looped >>> until gpupdate returned success. It went into an endless loop which >>> lasted about 20hrs before I stopped it. >>> >>> As for the sysvol location, it is in >"/samba/var/locks/sysvol", which >>> worked for a few years, and has just stopped. Permissions >appear to be >>> correct. >>> >>> On 05/29/2015 11:24 AM, James...

Sorry for the delay, I have been out of town. Your hunch was correct, Rowland. Both getent and id only return local machine accounts, not domain accounts. What have I overlooked which would cause this? I do have winbind in my PAM configuration. James, it has worked for a few years. It recently (in the last year) started having workstations report being unable to access the gpt.ini files. The

...gt; and suddenly it worked once, then went back to erroring >> out. Spamming it >>>> has not fixed it since. I even wrote a small batch script >> which looped >>>> until gpupdate returned success. It went into an endless loop which >>>> lasted about 20hrs before I stopped it. >>>> >>>> As for the sysvol location, it is in >> "/samba/var/locks/sysvol", which >>>> worked for a few years, and has just stopped. Permissions >> appear to be >>>> correct. >>>> >>>&...