From: Mat Harris <mat.harris@genestate.com>
To: John Hallam <john@dai.ed.ac.uk>
Cc: linux-admin@vger.kernel.org
Subject: Re: lpd user woes
Date: Tue, 11 Feb 2003 21:22:23 +0000 [thread overview]
Message-ID: <20030211212223.GA2383@genestate.com> (raw)
In-Reply-To: <20030211132619.GA31839@genestate.com>
[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]
There are no differences between the su and su - environments.
I have found a workaround for now, which is setting the uid for lp to 0 i
/etc/passwd but this is (hopefully) only temporary. If anyone knows how to
get lp to access the sound device or lib, please spill.
for now: SOLVED;
On Tue, Feb 11, 2003 at 01:26:19PM +0000, Mat Harris wrote:
> On Tue, Feb 11, 2003 at 01:22:10 +0000, John Hallam wrote:
> > Does it happen if you do `su lp' as root and then execute the code
> > that the lp user tries to execute? It might be that the environment (PATH
> > variable etc.) presented by lpd to its sub-processes is missing some vital
> > piece of information...
>
> if i do `su - lp` it does exactly the same
>
> btw, the code i run for testing is `cat test.mp3 | mpg123 -`
>
> > You could give the lp user group access to the sound device, by
> > changing the ownership and permissions on the sound device or by changing
> > the group membership possibilities for lp in /etc/groups. Either of these
> > may have other consequences.
>
> i have changed /etc/passwd so the group for lp is 0 and changed /etc/groups
> so lp is a member of root but i still have to same problem.
>
> --
> Mat Harris OpenGPG Public Key ID: C37D57D9
> mat.harris@genestate.com www.genestate.com
--
Mat Harris OpenGPG Public Key ID: C37D57D9
mat.harris@genestate.com www.genestate.com
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2003-02-11 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 10:34 lpd user woes Mat Harris
[not found] ` <Pine.GSO.4.44.0302111319050.23807-100000@tron.dai.ed.ac.uk>
2003-02-11 13:26 ` Mat Harris
2003-02-11 21:22 ` Mat Harris [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=20030211212223.GA2383@genestate.com \
--to=mat.harris@genestate.com \
--cc=john@dai.ed.ac.uk \
--cc=linux-admin@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).