search for: shutds

...nd i tested it under wine 1.1.7 The install works, but securom not (a bug has already been filled in), and the game starts with a crack! I had to add some dll's and disable dxgi, but that's not a huge problem. When launching single player, it works and i am ~ 8 seconds ingame, but then it shutds down... In my output i can see this 100 times: fixme:d3d_shader:shader_glsl_load_constants >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glUniform4fvARB @ glsl_shader.c / 445 fixme:d3d_shader:shader_glsl_load_constantsF >>>>>...

From: Chris Barker <barker at ling.ucsd.edu> To: openssh-unix-dev at mindrot.org Subject: X forwarding (still) broken on Linux This may be a lack-of-adequate-documentation problem rather than a bug, but I can't get X forwarding to work: localhost$ set | grep DIS DISPLAY=localhost.localdomain:11.0 localhost$ set | grep XA XAUTHORITY=/tmp/ssh-gzg13204/cookies localhost$ ssh -v

On Sun, 9 Apr 2000, barker at ling.ucsd.edu wrote: > This may be a lack-of-adequate-documentation problem rather than a bug, > but I can't get X forwarding to work: > > localhost$ set | grep DIS > DISPLAY=localhost.localdomain:11.0 > localhost$ set | grep XA > XAUTHORITY=/tmp/ssh-gzg13204/cookies > localhost$ ssh -v localhost > SSH Version

Hello there, I have a problem with replication between two domain controllers, dc1 and dc2. Distribution: Debian 8.5 Samba-Distribution: sernet-samba 4.3.11-14 The replication on dc2 working fine without any failures. But the synchronization on dc1 gives the failure "WERR_BAD_NETPATH". Because the message "BAD_NETPATH" I checked the DNS-resolution:

Am 23.08.2016 um 15:36 wrote Heinz Allerberger via samba: > Hello there, > > I have a problem with replication between two domain controllers, dc1 > and dc2. > Distribution: Debian 8.5 > Samba-Distribution: sernet-samba 4.3.11-14 > > The replication on dc2 working fine without any failures. > But the synchronization on dc1 gives the failure "WERR_BAD_NETPATH".

Thank you for your response. The point is that I have configured my system to shut down at the event "upsc Inform@localhost ups.status"!="OL", not at "LB". So there will be no /etc/killpower file created. At an ups.status != "OL" event, the following script named "notifyme" is run: echo `date` >> /root/upsLog echo " No power, shutting