Arch Linux

omgwtfbyobbq

Member

Registered: 2006-07-04

Posts: 226

Using nano with crontab and alsa problems.

I added 'export EDITOR="/usr/bin/nano"' to /etc/profile and ~/.bashrc for shits'n'giggles, but crontab won't use nano for some reason. Do I have to set a nano use flag and compile a version for myself, or is there some other command/config file I need to alter? I can remove vi and symlink /usr/bin/nano to /usr/bin/vi, but that'll probably lead to a thermonuclear explosion that takes out the western seaboard.

I'm also having sporadic trouble with sound. I have it set up so that a couple apps use OSS (vlc,skype) through the onboard card (intel8x0) since they're only on individually and don't need mixing. Everything else I pipe through the default alsa PCM thingy to be mixed and output by the pci card (ice1724).
Once every few boots, I'll find that everything going through the default alsa PCM thingy to the pci card (ice1724) isn't (xmms, mpd, aoss foo, etc..), i.e. no sound from those apps. And everything that was originally going through OSS to the onboard card (intel8x0) is still OSS, but is now going through the pci card (ice1724). Essentially, the sound output to the onboard card is rerouted to the pci card, and blocking the output to the pci card... Any suggestions?

Snowman

Developer/Forum Fellow

From: Montreal, Canada

Registered: 2004-08-20

Posts: 5,212

Re: Using nano with crontab and alsa problems.

for the soud problem, it might be caused by the order that udev loads the modules:
http://wiki.archlinux.org/index.php/Ude … _Each_Boot

allucid

Member

Registered: 2006-01-06

Posts: 259

Re: Using nano with crontab and alsa problems.

if you look at the crontab manpage, crontab uses the VISUAL environment variable to determine the editor instead of the EDITOR environment variable.

I am not sure why crontab uses a different env. variable than every other linux application. That is still a mystery.

omgwtfbyobbq

Member

Registered: 2006-07-04

Posts: 226

Re: Using nano with crontab and alsa problems.

Awesome, both of you were spot on! I still can believe I missed that during man crontab, must've been looking too hard for EDITOR. Thanks!