From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] [SOLVED] Mysterious sudoers.d error
Date: Wed, 26 Aug 2015 21:12:57 -0400 [thread overview]
Message-ID: <20150827011257.GA22962@waltdnes.org> (raw)
In-Reply-To: <20150826232841.GB522@apio.adsroot.itcs.umich.edu>
On Wed, Aug 26, 2015 at 07:28:41PM -0400, Alec Ten Harmsel wrote
> On Wed, Aug 26, 2015 at 07:20:37PM -0400, Walter Dnes wrote:
> > I've just switched from cdparanoia to cdda2wav, to get track
> > names/artists. As a regular user, I ran...
> >
> > cdda2wav -vall dev=1,0,0 cddb=0 -paranoia -B
> >
> > I got a bunch of complaints about insufficient read and write
> > privileges, but it seems to work OK. I ran the same command as root,
> > and no error messages.
>
> What exactly are the error messages? Most likely you just need to be
> added to the group that has access to CD drives or something like that.
I am a member of groups "cdrom" and "cdrw". Here are the messages...
[d531][waltdnes][~/music/glenn_miller_2a] cdda2wav -vall dev=1,0,0 cddb=0 -paranoia -B
cdda2wav: Insufficient 'file read' privileges. You will not be able to open all needed devices.
cdda2wav: Insufficient 'file write' privileges. You will not be able to open all needed devices.
cdda2wav: Insufficient 'device' privileges. You may not be able to send all needed SCSI commands, this my cause various unexplainable problems.
cdda2wav: Insufficient 'priocntl' privileges. You may get jitter.
cdda2wav: Insufficient 'network' privileges. You will not be able to do remote SCSI.
Type: ROM, Vendor 'TSSTcorp' Model 'CDRWDVD TS-H493B' Revision 'D200' MMC+CDDA
569344 bytes buffer memory requested, transfer size 131072 bytes, 4 buffers, 55 sectors
#Cdda2wav version 3.01a16_linux_4.0.5-gentoo_x86_64_intel-r--core-tm-2-duo-cpu-e4600-@-2.40ghz, real time sched., soundcard, libparanoia support
AUDIOtrack pre-emphasis copy-permitted tracktype channels
> Looks like it's the commas. Try:
>
> waltdnes d531 = (root) NOPASSWD: /usr/bin/cdda2wav -vall dev=1\,0\,0 cddb=0 -paranoia -B
It woiks! No warnings. Thank you very much. To avoid my
"fumble-fingers", I have a short script "~/bin/cdrip"...
#!/bin/bash
sudo /usr/bin/cdda2wav -vall dev=1,0,0 cddb=0 -paranoia -B
This episode prompted me to research further, to see what else has to
be escaped. Google turns up...
http://www.sudo.ws/man/1.8.13/sudoers.man.html#x4f74686572207370656369616c206368617261637465727320616e6420726573657276656420776f726473
> Long lines can be continued with a backslash (`\') as the last
> character on the line.
> White space between elements in a list as well as special syntactic
> characters in a User Specification (`=', `:', `(', `)') is optional.
> The following characters must be escaped with a backslash (`\') when
> used as part of a word (e.g. a user name or host name):
> `!', `=', `:', `,', `(', `)', `\'.
... i.e. "!=:,()\"
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
next prev parent reply other threads:[~2015-08-27 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 23:20 [gentoo-user] Mysterious sudoers.d error Walter Dnes
2015-08-26 23:28 ` Alec Ten Harmsel
2015-08-27 1:12 ` Walter Dnes [this message]
2015-08-27 9:22 ` [gentoo-user] [SOLVED] " Alan Mackenzie
2015-08-27 22:11 ` Walter Dnes
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=20150827011257.GA22962@waltdnes.org \
--to=waltdnes@waltdnes.org \
--cc=gentoo-user@lists.gentoo.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