Re: update-db cron job: solving a long-standing issue

2007-09-17 Thread Milan
Mark Schouten said: > I prefer this too. I also think it is good to think about newbies, but > is it really necessary to ignore more advanced users just because they > know what they're looking for? I know I would be annoyed if locate was > missing on my server. > We're not talking about servers

Re: update-db cron job: solving a long-standing issue

2007-09-17 Thread Thilo Six
> I don´t know if that already happens, but the same way updatedb could be > instructed to do a 'delta' only and leave unchanged files alone (instead of > update the whole db each time). # time /etc/cron.weekly/slocate real1m6.354s user0m0.247s sys 0m0.581s # time /etc/cron.weekly/s

Re: update-db cron job: solving a long-standing issue

2007-09-17 Thread Mark Schouten
On Mon, 2007-09-17 at 12:27 +0100, Colin Watson wrote: > > I fully agree. Installing *two* search tools by default is too much. > > We probably should not uninstall locate on upgrades, but we should not > > put it into new installations. One is painful enough (although they do > > not server the s

Re: update-db cron job: solving a long-standing issue

2007-09-17 Thread Vincenzo Ciancia
On 17/09/2007 Mark Schouten wrote: > > > Can we not come up with a way to generate the locate database from > > > tracker instead? > > I prefer this too. I also think it is good to think about newbies, but > is it really necessary to ignore more advanced users just because they > know what they're

Re: update-db cron job: solving a long-standing issue

2007-09-17 Thread Sebastien Bacher
Le lundi 17 septembre 2007 à 08:03 +0200, Martin Pitt a écrit : > I fully agree. Installing *two* search tools by default is too much. > We probably should not uninstall locate on upgrades, but we should not > put it into new installations. That will break gnome-search-tools (the panel item to

Re: update-db cron job: solving a long-standing issue

2007-09-17 Thread Colin Watson
On Mon, Sep 17, 2007 at 08:03:49AM +0200, Martin Pitt wrote: > Milan [2007-09-15 16:54 +0200]: > > We can also think (and this is my opinion ;-) ) that the locate command > > is only used by advanced users that now how to install slocate in two > > minutes, and thus that we don't need to install it

Re: update-db cron job: solving a long-standing issue

2007-09-17 Thread Scott James Remnant
On Mon, 2007-09-17 at 08:03 +0200, Martin Pitt wrote: > Milan [2007-09-15 16:54 +0200]: > > We can also think (and this is my opinion ;-) ) that the locate > command > > is only used by advanced users that now how to install slocate in > two > > minutes, and thus that we don't need to install it b

Re: update-db cron job: solving a long-standing issue

2007-09-16 Thread Martin Pitt
Hi, Milan [2007-09-15 16:54 +0200]: > We can also think (and this is my opinion ;-) ) that the locate command > is only used by advanced users that now how to install slocate in two > minutes, and thus that we don't need to install it by default. Newbies > don't use locate in a terminal, but Track

Re: update-db cron job: solving a long-standing issue

2007-09-16 Thread Milan
Thilo: OK, I didn't realise that. I closed this outdated Bug 27918 consequently. To Thilo and Mark and Scott: You agree that the operation of installing slocate is a piece of cake for an admin or a power user, and even if it is "surprising", it's not an issue for them. We can keep locate on the s

Re: update-db cron job: solving a long-standing issue

2007-09-16 Thread Thilo Six
Milan wrote the following on 15.09.2007 16:54 > 3) when not on battery Just for the record. On feisty the cron is not started when on battery here, unless i plug the power cable in. > Milan -- Thilo key: 0x4A411E09 -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubunt

Re: update-db cron job: solving a long-standing issue

2007-09-16 Thread Thilo Six
Scott Kitterman wrote the following on 16.09.2007 00:43 > I use locate regularly on desktops and servers. If there are locate > variants that update synchronously rather than once a day, I say looking > into that is the best answer. would that slowdown file operations (mv, rm, cp)? > It w

Re: update-db cron job: solving a long-standing issue

2007-09-15 Thread Scott Kitterman
On Sat, 15 Sep 2007 17:53:11 +0200 Soren Hansen <[EMAIL PROTECTED]> wrote: >On Sat, Sep 15, 2007 at 04:54:57PM +0200, Milan wrote: >> We can also think (and this is my opinion ;-) ) that the locate >> command is only used by advanced users that now how to install slocate >> in two minutes, and thus

Re: update-db cron job: solving a long-standing issue

2007-09-15 Thread Mark Schouten
On Sat, Sep 15, 2007 at 05:49:37PM +0200, Vincenzo Ciancia wrote: > On 15/09/2007 Wouter Stomp wrote: > > Wouldn't it be possible to replace locate with tracker somehow? Or let > > locate use the tracker database? > > I would like to add that often "dpkg -S" can replace locate. Ehm, locate works

Re: update-db cron job: solving a long-standing issue

2007-09-15 Thread Soren Hansen
On Sat, Sep 15, 2007 at 04:54:57PM +0200, Milan wrote: > We can also think (and this is my opinion ;-) ) that the locate > command is only used by advanced users that now how to install slocate > in two minutes, and thus that we don't need to install it by default. I agree with this. Heck, I consi

Re: update-db cron job: solving a long-standing issue

2007-09-15 Thread Vincenzo Ciancia
On 15/09/2007 Wouter Stomp wrote: > Wouldn't it be possible to replace locate with tracker somehow? Or let > locate use the tracker database? I would like to add that often "dpkg -S" can replace locate. Vincenzo -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modif

Re: update-db cron job: solving a long-standing issue

2007-09-15 Thread Wouter Stomp
On 9/15/07, Milan <[EMAIL PROTECTED]> wrote: > We can also think (and this is my opinion ;-) ) that the locate command > is only used by advanced users that now how to install slocate in two > minutes, and thus that we don't need to install it by default. Newbies > don't use locate in a terminal,

update-db cron job: solving a long-standing issue

2007-09-15 Thread Milan
The slocate cron.daily job has long been an issue, making users ask why their computers were not responding or simply working hard without any explanation. This little 'bug' is giving a really bad impression to new users, making Ubuntu look 'Windows-like' (the worst for us), that is to say unstable