[SATLUG] Re: Cron issues with strange sudo twist

Charles Hogan cd_satl at futuretechsolutions.com
Fri Jan 23 22:30:56 CST 2009


If it also runs fine as a cron job under root, you could add a chown 
command to the end of your cron script, or figure out what group the 
offending device needs to be accessed by, and add your user to that group.

Marc Ripley wrote:
> Interesting thing:
> If I run the arecord as su "sudo" it works from a remote login.  So
> evidently some hardware access permissions which are available in gome
> sessions but not in cron or remote sessions work as a superuser.  I
> dont know how to use this discovery to resolve my issue.  I don't want
> to run the jobs under a root cron because the files will not be owned
> by my log in user ID.
> 
> Suggestions?
> 
> On Fri, Jan 23, 2009 at 12:00 PM,  <satlug-request at satlug.org> wrote:
>> Run arecord --list-devices while you are in logged into Gnome, then
>> from console when you are logged out of Gnome.  Gnome may be tearing
>> down the ALSA device when you logout.
>>
>> -Henry


More information about the SATLUG mailing list