Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 91 - This is some kind of superkill
This is some kind of superkill
Status: CLOSED DUPLICATE of bug 78
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1998-11-16 11:01 EST by michelcas
Modified: 2016-06-27 16:21 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1998-11-16 11:04:13 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description michelcas 1998-11-16 11:01:01 EST
I am using:
  Red Hat Linux release 5.1 (Manhattan)
  Kernel 2.0.34 on an i586

This little code:
  #include <fcntl.h>
  #include <errno.h>
  #include <stdio.h>
  #include <stdlib.h>
  #include <unistd.h>

  int main(int argc, char *argv[]) {
    int s, p;
    if (argc != 2) {
      fputs("Please specify a pid to send signal to.\n",
    } else {
      p = atoi(argv[1]);
    s = fcntl(0,F_GETFL,0);
    printf("Sending SIGIO - press enter.\n");
    printf("SIGIO send attempted.\n");
    return 0;

Can kill just about anything without looking at ownership.

I just guessed the problem is in the kernel ???

I am nost sure if this have been fixed, or even looked at
but a little pointer to a solution would be greatly


Comment 1 Bill Nottingham 1998-11-16 11:04:59 EST
*** This bug has been marked as a duplicate of 78 ***
Comment 2 openshift-github-bot 2016-06-27 16:21:22 EDT
Commit pushed to master at https://github.com/openshift/origin-web-console

Fixes Issue #91 - Build-configs URL Tab Navigation

-Can now use ?tab=summary, ?tab=configuration, and ?tab=environment to navigate around the build-configs page.

Note You need to log in before you can comment on or make changes to this bug.