On Thu, 22 Dec 2005 13:36:40 +0200
Danny Braniss <[EMAIL PROTECTED]> wrote:

> shuttle-3> lsof -v lsof version information:

I forgot that one, here it is:
[EMAIL PROTECTED] lsof -v
lsof version information:
    revision: 4.77
    latest revision: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/
    latest FAQ: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/FAQ
    latest man page: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_man
    constructed: Thu Dec 22 12:00:24 CET 2005
    constructed by and on: [EMAIL PROTECTED]
    compiler: cc
    compiler flags: -pipe -DHASEFFNLINK=i_effnlink -DHASF_VNODE -DHASCPUMASK_T 
-DHASSBSTATE -DHAS_KVM_VNODE -DHAS_UFS1_2 -DHAS_NO_SI_UDEV -DHAS_SI_PRIV 
-DFREEBSDV=6000 -DHASFDESCFS=2 -DHASPSEUDOFS -DHASNULLFS -DHAS9660FS 
-DHAS_NO_ISO_DEV -DHASIPv6 -DLSOF_VSTR="6.0-STABLE" -I/usr/src/sys -O
    loader flags: -L./lib -llsof -lkvm
    system info: FreeBSD kg-quiet.kg4.no 6.0-STABLE FreeBSD 6.0-STABLE #1: Thu 
Dec 22 06:29:24 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/QUIET amd64
    Only root can list all files.
    /dev warnings are enabled.
    Kernel ID check is enabled.
    Device cache file read-only paths:
        Named via -D: none
        Named in environment variable LSOFDEVCACHE: none
        Personal path format (HASPERSDC): "%h/%p.lsof_%L"
        Modified personal path environment variable: LSOFPERSDCPATH
        LSOFPERSDCPATH value: none
        Personal path: /root/.lsof_kg-quiet
    Device cache file write paths:
        Named via -D: none
        Named in environment variable LSOFDEVCACHE: none
        Personal path format (HASPERSDC): "%h/%p.lsof_%L"
        Modified personal path environment variable: LSOFPERSDCPATH
        LSOFPERSDCPATH value: none
        Personal path: /root/.lsof_kg-quiet

I don't have any more suggestions.
-- 
Regards,
Torfinn Ingolfsen,
Norway

_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to