On Tuesday 16 September 2008 17:47:17 Dirk Heinrichs wrote:
> Am Dienstag, 16. September 2008 17:29:31 schrieb Robert Annessi:
> > How to make paludis quiet so it can be used in cronjobs?
>
> somecommand >/dev/null 2>&1
>
> Replace /dev/null with a file of your choice.

It's hard for me to automatically differ between an info and error message 
from paludis --sync.

My paludis related cronjobs currently look like this (from which I really 
don't like the --sync, because I don't get any error messages):

20 */23 */5 * * if on_ac_power; then for FILE in 
`/usr/share/paludis/ruby/demos/find_unused_distfiles.rb`; do rm -vf ${FILE}; 
done; fi
25 */23 */2 * * if on_ac_power; then paludis --sync >/dev/null 2>&1
40 */23 */2 * * if on_ac_power; then paludis --no-color --report | 
egrep -v '^(Current state of the system||Finished processing [0-9]+ 
packages\. 0 errors\.)$'; fi
45 */23 */2 * * if on_ac_power; then config-decruft | egrep -v '^* Checking '; 
fi


Am I missing any quiet option or how do you handle automatic syncing?

Cheers,
Robert


-- 
/"\  ASCII Ribbon Campaign for - plain text emails
\ /   ______________________   - attachments complying with standards
 X    | signed & encrypted |   - replies below quoted text
/ \   |  emails preferred  |   - lines shorter than 80 characters

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
paludis-user mailing list
[email protected]
http://lists.pioto.org/mailman/listinfo/paludis-user

Reply via email to