Re: watch: fatal: cannot open snoop device

From: clayton rollins (crollins666_at_hotmail.com)
Date: 06/20/04

  • Next message: Jim Trigg: "Re: The FreeBSD Diary: 2004-05-30 - 2004-06-19"
    To: freebsd-newbies@freebsd.org
    Date: Sun, 20 Jun 2004 17:45:39 +0000
    
    

    On June 20, 2004 "drew schulman" <drewunf@hotmail.com> wrote:
    >
    >How do I enable this program in FreeBSD 5.2.1?
    >
    >It was working fine before I reinstalled.
    >
    >-su-2.05b# watch -co p2
    >watch: snp module not available: Operation not permitted
    >watch: fatal: cannot open snoop device
    >

    Before I say anything else, I should say that all questions
    should be sent to freebsd-questions@freebsd.org. I'm
    not allowed to actually answer your question here, but
    maybe I can point you to some doc.s to help you out.

    According to 'man watch':
    "The watch utility allows the user to examine all data
    coming through a specified tty using the snp(4) device."

    According to 'man snp':
    "The kernel must be compiled with device snp or the snp
    device must be loaded, for these devices to be available."

    (Refer to the original man pages for more info.)

    Given those statements, refer to the following section
    of the handbook for advice on compiling a kernel and/or
    checking what configuration you used:
    http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html

    Alternately, refer to the kld man page for information
    on loading kernel modules.

    The above links are just my guess of what may be
    happening. If you do already have the snp device
    available and/or continue to have trouble getting it to
    work, you're encouraged to write freebsd-questions@.
    (And, please include information on your kernel
    configuration, etc.)

    Regards,
    Clayton Rollins

    _________________________________________________________________
    Get fast, reliable Internet access with MSN 9 Dial-up – now 3 months FREE!
    http://join.msn.click-url.com/go/onm00200361ave/direct/01/

    _______________________________________________
    freebsd-newbies@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-newbies
    To unsubscribe, send any mail to "freebsd-newbies-unsubscribe@freebsd.org"


  • Next message: Jim Trigg: "Re: The FreeBSD Diary: 2004-05-30 - 2004-06-19"

    Relevant Pages

    • [Full-Disclosure] RE: remote kernel exploits?
      ... > I know that a similar problem was fixed in FreeBSD a little ... I believe the `similar problem' to which you refer is described here: ... > Since this is a problem in the kernel, ... These are problems in the handling of arguments to certain system ...
      (Full-Disclosure)
    • FreeBSD Status report for Oct-Dec 2003
      ... Bluetooth stack for FreeBSD ... Not much to report. ... Bluetooth kernel modules appear to be stable. ... concerns and some src committers are willing to commit the patches. ...
      (freebsd-current)
    • FreeBSD Status Report for Oct-Dec 2003
      ... Bluetooth stack for FreeBSD ... Not much to report. ... Bluetooth kernel modules appear to be stable. ... concerns and some src committers are willing to commit the patches. ...
      (freebsd-hackers)
    • FreeBSD Status Report for Oct-Dec 2003
      ... Bluetooth stack for FreeBSD ... Not much to report. ... Bluetooth kernel modules appear to be stable. ... concerns and some src committers are willing to commit the patches. ...
      (freebsd-stable)
    • RE: FreeBSD 4.11 P13 Crash
      ... I do not want to jinx myself, but after back revving to FreeBSD 4.9 + ... think it is related to IPFilter in conjunction with 4 Intel nics and/or ... page fault while in kernel mode ... Okay this time my kernel was recompiled so there are no modules to ...
      (freebsd-hackers)