Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 7 of 7 for alarm (0.04 sec)

  1. src/cmd/vendor/golang.org/x/sys/unix/zerrors_linux_386.go

    	{9, "SIGKILL", "killed"},
    	{10, "SIGUSR1", "user defined signal 1"},
    	{11, "SIGSEGV", "segmentation fault"},
    	{12, "SIGUSR2", "user defined signal 2"},
    	{13, "SIGPIPE", "broken pipe"},
    	{14, "SIGALRM", "alarm clock"},
    	{15, "SIGTERM", "terminated"},
    	{16, "SIGSTKFLT", "stack fault"},
    	{17, "SIGCHLD", "child exited"},
    	{18, "SIGCONT", "continued"},
    	{19, "SIGSTOP", "stopped (signal)"},
    	{20, "SIGTSTP", "stopped"},
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Tue Jun 04 16:19:04 UTC 2024
    - 34.2K bytes
    - Viewed (0)
  2. src/cmd/vendor/golang.org/x/sys/unix/zerrors_linux_arm64.go

    	{9, "SIGKILL", "killed"},
    	{10, "SIGUSR1", "user defined signal 1"},
    	{11, "SIGSEGV", "segmentation fault"},
    	{12, "SIGUSR2", "user defined signal 2"},
    	{13, "SIGPIPE", "broken pipe"},
    	{14, "SIGALRM", "alarm clock"},
    	{15, "SIGTERM", "terminated"},
    	{16, "SIGSTKFLT", "stack fault"},
    	{17, "SIGCHLD", "child exited"},
    	{18, "SIGCONT", "continued"},
    	{19, "SIGSTOP", "stopped (signal)"},
    	{20, "SIGTSTP", "stopped"},
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Tue Jun 04 16:19:04 UTC 2024
    - 34.2K bytes
    - Viewed (0)
  3. docs/de/docs/index.md

    Für ein vollständigeres Beispiel, mit weiteren Funktionen, siehe das <a href="https://fastapi.tiangolo.com/tutorial/">Tutorial - Benutzerhandbuch</a>.
    
    **Spoiler-Alarm**: Das Tutorial - Benutzerhandbuch enthält:
    
    * Deklaration von **Parametern** von anderen verschiedenen Stellen wie: **Header-Felder**, **Cookies**, **Formularfelder** und **Dateien**.
    Registered: Mon Jun 17 08:32:26 UTC 2024
    - Last Modified: Mon Apr 29 05:18:04 UTC 2024
    - 21.1K bytes
    - Viewed (0)
  4. src/cmd/vendor/golang.org/x/sys/unix/zerrors_linux_amd64.go

    	{9, "SIGKILL", "killed"},
    	{10, "SIGUSR1", "user defined signal 1"},
    	{11, "SIGSEGV", "segmentation fault"},
    	{12, "SIGUSR2", "user defined signal 2"},
    	{13, "SIGPIPE", "broken pipe"},
    	{14, "SIGALRM", "alarm clock"},
    	{15, "SIGTERM", "terminated"},
    	{16, "SIGSTKFLT", "stack fault"},
    	{17, "SIGCHLD", "child exited"},
    	{18, "SIGCONT", "continued"},
    	{19, "SIGSTOP", "stopped (signal)"},
    	{20, "SIGTSTP", "stopped"},
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Tue Jun 04 16:19:04 UTC 2024
    - 34.2K bytes
    - Viewed (0)
  5. src/cmd/vendor/golang.org/x/sys/unix/zerrors_zos_s390x.go

    	{9, "SIGKILL", "killed"},
    	{10, "SIGBUS", "bus error"},
    	{11, "SIGSEGV", "segmentation fault"},
    	{12, "SIGSYS", "bad argument to routine"},
    	{13, "SIGPIPE", "broken pipe"},
    	{14, "SIGALRM", "alarm clock"},
    	{15, "SIGTERM", "terminated"},
    	{16, "SIGUSR1", "user defined signal 1"},
    	{17, "SIGUSR2", "user defined signal 2"},
    	{18, "SIGABND", "abend"},
    	{19, "SIGCONT", "continued"},
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Wed May 08 16:12:58 UTC 2024
    - 39.4K bytes
    - Viewed (0)
  6. src/cmd/cgo/internal/test/test.go

    	)
    
    	signal.Notify(sigCh, sig)
    
    	go func() {
    		n := 0
    		alarm := time.After(time.Second * 3)
    		for {
    			select {
    			case <-waitStart:
    				waitStart = nil
    			case v := <-sigCh:
    				n++
    				if v != sig || n > thres {
    					waitDone <- result{n, v}
    					return
    				}
    			case <-alarm:
    				waitDone <- result{n, sig}
    				return
    			}
    		}
    	}()
    
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Mon May 20 15:50:06 UTC 2024
    - 48.5K bytes
    - Viewed (0)
  7. src/runtime/signal_unix.go

    //
    // 3. It should be a signal that can happen spuriously without
    // consequences. For example, SIGALRM is a bad choice because the
    // signal handler can't tell if it was caused by the real process
    // alarm or not (arguably this means the signal is broken, but I
    // digress). SIGUSR1 and SIGUSR2 are also bad because those are often
    // used in meaningful ways by applications.
    //
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Fri May 10 16:04:54 UTC 2024
    - 45K bytes
    - Viewed (0)
Back to top