Comments for Terrarum http://terrarum.net System Administration and Development Tue, 24 Jan 2012 19:48:09 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on Adding a Calendar Widget to BIRT by Scott Mead http://terrarum.net/administration/adding-a-calendar-widget-to-birt.html#comment-6421 Scott Mead Tue, 24 Jan 2012 19:48:09 +0000 http://terrarum.net/?p=255#comment-6421 <p>You can change the format of what JSCal returns by changing:</p> <p></p> <p><button id="_button">...</p> <pre><code>Calendar.setup({ trigger : '_button', inputField : '', onSelect : function() { this.hide() } }); </code></pre> <p></p> <p>to:</p> <p></p> <p><button id="_button">...</p> <pre><code>Calendar.setup({ trigger : '_button', inputField : '', dateFormat : '%Y-%m-%d %H:%M:%S.000', onSelect : function() { this.hide() } }); </code></pre> <p></p> You can change the format of what JSCal returns by changing:

<button id="_button”>…

Calendar.setup({
    trigger    : '_button',
    inputField : '',
            onSelect   : function() { this.hide() }
});

to:

<button id="_button”>…

Calendar.setup({
    trigger    : '_button',
    inputField : '',
    dateFormat : '%Y-%m-%d %H:%M:%S.000',
            onSelect   : function() { this.hide() }
});

]]> Comment on Automating an Ubuntu Server Install by txomon http://terrarum.net/administration/automating-an-ubuntu-server-install.html#comment-6079 txomon Sun, 15 Jan 2012 15:07:05 +0000 http://terrarum.net/wordpress/?p=17#comment-6079 <p>I would rather use apt-cacher-ng , its the new apt-cacher, and works extremely well. Doesn't need any configuration.</p> I would rather use apt-cacher-ng , its the new apt-cacher, and works extremely well. Doesn’t need any configuration.

]]> Comment on Caching RPMs with automirror by Joe Topjian http://terrarum.net/administration/caching-rpms-with-automirror.html#comment-5001 Joe Topjian Mon, 19 Dec 2011 18:25:28 +0000 http://terrarum.net/?p=334#comment-5001 <p>Another note to make:</p> <p>I was confident that this script would work well for any RPM repository, but after testing over several months, I only had long-term success with CentOS5.</p> <p>I've since begun using Polipo for caching. It's a very small proxy server, and although it caches all data, I've been able to get it to work on some systems where automirror failed.</p> Another note to make:

I was confident that this script would work well for any RPM repository, but after testing over several months, I only had long-term success with CentOS5.

I’ve since begun using Polipo for caching. It’s a very small proxy server, and although it caches all data, I’ve been able to get it to work on some systems where automirror failed.

]]> Comment on Caching RPMs with automirror by Joe Topjian http://terrarum.net/administration/caching-rpms-with-automirror.html#comment-5000 Joe Topjian Mon, 19 Dec 2011 18:22:21 +0000 http://terrarum.net/?p=334#comment-5000 <p>In your last comment you have</p> <p>"ERROR: Getting request failed: Client closed"</p> <p>If this is the last log entry before automirror stops working, I would suspect there is a compatibility issue with RHEL and RedHat's repositories.</p> <p>Have you tried running automirror with --verbose? Does it give any hints?</p> <p>Also does the user running automirror have proper permissions to write to /var/cache/yum/automirror ?</p> <p>As a side note, the location of the cached files can be specified in the rc script or with command-line flags.</p> In your last comment you have

“ERROR: Getting request failed: Client closed”

If this is the last log entry before automirror stops working, I would suspect there is a compatibility issue with RHEL and RedHat’s repositories.

Have you tried running automirror with –verbose? Does it give any hints?

Also does the user running automirror have proper permissions to write to /var/cache/yum/automirror ?

As a side note, the location of the cached files can be specified in the rc script or with command-line flags.

]]> Comment on Caching RPMs with automirror by bushidoka http://terrarum.net/administration/caching-rpms-with-automirror.html#comment-4990 bushidoka Mon, 19 Dec 2011 15:59:18 +0000 http://terrarum.net/?p=334#comment-4990 <p>I'm using RHEL5. And I just checked from another box and it is still not working. You can see it is talking to my proxy on 8181 but it is not saving files in /var/cache/yum/automirror over there</p> <p>yum 31358 root 5u IPv4 2444784 TCP solexa4:47814->solexa-db:8181 (ESTABLISHED) yum 31358 root 10u IPv4 2444789 TCP solexa4:54907->xmlrpc.rhn.redhat.com:https (ESTABLISHED)</p> I’m using RHEL5. And I just checked from another box and it is still not working. You can see it is talking to my proxy on 8181 but it is not saving files in /var/cache/yum/automirror over there

yum 31358 root 5u IPv4 2444784 TCP solexa4:47814->solexa-db:8181 (ESTABLISHED) yum 31358 root 10u IPv4 2444789 TCP solexa4:54907->xmlrpc.rhn.redhat.com:https (ESTABLISHED)

]]> Comment on Caching RPMs with automirror by Joe Topjian http://terrarum.net/administration/caching-rpms-with-automirror.html#comment-4989 Joe Topjian Mon, 19 Dec 2011 15:57:01 +0000 http://terrarum.net/?p=334#comment-4989 <p>Hello,</p> <p>What distribution are you using? I have found that automirror does not work with CentOS/RHEL 6+.</p> <p>If you are using a 6+ distribution, see the note here: http://terrarum.net/administration/caching-rpms-with-automirror.html#update</p> <p>Joe</p> Hello,

