Tim Edwards wrote:
I also checked again and it looks like RHEL5.4 has the same behaviour
(ignoring amd64 arch) so I guess there's no fault in SL.
I wondered about that. I believe the naming convention for architecture
is built into rpm itself, that this would not just be a yum problem.
-Ed
Tim,
It's interesting that the rpms for the 3.05 version of syslog-ng are
correctly named with a "x86_64.rpm" extension. Perhaps you could use
those and sidestep this problem?
-Ed
Tim Edwards wrote:
These packages are from the syslog-ng site. The name seems to match
what's inside the pack
Just a heads-up, maybe it can be addressed by SL before 5.4 is
released... The update for OpenIPMI included with RHEL-5.4 added a new
and unnecessary dependency on xinetd. (It also mistakenly installs a
file into /etc/xinetd.d/ with executable bits set.) If you use
OpenIPMI, and didn't have
Greetings,
With the release of 5.3, I'm looking to improve on my first mirroring
effort, and to really understand the different trees. I've studied the
documentation on the website, and searched mail archives, but am still
confused about what's best or what's necessary. This page,
https://
Are /etc/hosts.allow and /etc/hosts.deny being used for access control
on the cluster? Perhaps the new MacBook ip is not permitted? Logs on
the cluster probably explain the failure, since that side is closing the
connection.
-Ed
Pann McCuaig wrote:
So here's the deal. One of my users just
Keith Lofstrom wrote:
...
I'm wondering if there is something needful that breaks when
I disable Avahi .
Probably not for 99% of RHEL/SL users. On servers in particular, avahi
is worse than an annoyance.
Be warned that the update to RHEL-5.3 [re-]installs and enables avahi,
apparently b
