From: Jim Bayer <kc9aop@gmail.com>
To: Chuck Hast <wchast@gmail.com>
Cc: Linux-Hams <linux-hams@vger.kernel.org>
Subject: Re: Running Listen
Date: Thu, 9 Dec 2004 16:58:38 -0600 [thread overview]
Message-ID: <e524c532041209145849580078@mail.gmail.com> (raw)
In-Reply-To: <620c905704120905527c439dc@mail.gmail.com>
Did you try setting the sticky bit?
As root type chmod a+s <file>. This sets the owner and group sticky
bit to root. Then anyone who runs the program runs it as root.
On Thu, 9 Dec 2004 08:52:57 -0500, Chuck Hast <wchast@gmail.com> wrote:
> Folks,
> I am trying to run listen as a non-root user. I have checked the permissions
> and group stuff, all appears Ok, it I run it as root, it takes off just fine,
> but if I run it as a non-root user I get this error:
> socket: Operation not permitted
>
> I have done some looking and see something to the effect that tcpdump
> must be run as root or you get the same error, is this true of listen also?
>
> Indeed I wanted to set up listen so I could have a log in directly to a listen
> session so I could just log in remotely and observe the goings on's on the
> different ports of the switch. (Has high speed internet connection so there
> is not problem there) Again I can ssh into the box as root and start a listen
> session just fine, but as anything else I get the above infamous error.
>
> --
> Chuck Hast
> To paraphrase my flight instructor;
> "the only dumb question is the one you DID NOT ask resulting in my going
> out and having to identify your bits and pieces in the midst of torn
> and twisted metal."
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
'73'
Jim - KC9AOP
prev parent reply other threads:[~2004-12-09 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 13:52 Running Listen Chuck Hast
2004-12-09 16:26 ` Curt, WE7U
2004-12-09 22:58 ` Jim Bayer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e524c532041209145849580078@mail.gmail.com \
--to=kc9aop@gmail.com \
--cc=linux-hams@vger.kernel.org \
--cc=wchast@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.