Bug 31386 - esearch cron script
Bug#: 31386 Product:  Gentoo Linux Version: unspecified Platform: All
OS/Version: Linux Status: RESOLVED Severity: enhancement Priority: P2
Resolution: FIXED Assigned To: genone@gentoo.org Reported By: dberkholz@gentoo.org
Component: Applications
URL: 
Summary: esearch cron script
Keywords:  
Status Whiteboard: 
Opened: 2003-10-17 18:49 0000
Description:   Opened: 2003-10-17 18:49 0000 
I wrote this cron script for eupdatedb. Might add it to the package and install
to /usr/share/doc/${PF}/eupdatedb.cron.

------- Comment #1 From Donnie Berkholz 2003-10-17 18:50:41 0000 ------- 
Created an attachment (id=19380) [details]
cron script

------- Comment #2 From Donnie Berkholz 2003-10-17 18:52:45 0000 ------- 
Created an attachment (id=19381) [details]
Patch to esearch-0.4.2.ebuild

------- Comment #3 From David Peter 2003-10-18 05:05:54 0000 ------- 
Hi,

I think it makes no sense to run eupdatedb hourly/daily/weekly/..
Instead you should run it after you've updated your portage tree
with "emerge sync".

Maybe you find the following script, I wrote useful:
http://forums.gentoo.org/viewtopic.php?t=94102

It calls emerge sync and eupdatedb automatically.

David

------- Comment #4 From Marius Mauch (RETIRED) 2003-10-18 06:26:04 0000 ------- 
Thanks Donnie, added it in 0.4.2-r1. Btw, that script looks very generic,
could be installed by baselayout as a template.

------- Comment #5 From Donnie Berkholz 2003-10-18 18:22:19 0000 ------- 
David,
Why not install esync in the same place, or install it by default in /usr/sbin
or something along with esearch?