[Linuxconsole-commit]CVS: ruby/linux/drivers/char vt_ioctl.c,1.63,1.64

[James S. <jsi...@us...>]

Update of /cvsroot/linuxconsole/ruby/linux/drivers/char
In directory usw-pr-cvs1:/tmp/cvs-serv13024

Modified Files:
	vt_ioctl.c 
Log Message:
oops. Missed a }

Index: vt_ioctl.c
===================================================================
RCS file: /cvsroot/linuxconsole/ruby/linux/drivers/char/vt_ioctl.c,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -d -r1.63 -r1.64
--- vt_ioctl.c	2001/11/13 19:38:22	1.63
+++ vt_ioctl.c	2001/11/13 20:10:33	1.64
@@ -1483,20 +1483,22 @@
 		 * is awry
 		 */
 		if (kill_proc(new_vc->vt_pid,new_vc->vt_mode.acqsig, 1) != 0) { 
-		/*
-		 * The controlling process has died, so we revert back to
-		 * normal operation. In this case, we'll also change back
-		 * to KD_TEXT mode. I'm not sure if this is strictly correct
-		 * but it saves the agony when the X server dies and the screen
-		 * remains blanked due to KD_GRAPHICS! It would be nice to do
-		 * this outside of VT_PROCESS but there is no single process
-		 * to account for and tracking tty count may be undesirable.
-		 */
-		if (old_vc_mode != new_vc->vc_mode) {
-			if (new_vc->vc_mode == KD_TEXT) 
-				unblank_screen(new_vc->display_fg);
-			else
-				do_blank_screen(new_vc);
+			/*
+		 	 * The controlling process has died, so we revert back 
+		 	 * to normal operation. In this case, we'll also change
+			 * back to KD_TEXT mode. I'm not sure if this is 
+		 	 * strictly correct but it saves the agony when the X 
+                   	 * server dies and the screen remains blanked due to
+		 	 * KD_GRAPHICS! It would be nice to do this outside of
+		         * VT_PROCESS but there is no single process to account
+		         * and tracking tty count may be undesirable.
+		 	 */
+			if (old_vc_mode != new_vc->vc_mode) {
+				if (new_vc->vc_mode == KD_TEXT) 
+					unblank_screen(new_vc->display_fg);
+				else
+					do_blank_screen(new_vc);
+			}
 		}
 	}