You are not logged in.
Recently awesome-client started acting odd. I pipe text into a-c from a shell script. If I launch the script manually from my own shell, it works properly. However, the shell script launched by cron has no effect. I know the script is running because it will also wall my consoles and beep.
This is the script in question:
http://bbs.archlinux.org/viewtopic.php? … 48#p466748
Any idea why awesome-client is being fickle about its input?
Last edited by keenerd (2009-05-30 01:06:45)
Offline
Another thread gave the answer. Long story short at some point last month cron began trying to send any job output to the user through sendmail. If you didn't have sendmail configured, the script died. Awesomewm had nothing to do with it, just that awesome-client was the last part of the script and so never executed after cron failed.
The fix was to append
&> /dev/nullto the cron job. The script does not produce output, so dev nulling it is fine.
Offline