What distribution are you using? I have found that automirror does not work with CentOS/RHEL 6+.

If you are using a 6+ distribution, see the note here: http://terrarum.net/administration/caching-rpms-with-automirror.html#update

Joe

]]> Comment on Caching RPMs with automirror by bushidoka http://terrarum.net/administration/caching-rpms-with-automirror.html#comment-4988 bushidoka Mon, 19 Dec 2011 15:39:20 +0000 http://terrarum.net/?p=334#comment-4988 <p>Well I was pretty excited about this, but I cannot seem to make it go. There was already something on port 8080 so I figured out how to make it sit on 8181. I was not sure where it was caching files but think I figured out it is in /var/cache/yum/automirror. On the first try nothing was in there (not even a directory there) so I made the directory, the removed the RPM in question to try again. Did my yum install and it downloaded it afresh - but there is still nothing in /var/cache/yum/automirror.</p> <p>During the download I did "lsof -i 8181" and saw that yum was indeed talking to port 8181. This was all on the same host BTW - automirror running on the same machine I was doing yum on.</p> <p>Log file looks like this :</p> <p>[Mon Dec 19 10:21:56 2011] (13545) Processing: mirrorlist [Mon Dec 19 10:21:56 2011] (13545) Using: external mirror for / [Mon Dec 19 10:21:56 2011] (13545) Processing: repomd.xml [Mon Dec 19 10:21:56 2011] (13545) Using: external mirror for / [Mon Dec 19 10:31:36 2011] (13545) ERROR: Getting request failed: Client closed</p> Well I was pretty excited about this, but I cannot seem to make it go. There was already something on port 8080 so I figured out how to make it sit on 8181. I was not sure where it was caching files but think I figured out it is in /var/cache/yum/automirror. On the first try nothing was in there (not even a directory there) so I made the directory, the removed the RPM in question to try again. Did my yum install and it downloaded it afresh – but there is still nothing in /var/cache/yum/automirror.

During the download I did “lsof -i 8181″ and saw that yum was indeed talking to port 8181. This was all on the same host BTW – automirror running on the same machine I was doing yum on.

Log file looks like this :

[Mon Dec 19 10:21:56 2011] (13545) Processing: mirrorlist [Mon Dec 19 10:21:56 2011] (13545) Using: external mirror for / [Mon Dec 19 10:21:56 2011] (13545) Processing: repomd.xml [Mon Dec 19 10:21:56 2011] (13545) Using: external mirror for / [Mon Dec 19 10:31:36 2011] (13545) ERROR: Getting request failed: Client closed

]]> Comment on Perlish – Try::Tiny by nm http://terrarum.net/development/perlish-trytiny.html#comment-4450 nm Tue, 06 Dec 2011 17:43:32 +0000 http://terrarum.net/?p=293#comment-4450 <p>Worth mentioning:</p> <p>http://search.cpan.org/~doy/Try-Tiny-0.09/lib/Try/Tiny.pm#BACKGROUND</p> Worth mentioning:

http://search.cpan.org/~doy/Try-Tiny-0.09/lib/Try/Tiny.pm#BACKGROUND

]]> Comment on Adding a Calendar Widget to BIRT by Rahul Chundawat http://terrarum.net/administration/adding-a-calendar-widget-to-birt.html#comment-3422 Rahul Chundawat Wed, 09 Nov 2011 06:43:56 +0000 http://terrarum.net/?p=255#comment-3422 <p>in a single try i added this calander to my application thanks</p> in a single try i added this calander to my application thanks

]]> Comment on Modifying Vixie Cron for Fun by Normalex http://terrarum.net/development/modifying-vixie-cron-for-fun.html#comment-2388 Normalex Mon, 03 Oct 2011 05:06:02 +0000 http://terrarum.net/wordpress/?p=11#comment-2388 <p>Joe, I almost started modifying it in the same direction, when accidentally read your article. Very nice toying. Would you like to work more on it together and make a nice complete feature? Here is what I wanted to change: * single execution queue * on each children completion log process's exec statistics like total time and memory getrusage() * additional parameters, like exclusion list of users from queuing. * we might create a global timer and handle queue in the main thread, this way there is no need to create many inherited threads. The timer will queue jobs and fork those users that should not be queued. * each job completion will trigger pop for the new one from the queue, not loop based.</p> Joe, I almost started modifying it in the same direction, when accidentally read your article. Very nice toying. Would you like to work more on it together and make a nice complete feature? Here is what I wanted to change: * single execution queue * on each children completion log process’s exec statistics like total time and memory getrusage() * additional parameters, like exclusion list of users from queuing. * we might create a global timer and handle queue in the main thread, this way there is no need to create many inherited threads. The timer will queue jobs and fork those users that should not be queued. * each job completion will trigger pop for the new one from the queue, not loop based.

]]>