-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20.01.2014 17:26, Tim Landscheidt wrote:
>
> As I wrote last month in
> http://permalink.gmane.org/gmane.org.wikimedia.toolserver/6450, you
> can export an XML dump of your project's issues (you'll have to
> download attachments manually (or write
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.01.2014 03:21, Tim Landscheidt wrote:
> These are two very different problems.
>
> AFAICS the wiki can be moved rather easily; your mail trig- gered
> me to finally create the bug from my notes written long ago :-)
> (cf. https://bugzilla.wikime
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I would vote strongly to keep the wiki and also JIRA somewhere
accessible. Both contain a serious amount of history and documentation.
Can that be done?
Greetings
DrTrigon
On 25.12.2013 21:05, Emilio J. RodrÃguez-Posada wrote:
> Hi all;
>
> I'm no
use non-free
libraries? What e.g. when the tool developer got permission to use a
library and it is open source - but the owner does not want to make it
free? Or the license(s) labs wants to enforce?
Greetings
On 20.08.2013 08:31, Ryan Lane wrote:
> On Tue, Aug 20, 2013 at 1:35 PM, Dr. Tri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> If you're asking "is it safe to move tools to Labs", my experience
> so far say "yes". I can't speak for all unique toolserver
> features, though.Cheers,Magnus
> If you don't care about losing your (nfs) file system every once in
> a while and havin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello DaB
Thanks for your answer!
> If you make a more detailed question, maybe I can give you a more
> detailed answer.
E.g. is it still planned to discontinue the TS? Having 2 payed admins
does not sound like that... - good news?
Thanks and Gree
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10.08.2013 12:37, legoktm wrote:
> On Sat, Aug 10, 2013 at 5:26 PM, Dr. Trigon <mailto:dr.tri...@surfeu.ch>> wrote:
>
> Hello all!
>
> Pywikibot finished GIT migration. Now a question has anybody ever
> tryed to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello DaB!
Could you please give me a short update - the end of 2013 is
approaching, what is the current state for TS resp. Labs?
Thanks and Greetings
DrTrigon
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all!
Pywikibot finished GIT migration. Now a question has anybody ever
tryed to clone and use the e.g. the pywikibot/compat repo on the TS?
If I do, I get and .git folder of about 200MB which nearly fills my
home quota. (this is the plain clone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
May be someone working with dumps can help?
- Original Message
Subject:[Pywikipedia-l] xmlreader.py
Date: Wed, 31 Jul 2013 20:03:17 +0100 (BST)
From: Automatik Wikipedia
Reply-To: Automatik Wikipedia , Pywikipedia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> yes, there is a minor problem with ngnix I haven?t time to fix yet.
> Also there is a harmless error-message about quota at login.
The funny thing with the quota error-message is, it works correct if I
do have over-quota when loggin-in. Not so if th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks so much!! ;)
Have a nice day!
On 23.05.2013 14:50, Marlen Caemmerer wrote:
> Hello,
>
> the SVN waited for configuration on the new installation and is
> now finished.
>
> Kind regards Marlen/nosy
>
>
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luckily those externals are important just for 1 script (catimages.py)
at the moment, so if you checkout the code except those 2 externals,
you should be fine - don't worry! ;)
In fact I was thinking about doing a svnsync from
https://svn.toolserver.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for that! (btw. ;)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlGc+f0ACgkQAXWvBxzBrDDyRwCgmDHayk3D162RF/TFbgDun7lp
gJIAmwXxA6FDsTD7AAv09eNIP5JKM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please make SVN work... :)
On 20.05.2013 12:39, Jason Y. Lee wrote:
> Please let me know if there is any assistance I can provide.
>
> Regards,
>
> AllyUnion
>
>
> On Mon, May 20, 2013 at 1:37 AM, Dr. Trigon <mailto:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is SVN supposed to be down still?
DrTrigon
On 18.05.2013 22:37, DaB. wrote:
> Hello all, At Saturday 18 May 2013 22:29:07 DaB. wrote:
>> We can only think of one solution: Replacing the solaris at the
>> ha-nodes with linux. But this can not start b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Admins!
Could please someone take care of TS-1301 [1]? This ticket is now open
for quite a while and having the possibility to generate docs and
coverage reports on the TS would be very favourable.
[1] https://jira.toolserver.org/browse/TS-1301
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Admins!
As I noticed it seems as if the cronjobs are executed correct at the
moment, so may be TS-1635 [1] can be closed. Though the statistics on
[2] are gone. Furthermore there are several cron-servers on [3] now.
Can someone give me a brief
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks a lot!!
On 11.04.2013 09:49, Marlen Caemmerer wrote:
> Hey,
>
> I set your account expiration to 1st June.
>
> Cheers Marlen/nosy
>
> On Thu, 11 Apr 2013, Dr. Trigon wrote:
>
>> Date: Thu, 11 Apr 2013 09:43:31
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If that helps, here you are:
https://jira.toolserver.org/browse/TS-1635
Greetings and all the best
DrTrigon
On 10.04.2013 16:14, K. Peachey wrote:
> Was this issue filed in JIRA?
>
> On Wed, Apr 10, 2013 at 11:18 PM, Dr. Trigon
> wrot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If that helps, here you are:
https://jira.toolserver.org/browse/TS-1636
Greetings and all the best
DrTrigon
On 10.04.2013 16:14, K. Peachey wrote:
> I would recommend opening a ticket in JIRA.
>
> On Wed, Apr 10, 2013 at 11:17 PM, D
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
PING! Any news here? Why was this ignored?
Greetings
DrTrigon
On 30.03.2013 14:37, Dr. Trigon wrote:
> Hello everybody! Hello nosy!
>
> Do you remember the issue below...? :)
>
>
> On 05.03.2013 13:03, Marlen Caemmerer wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello beloved Admins!
Today I recognized that my account has expired (what a pitty) so I
tried as usual to login and renew but just get this:
> $ ssh drtri...@nightshade.toolserver.org Your account has expired;
> please contact your system administra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello everybody!
Hello nosy!
Do you remember the issue below...? :)
On 05.03.2013 13:03, Marlen Caemmerer wrote:
>> Then another issue - I think (again - sorry but yes! ;) we have
>> some problem with cron job execution. When looking at my bots
>> (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05.03.2013 13:03, Marlen Caemmerer wrote:
>> Since about 2 days I got errors because my bot script started
>> running on mayapple.toolserver.org. As you might remember, back
>> last year (I think) there were [1], [2] and [3].
>>
>> [1] https://jira
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello DaB!
Hello to everybody!
Since about 2 days I got errors because my bot script started running
on mayapple.toolserver.org. As you might remember, back last year (I
think) there were [1], [2] and [3].
[1] https://jira.toolserver.org/browse/TS-1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks DaB whatever you (or someone else? ;) did!
Now it works again as you can see from looking at [1] there was clearly
a drop in executed jobs now it is on a constant level again! Cool!
[1] http://munin.toolserver.org/Login/hawthorn/cron_jobs_sh.h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04.02.2013 01:30, DaB. wrote:
>> I am now noticing issues with my cronjobs too.
>
> What exactly is the problem?
Cronjobs not getting executed (as usual... ;) - at the moment I do
also have jobs in SGE queue that do not get runned at all (at least
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello!
There were 2 messages here during Janury reporting problems with cron.
I am now noticing issues with my cronjobs too. By looking at [1] you
are able to see that the strange behaviour started somewhen week 2 and
3 (mid January). Do we have again
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Happy new year to everybody!! (thanks for all your work!)
So long, and thanks for all the fish (for this year ;))
DrTrigon
On 24.12.2012 14:04, DaB. wrote:
> Hello all,
>
> 2012 was not very kind to the Toolserver and 2013 will not be much
> better
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25.11.2012 23:44, DaB. wrote:
> I have not decided yet if I will remain as root under this
> circumstances for 2013 ? I will tell you my decision until next
> Sunday.
I hope you stay - but it's (of course) your decision...
> For now I will head to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25.11.2012 23:03, Marlen Caemmerer wrote:
> Hello,
>
> nice to hear. I had a look from all sides but it seemed the SGE
> master thought the queues on the hosts were full. This morning when
> I looked I saw only willow doing some jobs - ortelius sti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today it seems to be working and fully functional again... Nice job! ;)
Thanks to all involved here!
Greetings and have a nice weekend
DrTrigon
On 24.11.2012 22:10, Platonides wrote:
> On 24/11/12 21:38, Dr. Trigon wrote:
>>> @All
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24.11.2012 21:15, Merlissimo wrote:
> At 20:32 on Nov 23th sge on turnera stopped and was started at
> damiana. The qmaster thread started successfully because it
> responses pings and so on. But the scheduler thread seems not to
> work. qconf -tsm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello
I have an issue with my jobs not executed or more precise queued since
midnight:
job-ID prior name user state submit/start at
queue slots ja-task-ID
-
---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+ 1(the same for me)
Greetings
DrTrigon
On 23.11.2012 20:46, Tim Landscheidt wrote:
> (anonymous) wrote:
>
>>> At some point I even logged in, clicked an issue, clicked Edit
>>> (which uses AJAX) and then the Edit screen wouldn't load due to
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Intressting - my cron jobs refused to run today with...
/bin/sh: qcronsub: not found
...until you wrote this mail. Since then it looks better again.
Thanks and greetings
DrTrigon
On 11.10.2012 13:05, DaB. wrote:
> Hello all,
>
> yesterday I remov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09.10.2012 20:57, DaB. wrote:
> Hello, At Tuesday 09 October 2012 20:57:01 DaB. wrote:
>> A hopefully small feature request; would it be possible to have a
>> more detailed view added? Max 1 day (24 hours) in order to
>> resolve the minutes too... (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09.10.2012 13:14, DaB. wrote:
> yesterday I hacked together a munin-script for that; you can find
> it at [1] for hawthorn (the current submit-host). I will add it to
> clematis (the other submit-host) and maybe the other hosts too
> today.
>
> Sin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
By the way; DaB what can we TS user do to support you here in a
somewhat strategic way?
May be this is obvious and I just missed the point - but summarizing
should not be of any harm... ;)
Greetings
DrTrigon
On 26.09.2012 12:48, DaB. wrote:
> Hello
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06.10.2012 11:06, Dr. Trigon wrote:
> So essentially MY BOTS DO NOT RUN ANYMORE BECAUSE OF THE TS
> OVERLOAD for at least 1 week!! I am up to stop my work here in
> wikipedia (de, en, commons, meta, ...) because I do not have the
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello DaB
As mentioned on TS-1466 [1] (may be the wrong place...?) I do have some
issues with my scripts because of the python version (again!) we really
should have the
[1]
https://jira.toolserver.org/browse/TS-1466?focusedCommentId=22109#comment-22
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all!
So essentially MY BOTS DO NOT RUN ANYMORE BECAUSE OF THE TS
OVERLOAD for at least 1 week!! I am up to stop my work here
in wikipedia (de, en, commons, meta, ...) because I do not
have the time and ressources to keep my bots running...
Sorr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14.09.2012 16:46, Merlissimo wrote:
> btw.: This bug only exists because many people on this mailinglist
> did not like the solaris crontab format and requested to install
> vixie cron as alternative cron some years ago.
As far as I remember my mai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello DaB
As we discussed yesterday evening I changed minutes for my cronjobs
from 00 to 07. As I explained yesterday only 4 of 5 jobs runned, today
after the change only (!) 2 of 5 jobs runned. So this change did not
help, but made it worse... any id
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What about a tool that gather some statistics from all users cron(ie)tab
files and show them on a public (or for logged-in users only)
page/place.
The idea is that user can get an clue on what times have high or low job
loads.
Something like:
00 - u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Looks good on a first glimpse. Thanks a lot!!
On 13.09.2012 18:12, DaB. wrote:
> Hello again, At Thursday 13 September 2012 18:08:55 DaB. wrote:
>> A word to the pywikipedia-framework users: At the moment it is
>> unclear if the old python-unicode-bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wanted to suggest Wikidata support - but it's already done! Good work!
Greetings
DrTrigon
On 05.09.2012 03:25, Sumana Harihareswara wrote:
> DeltaQuad suggested I tell the bots developers on this list about
> this tool, because he hadn't heard about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To me as someone always struggling with sql queries (since I am not an
expert at all) this sound somehow promising. May be there will be a
comprehensive set of queries going to pipes one day. Then I would simply
have to pick up the pipe and connect it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15.07.2012 14:39, DaB. wrote:
> -There is "-l arch=lx" now which will run your task at a
> linux-host. -There is also "-l arch='*'" that will run your task on
> linux or Solaris.
...just wondering, what about running a job on NON-linux-hosts only?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for this update and all the work included!!
On 14.07.2012 16:09, DaB. wrote:
> Hello all, it is finally done, the linux-login-servers (yarrow and
> nightshade) are ready to use :-). You should be able to login from
> the outside to these boxes
me up (and this is bad)
But after all at the moment it works and I just wanted to
thank you all involved here for your help and work!!
Greetings
DrTrigon
On 15.06.2012 10:57, Dr. Trigon wrote:
> Hello all!
>
> I have a bunch of cronie jobs calling qcronsub for several times
> with very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.07.2012 01:18, Platonides wrote:
> I stand corrected. I had only tested with the second line.
In fact it is very good thing to look at other codes and check them
BEFORE running... ;) Thanks for your work and feedback!
Greetings
-BEGIN PGP S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Sorry Trigon, but it doesn't work. It is calculating the percentage
> of the hard limit at which your soft limit is set. Not really what
> you wanted :)
May be we do not have the same 'quota -v' output, mine is:
> Disk quotas for drtrigon (uid 1340
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry, this copy'n'paste is useless - thus I attached the file here.
On 09.07.2012 19:20, Dr. Trigon wrote:
> So no answer at all... that's a pitty!
>
> To have at least some information, I wrote a small script:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Any updates/progress here?? DaB?
On 19.06.2012 22:07, Dr. Trigon wrote:
> Don't panic = no need to hurry
>
> But I need at least a feedback; which you gave me know! Thanks for
> this!
>
> To be honest it could become
t; qcronsub -l h_rt=00:05:00 -l virtual_free=50M -m as -j y -b y -N
> maintenance $HOME/warnuserquota.py >/dev/null
may be this helps other users having the same problems/issues.
Greetings
DrTrigon
On 12.06.2012 21:39, Dr. Trigon wrote:
> Is this also supposed to solve TS-1317 [1]??
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When will quota system start sending warn mails? (as already requested a
few times...)
Or; under what conditions are warn mails sent? When reaching softquota?
Greetings
DrTrigon
On 22.06.2012 23:41, DaB. wrote:
> Hello all,
>
> willow was rebooted
any useful one ;)...!
Thanks a lot and greetings
DrTrigon
On 20.06.2012 02:04, Russell Blau wrote:
> On Sun, Jun 17, 2012, at 02:29 PM, Dr. Trigon wrote:
>>
>> So why are some of my cronie-jobs or qcronsub calls (typically 1
>> per day) silently dropped?
>>
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Don't panic = no need to hurry
But I need at least a feedback; which you gave me know! Thanks for this!
To be honest it could become a pain to get this bot running on TS since
it has a lot of exotic (opencv) and C/C++ dependencies... So I think it
do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
No anwser at all? Even after this 2nd request?
Is this because nobody *can* help? Or because nobody *wants* to help??
DrTrigon
On 12.06.2012 21:31, Dr. Trigon wrote:
> Hello admins!
>
> I opened TS-1360 [1] quite some time ago. Wo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today 2 jobs did not execute! Does this mean it is getting worse?
Is the toolserver about to die?
Greetings
DrTrigon
On 15.06.2012 10:57, Dr. Trigon wrote:
> Hello all!
>
> I have a bunch of cronie jobs calling qcronsub for several time
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- Original Message
Subject: Re: [Toolserver-l] Write attempts to wiki API from TS timeout
Date: Fri, 15 Jun 2012 10:42:40 +0200
From: Dr. Trigon
To: marlen.caemme...@wikimedia.de
> I spoke to a network admin since the WMF w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> For your other questions: stderr and stdout are buffered by sge
> because they are send over network. At the toolserver configuration
> it is send to localhost by default because all execution servers
> have the same filesystems mounted. At a standar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Is it by chance your last cron entry? Remember that there must be a
> newline finalising your crontab or the last command won't get
> executed.
>
> You should get this output: $ crontab -l | tail -c1 | od -c 000
> \n 001
No it is not - but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17.06.2012 00:07, Merlissimo wrote:
> All jobs named "subster_en" were executed successfully by sge
> (mostly on wolfsbane). The return code of your python script was 0,
> but the runtime was only about a minute. You can check it by
> executing e.g.
:51, Marlen Caemmerer wrote:
> Hello,
>
> which one is it exactly?
>
> Cheers nosy
>
> On Fri, 15 Jun 2012, Dr. Trigon wrote:
>
>> Date: Fri, 15 Jun 2012 10:57:43 From: Dr. Trigon
>> Reply-To: toolserver-l@lists.wikimedia.org
>> To: Toolserver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all!
I have a bunch of cronie jobs calling qcronsub for several times
with very similar settings (just the language of the wiki used
changes). In total there are 5 jobs - regurarly (about ever 2nd
day) one of those jobs does not get executed and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Open a bug in https://bugzilla.wikimedia.org/ with the ops
> keyword.
Done: https://bugzilla.wikimedia.org/show_bug.cgi?id=37536
Thanks for the hint!
DrTrigon
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG wit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is this also supposed to solve TS-1317 [1]??
[1] https://jira.toolserver.org/browse/TS-1317
Thanks and greetings!
DrTrigon
On 16.05.2012 21:31, DaB. wrote:
> Hello At Wednesday 16 May 2012 21:28:30 DaB. wrote:
>> There have been arrangements with s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello everybody!
I experience a behaviour with SGE that I cannot understand.
Due to logging my scripts output I redirect stdout and stderr.
When running the script from console (e.g. on willow) all
write actions to stderr are passed as they are, but r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello admins!
I opened TS-1360 [1] quite some time ago. Would it be possible to
install those libs or is there any serious issue? The bot using
this is now ready-to-use and should be runned from TS now.
[1] https://jira.toolserver.org/browse/TS-1360
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello everybody!
Since 7th (may be 6th) of june my bot is not able to write pages on
dewiki larger than ~130KB. The bot code was not changed but now occurs
MaxTriesExceeded errors with all the time.
Befor it was able to write pages >600KB. It looks t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I did not open an JIRA bug because it vanished again... so; SOLVED.
But if someone is interessted in details:
http://toolserver.org/~drtrigon/DrTrigonBot/mainbot.log.2012-03-11
http://toolserver.org/~drtrigon/DrTrigonBot/mainbot.log.2012-03-12
http:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13.03.2012 17:05, Tim Landscheidt wrote:
> Even if only for PHP there would be a critical mass, it'd be still
> useful to Perl, Python and other developers. For example, I think
> it is a common problem to normalize links - e. g., are
> "[[Diskussi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is it now usual behaviour that qcronsub adds all command-line
options to following calls too?
qcronsub [some options] script.py [other options]
used to call
script.py [other options]
but now it calls
script.py [some options] script.py [other optio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04.03.2012 16:25, Platonides wrote:
> On 04/03/12 01:06, Merlissimo wrote:
>> In both cases the old behavior was without -m a -b y, so
>>
> (...)
>> The -b y option is mostly useful for binaries, e.g. if you don't
>> submit the python script itself
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04.03.2012 01:06, Merlissimo wrote:
> Some weeks ago i installed a script that removes empty log files
> for standard error/output stream after job execution. Many people
> used this option to prevent that their homedir contain so many
> empty error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04.03.2012 01:21, Platonides wrote:
> On 04/03/12 00:17, Dr. Trigon wrote:
>> And here my key question arises; you mentioned 'qacct' to get
>> more info (thanks for this hint) and this is one of the biggest
>> problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04.03.2012 01:06, Merlissimo wrote:
> In both cases the old behavior was without -m a -b y, so
>
> 'cronsub [jobname] [command]' has become 'qcronsub -l h_rt=06:00:00
> -l virtual_free=100M -N [jobname] [command]
>
> 'cronsub -l [jobname] [command
> have the same problem again if willow must be shut down for a longer
> time (which hopefully never happens).
First thanks a lot for your effort!! First I thought why making it even
more complicate (this increases the possibility of mal-config) but after
setting my cron(ie)tab up I have t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> That's the right thing to do. If the server is so overloaded it
> can't even fork, it makes no sense for SGE to create more processes
> there. They should be scheduled in some other host.
I thought SGE does itself load balance it and use another hos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, e.g. SGE job are not even sent to queue, they go into 'qw' directly
after starting... So my bot is down...
Greetings
DrTrigon
On 03.03.2012 05:17, Matthew Bowker wrote:
> Hi, all:
>
> The login server Willow seems to be having load issues. Se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Meanwhile you can use
ssh drtri...@login.toolserver.org
or login to 'willow' instead of 'nightshade' directly.
And for running bots you should use SGE, e.g from
ssh drtri...@submit.toolserver.org
But recently I do also have issues with bots/cronj
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
and the 'subster_en' does not run anymore now... can someone explain me
why??? I did not change any config or settings (as I am aware)...
...honestly ;)
Greetings
On 12.02.2012 13:45, Dr. Trigon wrote:
> Hello all
>
> I got s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all
I got some strange info by mail tonight, first:
> Unable to run job: error: no suitable queues. Exiting.
>
then later
> Job 1601224 (subster_ar) Set in error state Exit Status = -1
> Signal = unknown signal User
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Try to sleep well and focus on exams (it is an fact the same I am doing
at the moment ;) - thus; I wish you success!
Greetings
DrTrigon
ps.: Thanks for the support and service anyway!
On 09.02.2012 00:55, DaB. wrote:
> Hello all,
>
> the dumping o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
May be late - had no time - but:
HELLO 'nosy'! Nice to have a new admin here! :)
Greetings and have fun!
DrTrigon
Am 24.10.2011 23:47, schrieb DaB.:
> Hello all,
>
> how Daniel Kinzler told you in his mail of 5. October already, the
> german chapte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 14.09.2011 00:08, schrieb Platonides:
> Heh, you could have added - and _ to the list of allowed characters
> (that's why I pointed out *what* I wanted to protect from).
Because you mentioned alphanumeric I thought of using "str.isalnum()"
but the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> btw.: ...is the pywikipedia framework's 'getUrl' safe in this
> sence?
Just for information: no it is not! The following works:
>>> print site.getUrl("file:///etc/passwd", no_hostname = True)
(this could be an issue for other homebrew bots blindly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 12.09.2011 16:43, schrieb Merlijn van Deen:
> On 12 September 2011 16:00, Dr. Trigon <mailto:dr.tri...@surfeu.ch>> wrote:
>
> So this "IOError: [Errno 2] No such file or directory: ..." was
> NOT triggered becau
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 12.09.2011 14:21, schrieb DaB.:
> Hello, At Monday 12 September 2011 14:21:05 DaB. wrote:
>> "/home/drtrigon/xslt/../../dab/text.xml" as path, it returns an
>> "IOError: [Errno 2] No such file or directory: ..."
>
> which is true. There is no text
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 12.09.2011 13:43, schrieb DaB.:
> to prevent something like
>
> "../../dab/text.xml" as parameter with would result in
>
> "/home/drtrigon/xslt/"../../dab/text.xml" which would result to
>
> "/home/dab/text.xml"
Yes I assumed something similar,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 11.09.2011 22:59, schrieb Platonides:
> Dr. Trigon wrote:
>> import os allowed = [item for item in os.listdir('.') if '.xslt'
>> in item] if xslt not in allowed: # return some neutral/blank
>> message (hi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I have checked out your code out of SVN and I am playing with it. I
> don't think I have commit rights to your repository, so you
> shouldn't worry.
I'm not worried about the repo, but my home dir on the TS... since
I am FULLY trusting all TS-users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I extracted all files that are not there (there are also some i18n
> differences).
>
> bot_control.py clean_user_sandbox.py Doxyfile dtbext
> dtbext/dtbext_pywikibot
> dtbext/dtbext_pywikibot/dtbext_exceptions.py
> dtbext/dtbext_pywikibot/__init_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> It even works without. For urllib2, you do need to use file://
> urls.
>
> valhallasw@dorthonion:~$ python Python 2.6.5 (r265:79063, Apr 16
> 2010, 13:09:56) [GCC 4.4.3] on linux2 Type "help", "copyright",
> "credits" or "license" for more informati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I looked at your SVN (in case we'd like to create a shared
> repository or put it into Pywiki's SVN) and I, too, found that you
> have actually your own copy of pywikipedia there. Are there any
> local changes that would need to be included in the ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 11.09.2011 20:50, schrieb DaB.:
> Hello, At Sunday 11 September 2011 20:49:25 DaB. wrote:
>> all files on the toolserver can be checked for existence, if they
>> are XML files
>
> disabled for this reason.
>
> @drtrigon: Please fix your script BEF
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello TS users!
To close the topic [1] I finally decided to follow the hints given by
Maciej Jaros and Merlissimo and created (since it seams nobody did this
already - please correct me, if I am wrong)
"XSaLT: XSL/XSLT Simple and Lightweight Tool" [2
1 - 100 of 125 matches
Mail list logo
