|
Home > Archive > Debian Developers > July 2005 > Please participate in popularity-contest
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Please participate in popularity-contest
|
|
| Petter Reinholdtsen 2005-07-23, 9:07 pm |
|
Please help the install team and others get a better view on the use
of packages in Debian. To do this, install the popularity-contest
package and say yes to participate.
The results are updated daily on <URL:http://popcon.debian.org/>, and
the information is used to make the Debian CDs, to give developers an
idea of the use of their packages, and the project an idea on the use
of the different architectures.
At the moment, this is the relative ordering of architectures
reporting to popularity-contest. I would love to see more machines
reporting in.
1 0.02% m68k
1 0.02% hurd-i386
1 0.02% ppc64
2 0.03% kfreebsd-i386
3 0.05% mipsel
4 0.07% arm
4 0.07% s390
8 0.13% mips
16 0.27% ia64
24 0.40% hppa
33 0.56% alpha
72 1.21% sparc
98 1.65% powerpc
279 4.69% amd64
5398 90.81% i386
5944 100.00% total (ignored 620 without arch info)
New in version 1.30 is support for reporting using HTTP POST, to make
it possible for machines without working MTA to participate as well.
Please direct any questions to popcon-developers at lists.alioth.debian.org.
Friendly,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Michelle Konzack 2005-07-24, 8:07 am |
| Am 2005-07-24 01:56:24, schrieb Petter Reinholdtsen:
> At the moment, this is the relative ordering of architectures
> reporting to popularity-contest. I would love to see more machines
> reporting in.
>
> 1 0.02% m68k
> 1 0.02% hurd-i386
> 1 0.02% ppc64
> 2 0.03% kfreebsd-i386
> 3 0.05% mipsel
> 4 0.07% arm
> 4 0.07% s390
> 8 0.13% mips
> 16 0.27% ia64
> 24 0.40% hppa
> 33 0.56% alpha
> 72 1.21% sparc
> 98 1.65% powerpc
> 279 4.69% amd64
> 5398 90.81% i386
Are there really only 5398 machines in i386 ?
I cant belive it... I have already 13 i386 machines with popcon and
now I will install it on my Macintosh IIvx, my SPARCstation 10, my
iMac and my new Digital Alpha 64/166 (bought for some days on eBay)
And on most Desktop PC's I have installed at my Clients, popcon is
running. Maybe around 150 PC's in Strasbourg.
> 5944 100.00% total (ignored 620 without arch info)
>
> New in version 1.30 is support for reporting using HTTP POST, to make
> it possible for machines without working MTA to participate as well.
Cool, this will be better, because I have to made hacks to get the
messages out of some of my systems which are in a protected erea.
> Friendly,
Greetings
Michelle
--
Linux-User #280138 with the Linux Counter, http://counter.li.org/
Michelle Konzack Apt. 917 ICQ #328449886
50, rue de Soultz MSM LinuxMichi
0033/3/88452356 67100 Strasbourg/France IRC #Debian (irc.icq.com)
| |
| Petter Reinholdtsen 2005-07-24, 8:07 am |
| [Michelle Konzack]
> Are there really only 5398 machines in i386 ?
Well, you need to remember the 620 reports without any arch info. 95%
of them are probalby running i386 as well. 
> I cant belive it... I have already 13 i386 machines with popcon and
> now I will install it on my Macintosh IIvx, my SPARCstation 10, my
> iMac and my new Digital Alpha 64/166 (bought for some days on eBay)
>
> And on most Desktop PC's I have installed at my Clients, popcon is
> running. Maybe around 150 PC's in Strasbourg.
Great. Please keep up the good work, and try to get more people to
participate as well.
Perhaps some of the reports got lost in the mail? Hopefully the HTTP
option will increase the participation count.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Michelle Konzack 2005-07-24, 8:07 am |
| Am 2005-07-24 14:25:11, schrieb Petter Reinholdtsen:
> Great. Please keep up the good work, and try to get more people to
> participate as well.
I try to encourage and convince my clients to install it. :-)
Some have concerns about security...
> Perhaps some of the reports got lost in the mail? Hopefully the HTTP
> option will increase the participation count.
For my own Computers I have added an internal E-Mail Address,
to know, when it was send... :-)
I hope it will increase.
Greetings and nice Sunday
Michelle
--
Linux-User #280138 with the Linux Counter, http://counter.li.org/
Michelle Konzack Apt. 917 ICQ #328449886
50, rue de Soultz MSM LinuxMichi
0033/3/88452356 67100 Strasbourg/France IRC #Debian (irc.icq.com)
| |
| Andreas Fester 2005-07-24, 5:52 pm |
| >>Perhaps some of the reports got lost in the mail? Hopefully the HTTP[vbcol=seagreen]
it already did, at least by one ;-)
The HTTP option is really a great improvement, especially
for desktop users.
Greetings,
Andreas
--
Andreas Fester
mailto:Andreas.Fester@gmx.de
WWW: http://littletux.homelinux.org
ICQ: 326674288
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Erik Schanze 2005-07-24, 5:52 pm |
| | |
| Michelle Konzack 2005-07-24, 5:52 pm |
| Am 2005-07-24 23:08:00, schrieb Erik Schanze:
> Hi Petter,
> Perhaps more will participate if you zip the report, to reduce traffic.
> It's requested in bug 149425 for years.
>
> At least for modem users popcon traffic is significant.
>
> And yes, I have only a low bandwidth modem line and run popcon, but others
> don't do so.
FullACK. - Most of my friends in Turkey and arabic counties too.
> Kindly regards,
>
> Erik
Greetings
Michelle
--
Linux-User #280138 with the Linux Counter, http://counter.li.org/
Michelle Konzack Apt. 917 ICQ #328449886
50, rue de Soultz MSM LinuxMichi
0033/3/88452356 67100 Strasbourg/France IRC #Debian (irc.icq.com)
| |
| Bernd Eckenfels 2005-07-24, 5:52 pm |
| In article <20050724122511.GM13606@saruman.uio.no> you wrote:
> Well, you need to remember the 620 reports without any arch info. 95%
> of them are probalby running i386 as well.
How can this happen, anyway? PErhaps it would be good to add a option where
one can send a nickname of the owner and look up the reports by it?
Greetings
Bernd
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Ron Johnson 2005-07-25, 3:04 am |
| On Sun, 2005-07-24 at 14:25 +0200, Petter Reinholdtsen wrote:
> [Michelle Konzack]
[snip][vbcol=seagreen]
> Perhaps some of the reports got lost in the mail? Hopefully the HTTP
> option will increase the participation count.
Soon after you put it in Experimental, installed it, for that very
reason.
Maybe a post to d-u would spread the word.
--
-----------------------------------------------------------------
Ron Johnson, Jr.
Jefferson, LA USA
PGP Key ID 8834C06B I prefer encrypted mail.
"Politics is supposed to be the second-oldest profession. I have
come to realize that it bears a very close resemblance to the
first."
Ronald Reagan
| |
| Helmut Wollmersdorfer 2005-07-25, 3:04 am |
| Petter Reinholdtsen wrote:
> Perhaps some of the reports got lost in the mail?
Or because many machines are not turned on that early in the morning.
> Hopefully the HTTP
> option will increase the participation count.
Thx for the message. I now upgraded to 1.30 and checked, if installed on
all my machines.
You should change the description
| When you install this package, it sets up a cron job that will
| anonymously e-mail the Debian developers
^^^^^^
Helmut Wollmersdorfer
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Goswin von Brederlow 2005-07-25, 8:19 am |
| Helmut Wollmersdorfer <helmut.wollmersdorfer@gmx.at> writes:
> Petter Reinholdtsen wrote:
>
>
> Or because many machines are not turned on that early in the morning.
apt-get install anacron
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Henrique de Moraes Holschuh 2005-07-25, 8:19 am |
| On Mon, 25 Jul 2005, Goswin von Brederlow wrote:
> Helmut Wollmersdorfer <helmut.wollmersdorfer@gmx.at> writes:
>
> apt-get install anacron
or aptitude install fcron, for that matter.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Margarita Manterola 2005-07-25, 6:08 pm |
| On 7/25/05, Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de> wro=
te:
> apt-get install anacron
Heh, this doesn't solve the problem that most desktop systems aren't
turned on at that time, because most desktop users won't read this
mail, and therefore won't install anacron.
A better solution (from my point of view, of course), would be to
change the popcon crontab's entry, so that it runs at a time when most
computers are turned on (this is difficult to guess, of course, but
maybe 15:00 ?). After all, it's not a cpu-intensive, or other
resource-intensive task, and can run at any other moment.
--=20
Besos,
Marga
| |
| Pascal Hakim 2005-07-25, 6:08 pm |
| On Mon, Jul 25, 2005 at 10:53:46AM -0300, Margarita Manterola wrote:
> On 7/25/05, Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de> wrote:
>
>
> Heh, this doesn't solve the problem that most desktop systems aren't
> turned on at that time, because most desktop users won't read this
> mail, and therefore won't install anacron.
>
> A better solution (from my point of view, of course), would be to
> change the popcon crontab's entry, so that it runs at a time when most
> computers are turned on (this is difficult to guess, of course, but
> maybe 15:00 ?). After all, it's not a cpu-intensive, or other
> resource-intensive task, and can run at any other moment.
>
'lo,
Running anacron (or fcron or whatever) will make sure you run all of
cron.daily however. This is more useful than just running popcon. If
your computer is turned off, you'll be missing things like log rotation
and your locate database, as well as all your man pages stuff.
Cheers,
Pasc
--
Pascal Hakim 0403 411 672
Do Not Bend
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Adeodato Simó 2005-07-25, 6:08 pm |
| * Margarita Manterola [Mon, 25 Jul 2005 10:53:46 -0300]:
> Heh, this doesn't solve the problem that most desktop systems aren't
> turned on at that time, because most desktop users won't read this
> mail, and therefore won't install anacron.
> A better solution (from my point of view, of course), would be to
> change the popcon crontab's entry, so that it runs at a time when most
> computers are turned on (this is difficult to guess, of course, but
> maybe 15:00 ?). After all, it's not a cpu-intensive, or other
> resource-intensive task, and can run at any other moment.
Or even better, make sure d-i installs anacron for desktop systems.
That could be the case already, I'm not sure. CC'ing debian-boot to
hear something from them.
--
Adeodato Simó
EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
When it is not necessary to make a decision, it is necessary not to make
a decision.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Olaf van der Spek 2005-07-25, 6:08 pm |
| On 7/25/05, Adeodato Sim=F3 <asp16@alu.ua.es> wrote:
> Or even better, make sure d-i installs anacron for desktop systems.
What's the disadvantage of anacron compared to cron (or: Why not
always install it instead of cron)?
> That could be the case already, I'm not sure. CC'ing debian-boot to
> hear something from them.
| |
| Olaf van der Spek 2005-07-25, 6:08 pm |
| On 7/25/05, Pascal Hakim <pasc@redellipse.net> wrote:
> On Mon, Jul 25, 2005 at 04:43:32PM +0200, Olaf van der Spek wrote:
>=20
> Anacron isn't actually a daemon. It's run by cron once a day, and on
> startup/apm-resume.
>=20
> The main 'disadvantage' of anacron, is that it's set up by default to
> only run /etc/cron.{daily,weekly,monthly}. It won't take care of running
> normal cron jobs that would have been scheduled to run otherwise, and
> didn't run because the computer wasn't on.
But cron doesn't do that either (when the system is off), so compared
to cron that's no disadvantage.
| |
| Pascal Hakim 2005-07-25, 6:08 pm |
| On Mon, Jul 25, 2005 at 04:43:32PM +0200, Olaf van der Spek wrote:
> On 7/25/05, Adeodato Simó <asp16@alu.ua.es> wrote:
>
> What's the disadvantage of anacron compared to cron (or: Why not
> always install it instead of cron)?
>
Anacron isn't actually a daemon. It's run by cron once a day, and on
startup/apm-resume.
The main 'disadvantage' of anacron, is that it's set up by default to
only run /etc/cron.{daily,weekly,monthly}. It won't take care of running
normal cron jobs that would have been scheduled to run otherwise, and
didn't run because the computer wasn't on.
Cheers,
Pasc (with his "I'm the anacron maintainer" hat on)
--
Pascal Hakim 0403 411 672
Do Not Bend
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Joey Hess 2005-07-25, 6:08 pm |
| Adeodato Simó wrote:
> Or even better, make sure d-i installs anacron for desktop systems.
> That could be the case already, I'm not sure. CC'ing debian-boot to
> hear something from them.
It doesn't do so currently. It does for laptops though, so not too big a
leap I suppose.
--
see shy jo
| |
| Goswin von Brederlow 2005-07-25, 6:08 pm |
| Pascal Hakim <pasc@redellipse.net> writes:
> On Mon, Jul 25, 2005 at 04:43:32PM +0200, Olaf van der Spek wrote:
>
> Anacron isn't actually a daemon. It's run by cron once a day, and on
> startup/apm-resume.
>
> The main 'disadvantage' of anacron, is that it's set up by default to
> only run /etc/cron.{daily,weekly,monthly}. It won't take care of running
> normal cron jobs that would have been scheduled to run otherwise, and
> didn't run because the computer wasn't on.
>
> Cheers,
>
> Pasc (with his "I'm the anacron maintainer" hat on)
Will you report a bug or shall I?
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Marc Haber 2005-07-26, 8:00 am |
| On Mon, 25 Jul 2005 19:50:34 +0200, Goswin von Brederlow
<brederlo@informatik.uni-tuebingen.de> wrote:
>Pascal Hakim <pasc@redellipse.net> writes:
running[vbcol=seagreen]
>
>Will you report a bug or shall I?
How can anacron decide whether it is ok to run a hourly cron job once
or n times, or whether a cron job is only meaningful if it is run at
the right time and does more harm being run at the wrong time than
being missed altogether?
Greetings
Marc
--=20
-------------------------------------- !! No courtesy copies, please !! =
-----
Marc Haber | " Questions are the | Mailadresse im =
Header
Mannheim, Germany | Beginning of Wisdom " | =
http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 =
72739834
| |
| Henrique de Moraes Holschuh 2005-07-26, 8:00 am |
| On Tue, 26 Jul 2005, Marc Haber wrote:
> On Mon, 25 Jul 2005 19:50:34 +0200, Goswin von Brederlow
> <brederlo@informatik.uni-tuebingen.de> wrote:
>
> How can anacron decide whether it is ok to run a hourly cron job once
> or n times, or whether a cron job is only meaningful if it is run at
> the right time and does more harm being run at the wrong time than
> being missed altogether?
fcron can, but it does not have enough functionality to *replace* cron yet.
I just ask that people don't bother filing a bug, and code it and send me
(and upstream) a patch, instead.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Olaf van der Spek 2005-07-26, 8:00 am |
| On 7/26/05, Marc Haber <mh+debian-devel@zugschlus.de> wrote:
> On Mon, 25 Jul 2005 19:50:34 +0200, Goswin von Brederlow
> <brederlo@informatik.uni-tuebingen.de> wrote:
ng[vbcol=seagreen]
>=20
> How can anacron decide whether it is ok to run a hourly cron job once
> or n times, or whether a cron job is only meaningful if it is run at
> the right time and does more harm being run at the wrong time than
> being missed altogether?
Isn't it the responsibility of the job itself to check for that (if it
does more harm than good)?
Timing guarantees are rarely given.
| |
| Goswin von Brederlow 2005-07-26, 8:00 am |
| Marc Haber <mh+debian-devel@zugschlus.de> writes:
> On Mon, 25 Jul 2005 19:50:34 +0200, Goswin von Brederlow
> <brederlo@informatik.uni-tuebingen.de> wrote:
>
> How can anacron decide whether it is ok to run a hourly cron job once
> or n times, or whether a cron job is only meaningful if it is run at
> the right time and does more harm being run at the wrong time than
> being missed altogether?
>
> Greetings
> Marc
A missed cron job should never be run multiple times. If that is realy
needed then the job itself should make sure it is run often enough. I
doubt anything will need that or even get usefull results from running
multiple times. I certainly wouldn't want my mrtg, runs every 5
minutes, to be run 1000 times after boot.
Nothing garanties that cron jobs are run at the right time. Running
it a bit later (whenever you boot) is just like it being delayed due
to excess load. If there are things that shouldn't be run at the wrong
time we should find them and protect them in the job itself.
I think overall it serves the users more to default to running missed
cronjobs on boot than not. If that causes you problems you can always
purge anarcron or fcron or protect the jobs itself. There might eb
cases where it harms but those should be the minority.
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Kevin B. McCarty 2005-07-26, 5:58 pm |
| Bernd Eckenfels wrote:
> In article <20050724122511.GM13606@saruman.uio.no> you wrote:
>
> How can this happen, anyway? PErhaps it would be good to add a option where
> one can send a nickname of the owner and look up the reports by it?
IIRC the version of popularity-contest in woody didn't report the
architecture, so those 620 machines probably haven't updated to sarge yet.
regards,
--
Kevin B. McCarty <kmccarty@princeton.edu> Physics Department
WWW: http://www.princeton.edu/~kmccarty/ Princeton University
GPG: public key ID 4F83C751 Princeton, NJ 08544
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Graham Wilson 2005-07-26, 5:58 pm |
| On Tue, Jul 26, 2005 at 03:12:10PM +0200, Goswin von Brederlow wrote:
> I think overall it serves the users more to default to running missed
> cronjobs on boot than not. If that causes you problems you can always
> purge anarcron or fcron or protect the jobs itself. There might eb
> cases where it harms but those should be the minority.
Seems to make sense. Are there any cases where having anacron installed
by default would mess something up?
--
gram
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Helmut Wollmersdorfer 2005-07-26, 5:58 pm |
| Graham Wilson wrote:
> On Tue, Jul 26, 2005 at 03:12:10PM +0200, Goswin von Brederlow wrote:
[vbcol=seagreen]
> Seems to make sense. Are there any cases where having anacron installed
> by default would mess something up?
I would not like to have it on 7/24 servers. There could be problems
after longer power outages in combination with weak scripts (which use
dates as file names). But this "should be the minority". And such logic
will even have problems without anacron.
Helmut Wollmersdorfer
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Goswin von Brederlow 2005-07-26, 5:58 pm |
| Helmut Wollmersdorfer <helmut.wollmersdorfer@gmx.at> writes:
> Graham Wilson wrote:
>
>
>
> I would not like to have it on 7/24 servers. There could be problems
> after longer power outages in combination with weak scripts (which use
> dates as file names). But this "should be the minority". And such
> logic will even have problems without anacron.
>
> Helmut Wollmersdorfer
How will that be a problem? They will run once at (shortly after)
bootup and end up with a slightly wrong date in the filename.
If you only include the week in the name a simple if [ -e log.$WEEK ];
then exit 1; fi will protect against running twice in one week. If
overwriting the log on the next scheduled run is a problem use that.
Certainly no debian package should be vulnerable to this.
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Helmut Wollmersdorfer 2005-07-26, 5:58 pm |
| Goswin von Brederlow wrote:
> Helmut Wollmersdorfer <helmut.wollmersdorfer@gmx.at> writes:
[vbcol=seagreen]
> How will that be a problem? They will run once at (shortly after)
> bootup and end up with a slightly wrong date in the filename.
A real example: A large organisation names the daily logs (each 1-2 GB)
of some servers by date. They exactly contain records from 0:00 to
24:00. After transfer to a dedicated server a cron job uses 'date
--date=yesterday' and 'find' to start an analyzing script. anacron
cannot solve this, but it will not damage something (just result in some
error messages, and/or unnecessary CPU hours in worst case). To make
this anacron-proof would need complex bookkeeping and exception handling.
Helmut Wollmersdorfer
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Steve Greenland 2005-07-26, 8:49 pm |
|
[vbcol=seagreen]
Note that by running only cron.{daily,weekly,monthly}, anacron is
not forced to parse crontabs, worry about permissions, change users,
etc. etc. etc. All it has to do is run scripts.It's not a bug, it's a
significant design choice.
Perhaps popcon should create an @boot job as well as daily. The @boot
job could check "have I run yet today", and then DTRT.
Steve
--
Steve Greenland
The irony is that Bill Gates claims to be making a stable operating
system and Linus Torvalds claims to be trying to take over the
world. -- seen on the net
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Petter Reinholdtsen 2005-07-27, 5:56 pm |
| [Erik Schanze]
> Perhaps more will participate if you zip the report, to reduce
> traffic. It's requested in bug 149425 for years.
[Michelle Konzack]
> FullACK. - Most of my friends in Turkey and arabic counties too.
The HTTP upload is sending a gzip-ed version. I'm working on a
version compressing the emails as well, but the receiving end is yet
to be written.
If you have little bandwith, use HTTP for now.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Petter Reinholdtsen 2005-07-27, 5:56 pm |
| [Ron Johnson]
> Soon after you put it in Experimental, installed it, for that very
> reason.
I got a parse error on this one. I suspect you are unaware that the
HTTP option is available in unstable, version 1.30.
> Maybe a post to d-u would spread the word.
Yes, that would be nice. But I leave that to someone reading that
list.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Michelle Konzack 2005-07-27, 5:56 pm |
| Am 2005-07-27 21:59:05, schrieb Petter Reinholdtsen:
> The HTTP upload is sending a gzip-ed version. I'm working on a
> version compressing the emails as well, but the receiving end is yet
> to be written.
>
> If you have little bandwith, use HTTP for now.
I think, my own four ADSL-Lines 8M/512k are enough, but
some of my clients have only partial E1 or small ADSL,
where the downsteam is 1 MBit and the upstream 128kBit
My friends in not western contries using V.34/90 and
will very happy if it works now compressed.
Greetings
Michelle
--
Linux-User #280138 with the Linux Counter, http://counter.li.org/
Michelle Konzack Apt. 917 ICQ #328449886
50, rue de Soultz MSM LinuxMichi
0033/3/88452356 67100 Strasbourg/France IRC #Debian (irc.icq.com)
| |
| Philip Ross 2005-07-28, 6:01 pm |
| Helmut Wollmersdorfer wrote:
> Graham Wilson wrote:
>
>
>
>
> I would not like to have it on 7/24 servers. There could be problems
> after longer power outages in combination with weak scripts (which use
> dates as file names). But this "should be the minority". And such logic
> will even have problems without anacron.
Anacron provides protection against running cron jobs a second time due
to a reboot or power outage. The first task in
cron.(daily|weekly|monthly) runs anacron -u cron.(daily|weekly|monthly).
This updates anacron's last run timestamp with the current date. When
anacron next runs at boot, it will only run the tasks using anacron if a
day, week or month have elapsed since the last timestamp was written.
Phil
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Ron Johnson 2005-07-28, 6:01 pm |
| On Wed, 2005-07-27 at 22:00 +0200, Petter Reinholdtsen wrote:
> [Ron Johnson]
>
> I got a parse error on this one. I suspect you are unaware that the
> HTTP option is available in unstable, version 1.30.
Yes. But I installed it back when it entered Exprimental.
>
> Yes, that would be nice. But I leave that to someone reading that
> list.
I think I can do that.
--
-----------------------------------------------------------------
Ron Johnson, Jr.
Jefferson, LA USA
PGP Key ID 8834C06B I prefer encrypted mail.
In 1929, when the Great Depresion hit, while all the other
tabulating companies retrenched, Thomas Watson Sr. insisted that
IBM's factories stay open and R&D spending increase. Thus, in
1935 when FDR signed the Social Security Act, and businesses and
gov't had a huge need for tabulating/sorting machines, IBM was in
position to dominate the industry, and did so for the next 45
years.
| |
| GOMBAS Gabor 2005-07-29, 8:08 am |
| On Tue, Jul 26, 2005 at 03:12:10PM +0200, Goswin von Brederlow wrote:
> Nothing garanties that cron jobs are run at the right time. Running
> it a bit later (whenever you boot) is just like it being delayed due
> to excess load. If there are things that shouldn't be run at the wrong
> time we should find them and protect them in the job itself.
Running a job a little later is not a problem. Running a job during work
hours when it was scheduled to run during the night _is_ a problem since
such jobs can (and usually do) hog both memory and I/O bandwidth, making
interactive work difficult.
In such cases not running the job for a day or two is way better than
running it at a time it was not meant to run; not because it causes
damage but because it causes real user inconvenience.
Gabor
--
---------------------------------------------------------
MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of Sciences
---------------------------------------------------------
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
|
|
|
|