Re: [Spacewalk-devel] Dropping i386 for Spacewalk Server?

2011-03-25 Thread Cliff Perry

Miroslav Suchý wrote:

On 03/25/2011 02:00 PM, Michael Gliwinski wrote:

Anyway, may I ask why?  Is it getting in the way somehow?


It cost resources. Especially for testing.



Think of the big picture matrix of OS + arch combinations.


http://spacewalk.redhat.com/yum/1.3/

Fedora 13
1) i386
2) x86_64

Fedora 14
3) i386
4) x86_64

RHEL 5
5) i386
6) x86_64

RHEL 6
7) i386
8) x86_64

To release, that is at least 8 combinations to ensure they build, 
install and function. Plus upgrade paths to each.


Dropping i386, cuts this work in half, allowing us to release 
quicker/easier (ideally).


Cliff

___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel


[Spacewalk-devel] spacewalk-service start hangs at waiting for tomcat

2011-03-25 Thread Dale Bewley
I have a brand new install on F14 x86_64 of
spacewalk-admin-1.3.9-1.fc14.

If I run /usr/sbin/spacewalk-service start it hangs at Waiting for
tomcat to be ready ... until I telnet localhost 8009. Changing the lsof
command to below seems to fix that.

--- spacewalk-service.dist  2011-01-20 09:56:49.0 -0800
+++ spacewalk-service   2011-03-25 09:33:59.017356000 -0700
@@ -52,7 +52,7 @@
 if lsof /proc  /dev/null ; then
 echo Waiting for tomcat to be ready ...
 while [ -f /var/run/$TOMCAT.pid ] ; do
-lsof -t -i @localhost:8009 -p $(cat 
/var/run/$TOMCAT.pid)  /dev/null  break
+lsof -t -i TCP:8009 -p $(cat /var/run/$TOMCAT.pid)  
/dev/null  break
 sleep 1
 done
 else


___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel


Re: [Spacewalk-devel] Dropping i386 for Spacewalk Server?

2011-03-25 Thread Michael Gliwinski
On Friday 25 Mar 2011 14:34:38 Cliff Perry wrote:
 Miroslav Suchý wrote:
  On 03/25/2011 02:00 PM, Michael Gliwinski wrote:
  Anyway, may I ask why?  Is it getting in the way somehow?
  
  It cost resources. Especially for testing.
 
 Think of the big picture matrix of OS + arch combinations.
 
 
 http://spacewalk.redhat.com/yum/1.3/
 
 Fedora 13
 1) i386
 2) x86_64
 
 Fedora 14
 3) i386
 4) x86_64
 
 RHEL 5
 5) i386
 6) x86_64
 
 RHEL 6
 7) i386
 8) x86_64
 
 To release, that is at least 8 combinations to ensure they build,
 install and function. Plus upgrade paths to each.
 
 Dropping i386, cuts this work in half, allowing us to release
 quicker/easier (ideally).

Got it.  Didn't realise you do separate testing for each combination :P

Which rel would you intend to be the first x86_64-only one? 1.4 or later?


-- 
Michael Gliwinski
Henderson Group Information Services
9-11 Hightown Avenue, Newtownabby, BT36 4RT
Phone: 028 9034 3319

**
The information in this email is confidential and may be legally privileged.  
It is intended solely for the addressee and access to the email by anyone else 
is unauthorised.
If you are not the intended recipient, any disclosure, copying, distribution or 
any action taken or omitted to be taken in reliance on it, is prohibited and 
may be unlawful.
When addressed to our clients, any opinions or advice contained in this e-mail 
are subject to the terms and conditions expressed  in the governing client 
engagement leter or contract.
If you have received this email in error please notify 
supp...@henderson-group.com

John Henderson (Holdings) Ltd
Registered office: 9 Hightown Avenue, Mallusk, County Antrim, Northern Ireland, 
BT36 4RT.
Registered in Northern Ireland
Registration Number NI010588
Vat No.: 814 6399 12
*


___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel


Re: [Spacewalk-devel] spacewalk-service start hangs at waiting for tomcat

2011-03-25 Thread Jan Pazdziora
On Fri, Mar 25, 2011 at 09:49:24AM -0700, Dale Bewley wrote:
 I have a brand new install on F14 x86_64 of
 spacewalk-admin-1.3.9-1.fc14.
 
 If I run /usr/sbin/spacewalk-service start it hangs at Waiting for
 tomcat to be ready ... until I telnet localhost 8009. Changing the lsof
 command to below seems to fix that.
 
 --- spacewalk-service.dist  2011-01-20 09:56:49.0 -0800
 +++ spacewalk-service   2011-03-25 09:33:59.017356000 -0700
 @@ -52,7 +52,7 @@
  if lsof /proc  /dev/null ; then
  echo Waiting for tomcat to be ready ...
  while [ -f /var/run/$TOMCAT.pid ] ; do
 -lsof -t -i @localhost:8009 -p $(cat 
 /var/run/$TOMCAT.pid)  /dev/null  break
 +lsof -t -i TCP:8009 -p $(cat /var/run/$TOMCAT.pid)  
 /dev/null  break
  sleep 1
  done
  else

Thank you, committed to Spacewalk git master as 
c63c29542cbe22247ab6e4bdcabd78de3a13933e.

-- 
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat

___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel


Re: [Spacewalk-devel] Dropping i386 for Spacewalk Server?

2011-03-25 Thread Luc de Louw

On 03/25/2011 03:34 PM, Cliff Perry wrote:

Miroslav Suchý wrote:

On 03/25/2011 02:00 PM, Michael Gliwinski wrote:

Anyway, may I ask why? Is it getting in the way somehow?


It cost resources. Especially for testing.



Think of the big picture matrix of OS + arch combinations.


http://spacewalk.redhat.com/yum/1.3/

Fedora 13
1) i386
2) x86_64

Fedora 14
3) i386
4) x86_64

RHEL 5
5) i386
6) x86_64

RHEL 6
7) i386
8) x86_64



People tend to re-use old hardware as test-beds. A lot of this hardware 
is still 32bit.


On the other hand, I agree with Cliff, it costs resources and thus time 
and money.


How about a compromise? Drop i386 support for Fedora and keep it for EL5 
and EL6?


The other question that arises is: How would this affect RHN-Satellite?

Thanks,

Luc


___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel