Re: [CentOS] rpc.idmamd warnings/errors

2013-10-28 Thread Dale Dellutri
On Mon, Oct 28, 2013 at 11:57 AM, Marius Vaitiekunas 
mariusvaitieku...@gmail.com wrote:

 Hello,

 Every 15 minutes I get an error on NFSv4 server:
 rpc.idmapd[1889]: nss_getpwnam: name '0' does not map into domain
 'aaa.test.home'

 I have fully updated Centos 6.4 machine. All shares seems to be ok.

 Does anybody know, what does this error mean?


Google sends me to this bugzilla:
   https://bugzilla.redhat.com/show_bug.cgi?id=997164

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] [CEntOS] - problem with iptables

2013-10-10 Thread Dale Dellutri
On Thu, Oct 10, 2013 at 9:13 AM, Paolo De Michele
pa...@paolodemichele.itwrote:

 sorry, but now if I modify /etc/sysconfig/iptables and I add two strings,
 per example:

 output omitted
 -
 -A INPUT -s ddns.no-ip.org -p icmp -j ACCEPT
 -A INPUT -j DROP
 --
 output omitted

 and I do:

 service iptables save
 and
 restart my iptables firewall, output iptables -L is:

 -A INPUT -j DROP
 -A INPUT -s ddns.no-ip.org -p icmp -j ACCEPT

 why?


When you do
  # service iptables save
it over-writes /etc/sysconfig/iptables with the active set of
iptables, so your changes are lost.  One way to do what
you want is to modify /etc/sysconfig/iptables, then do
  # service iptables restart
This will reload the iptables from /etc/sysconfig/iptables

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] How to list openvpn clients?

2013-10-08 Thread Dale Dellutri
On Tue, Oct 8, 2013 at 10:09 AM, Timothy Murphy gayle...@eircom.net wrote:

 I'm running an openvpn server on a CentOS machine -
 that is my excuse for posting my query here -
 and I'm wondering if there is some way of finding
 all the clients (not just those connected at this moment)
 who have been registered as clients of the openvpn server?


All users should have a key in /etc/openvpn/easy-rsa/2.0/keys
So that might be one source of usernames.

Also look through /etc/openvpn/server.conf . There might be a line
which verifies usernames, for example, from the OpenVPN 2 Cookbook:
   tls-verify /etc/openvpn/cookbook/example6-5-tls-verify.sh
so you'd need to look at that file and example6-5-tls-verfiy.sh.allowed

There are other possibilities that list all allowed users.  See the
Cookbook.

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] How to list openvpn clients?

2013-10-08 Thread Dale Dellutri
On Tue, Oct 8, 2013 at 10:48 AM, Timothy Murphy gayle...@eircom.net wrote:

 John Doe wrote:

  From: Timothy Murphy gayle...@eircom.net
 
  I'm running an openvpn server on a CentOS machine -
  that is my excuse for posting my query here -
  and I'm wondering if there is some way of finding
  all the clients (not just those connected at this moment)
  who have been registered as clients of the openvpn server?
 
  Did you configure ifconfig-pool-persist...?

 Thank you very much.
 I did actually set this in server.conf,
 and the list I am seeking is in fact in the place specified.


This list will only include the usernames of those who have logged in
as openvpn clients.  There may be others who can log in but have
not as yet.  That's why I suggested looking at the keys.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Triple- or Quad-display single-card graphics solutions

2013-08-20 Thread Dale Dellutri
On Tue, Aug 20, 2013 at 1:52 PM, Glenn Eychaner geycha...@mac.com wrote:

 So, after some discussion of our new control workstations, we are
 iterating in on a solution; we are looking at a 1U short-depth SuperMicro
 SuperServer 5017R-MF with a graphics card in the PCI-Ex16 expansion slot.
 However, the display requirements have increased to 3 or more monitors for
 future expansion, so I was wondering whether anyone had any experience with
 triple- or quad-display single card solutions. Thus far, I have found two
 promising solutions:

 NVidia NVS 510 or 450


I have an nVidia 510 in a Dell Optiplex 9010, small form factor computer
using CentOS 6.4.  It works well with the standard nouveau driver.

I used to use Matrox M9140 cards, but that requires the Matrox proprietary
driver which, at the time (April 2013), had not been updated to install
on CentOS 6.4.  Perhaps by now it has.

However, I like the NVS 510 and I'll use them in the future.

Is the NVS 450 card one or two GPUs?  If two, you'll have two video cards
and you'll probably have to stitch the monitors together with xinerama.

Matrox M-series M9138 or M9148

 Both these solutions claim to have Linux support, but I was wondering if
 anyone had any experience with them in CentOS 6.4? And if there were any
 other solutions I had overlooked?

 Thanks,
 -G.
 --
 Glenn Eychaner (geycha...@lco.cl)
 Telescope Systems Programmer, Las Campanas Observatory


As an amateur astronomer, I'm a little envious.  However, I probably
wouldn't do well at 2380 m altitude.

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6 SFF motherboard or complete system

2013-06-27 Thread Dale Dellutri
On Thu, Jun 27, 2013 at 11:32 AM, Glenn Eychaner geycha...@mac.com wrote:

 I am trying to assemble or purchase a set of CentOS 6 compatible
 SFF workstations, and am finding it incredibly frustrating to do so.
 hardware.redhat.com is so slow as to be useless and provides almost no
 information about each of the 1,300 or so products listed in their
 database; clicking through them one at a time is incredibly frustrating
 (and about half of them are discontinued or out of stock when I actually go
 looking for them, like the Intel DQ series motherboards I was interested
 in).  Vendor web sites are almost no use; they trumpet their Windows 8
 compatibility all over the site, but finding information about Linux
 compatibility is next to impossible.
 My requirements aren't overwhelming; an i7 processor, four memeory
 slots preferred, dual 24 (1920x1200) monitor capability, and dual ethernet
 (or an expansion slot for a second Ethernet card).
 Anyone have any advice on how to attack this these days? I've been
 out of the hardware-purchase game on the Linux side for years, and most of
 my bookmarks no longer point anywhere useful, sadly.


I assume SFF is small form factor.  If you're willing to buy from Dell, the
Optiplex 9010 SFF has 4 memory
slots, i7 capable, 2 expansion PCIe-16 (one wired x4) slots.  You could use
one for a dual monitor graphics
card, and the other for extra ethernet ports.

You'd need to get to someone in  Dell enterprise support if you want to buy
one without Windows, or
you could just not use the Windows license.

I'm curious though: why do you need dual ethernet for a workstation?  Does
your office have
two lans?

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] 4 monitors with one graphics card and standard driver

2013-04-26 Thread Dale Dellutri
On Tue, Apr 16, 2013 at 12:52 PM, Dale Dellutri daledellu...@gmail.comwrote:

 I've just test an ATI FirePro 2460 graphics card on CentOS 6.4.  It
 connects 4 monitors.
 It worked with the standard radeon driver.  I was able to arrange the
 monitors into my
 preferred configuration (as a square array, 1 upper left, 2 lower left, 3
 lower right, 4
 upper right) simply by clicking System - Preferences - Display, and then
 moving the
 four monitor images.  This creates the file ~/.config/monitors.xml .

 Moving windows among the monitors worked smoothly.  I did not install the
 proprietary
 ATI driver;  I don't need any of its features beyond what the standard
 driver provides.

 Some details:
   Dell Optiplex 9010, Small Form Factor (SFF) case requires SFF cards.
   CentOS 6.4 fully updated as of today.
   2.6.32-358.2.1.el6.x86_64 kernel
   xorg-x11-drv-ati 6.99.99 1.el6 x86_64
   BIOS shows the board in slot 1 (the blue connector) as VGA Compatible
   lspci shows
 01:00.0 VGA compatible controller:
 Advanced Micro Devices [AMD] nee ATI Cedar [FirePro 2460]
 Kernel driver in use: radeon
   No xorg.conf was created or required.
   4 Dell 2007FP monitors, each at 1600x1200 connected via DVI.

 I used to use Matrox M9140 cards, but that requires the Matrox proprietary
 driver which has not been updated for CentOS 6.4 as of today.

 I also tested two other cards: ATI FirePro 2450 and NVidia Quadro NVS 420.
 For each of these cards, the BIOS shows the card in slot 1 as a PCI Bridge.
 lspci reports two identical video cards at 03:00.0 and 04:00.0.
 Though it's easy to set up two screens properly, xinerama would probably be
 required in an xorg.conf to get all four screens working properly.


As it turns out, the ATI FirePro 2460 works, but it's too slow with the
standard
radeon driver for our application.

I tested an NVidia NVS 510 with both the standard nouveau driver, and the
proprietary kmod-nvidia, nvidia-x11-drv rpms from elrepo.  The two gave very
similar quick response on our application, so we've decided to use the
standard
nouveau driver.

Of all the cards I've tested, the 510 is the best.

xorg-x11-drv-nouveau-1.0.1-3.el6.x86_64
lspci shows
  01:00.0 VGA compatible controller:
  NVIDIA Corporation Device 0ffd (rev a1)

The rest of the info is the same as shown above.

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] 4 monitors with one graphics card and standard driver

2013-04-16 Thread Dale Dellutri
On Tue, Apr 16, 2013 at 2:47 PM, m.r...@5-cent.us wrote:

 Dale Dellutri wrote:
  I've just test an ATI FirePro 2460 graphics card on CentOS 6.4.  It
  connects 4 monitors.
  It worked with the standard radeon driver.  I was able to arrange the
  monitors into my preferred configuration (as a square array, 1 upper
  left, 2 lower left, 3 lower right, 4 upper right) simply by clicking
  System - Preferences - Display, and then moving the
  four monitor images.  This creates the file ~/.config/monitors.xml .
 snip
  I also tested two other cards: ATI FirePro 2450 and NVidia Quadro NVS
 420.
  For each of these cards, the BIOS shows the card in slot 1 as a PCI
  Bridge.
  lspci reports two identical video cards at 03:00.0 and 04:00.0.
  Though it's easy to set up two screens properly, xinerama would probably
  be required in an xorg.conf to get all four screens working properly.

 Would you mind sending me your xorg.conf offlist? I *may* have found
 something in the one I've been handcrafting, but as my user is busy, I
 won't be able to try it out for a while, and would love to see what you
 did.


As I said, when I used the ATI FirePro 2460, there was NO xorg.conf
created or required.  I would have needed one for the ATI 2450 or the
NVidia NVS 420, but I never tried to create one.


 I'm still at the point of him having one monitor working fine, but the
 other comes up, not mirrored, but unreachable by keyboard or mouse.
 Looking at his old xorg.conf that worked with kmod-fglrx, and my own (an
 NVidia card) I realized they only have one Screen sectiuon, and a viewport
 on his (mine, of course, has twinview), so I've just edited his that way.


I suggest that you restart the machine without X (in run level 3), then as
root
do:
  # X -configure
which will write a new xorg.conf.new in the current directory.

But are you sure the problem is in the xorg.conf?  What does System -
Preferences - Display show?

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] How to determine why a server is not responding

2013-04-11 Thread Dale Dellutri
On Thu, Apr 11, 2013 at 10:36 AM, nan del bosc nandelb...@gmail.com wrote:

 Hi to all!

 We're using CentOS 5.5 64bits for our Plesk 11.

 This week we had the following problem 3 times...

 Suddenly, the server stops responding in all services (SSH, Apache,
 Postfix, ...) but ping works!

 After wait a few minutes (or 2 hours some times) the server continues
 unresponsive until we reboot. After reboot we search on /var/log/messages
 but cannot find useful information...

...

 What can we do? what can we test?


Are you running  sysstat / sar ?

Perhaps the sa / sar database that's left after reboot can show if some
resource
was over capacity.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] How to determine why a server is not responding

2013-04-11 Thread Dale Dellutri
On Thu, Apr 11, 2013 at 10:59 AM, nan del bosc nandelb...@gmail.com wrote:

 ...
 This is a Virtual Server from 1and1, I cannot access the BIOS...

 any other idea?


If this is a virtual server, the actual hardware may just be running
other virtual servers and you're not getting any resources.  If that's
true, nothing you do from your server will help you.  You'll need to
get system stats from the actual hardware provider.

Sounds like the hardware is over-committed.  Do you have some
kind of service guarantee?

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] floppy drives

2013-04-08 Thread Dale Dellutri
On Sun, Apr 7, 2013 at 2:45 PM, mark m.r...@5-cent.us wrote:

 Yes, really. I've got hundreds of the damn things here at home, and I
 want to go through them and get rid of them all.

 But... to do that I want to read them. I have both a 5.25 and a 3.5
 drive, both are plugged in, but in the BIOS, all I see is the 3.5.
 Fine, I figure I'll take care of those.

 Nope. I see /dev/fd0 once I've booted up, but neither konqueror nor
 mount nor fdisk works - the latter telling me that /dev/fd0 is not a
 valid block device. After some googling, I tried modprobe floppy, which
 installed it, but still no joy.

 Anyone have a clue?


To debug this, I'd do the following:

1. Remove both USB plugs (I assume that these floppies are USB connected)
2. Reboot
3. Plug just one in, then do
  lsusb
and get the end of /var/log/messages
One of these might tell you where the floppy is connected in /dev.  It
might not
be /dev/fd0
4. If it doesn't show up immediately, try putting in a floppy disk and do 3
again.
5. If it doesn't show up again, then it's probably dead.
6. If it does show, perhaps at /dev/sdb1, then create a file .mtoolsrc:
  # USB drive
  drive u: file=/dev/sdb1
Then do
  mdir u:

Of course, it will probably show up at /dev/fdn.

Just my pre-tax 2 cents.

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Does CentOS support dual graphics cards with 2 monitors each?

2013-04-06 Thread Dale Dellutri
On Thu, Mar 28, 2013 at 5:08 PM, Alfred von Campe alf...@von-campe.comwrote:

 I have a user who wants to have 4 monitors attached to his CentOS 6.4
 system.  I know that you
 can't use both on-board video and a PCI video card at the same time, but
 what about two PCI
 video cards?  The system seems to recognize them as shown by the lspci -v
 output below, but
 I can't get Xorg to use the second card.  Has anyone done this?  If so,
 what is the trick to
 get it to work?


I previously suggested the Matrox M9140 with the matrox proprietary driver
(m9x),
but the current one does not support the Xorg server 1.13 which is the
current
server for CentOS 6.4.  Until they update the driver package, it can't be
installed
on a CentOS 6.4 system.

In the next few weeks I'm going to test some other graphic cards that have
four
monitor connections on one card:
  ATI FirePro 2460 Multiview
  NVidia Quadro NVS 420
  NVidia Quadro NVS 510
I hope that they will work with the open source driver (radeon or nouveau).

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Does CentOS support dual graphics cards with 2 monitors each?

2013-03-30 Thread Dale Dellutri
On Fri, Mar 29, 2013 at 9:07 AM, Alfred von Campe alf...@von-campe.comwrote:

 On Mar 28, 2013, at 23:01, Dale Dellutri wrote:

  What does xrandr report?

 Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
 DVI-I-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis)
 518mm x 3200mm
1920x1080  59.9*+
1600x1200  60.0
1680x1050  60.0
1280x1024  75.0 60.0
1440x900   59.9
1280x960   60.0
1280x800   59.8
1152x864   75.0
1024x768   75.1 70.1 60.0
832x62474.6
800x60072.2 75.0 60.3 56.2
640x48072.8 75.0 66.7 60.0
720x40070.1
 HDMI-1 disconnected (normal left inverted right x axis y axis)
 VGA-1 disconnected (normal left inverted right x axis y axis)

  (I've used Matrox M9140 and the matrox prop driver.  That combo provides
  quad monitors with one graphics card.)

 That looks promising; I will have to check it out.  Did you use this on
 Linux,
 and specifically CentOS?


Yes.  Four of these on older Fedora releases, and one on CentOS 6.3.

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Does CentOS support dual graphics cards with 2 monitors each?

2013-03-28 Thread Dale Dellutri
On Thu, Mar 28, 2013 at 5:08 PM, Alfred von Campe alf...@von-campe.com wrote:
 I have a user who wants to have 4 monitors attached to his CentOS 6.4 system. 
  I know that you
 can't use both on-board video and a PCI video card at the same time, but what 
 about two PCI
 video cards?  The system seems to recognize them as shown by the lspci -v 
 output below, but
 I can't get Xorg to use the second card.  Has anyone done this?  If so, what 
 is the trick to
 get it to work?

What does xrandr report?

(I've used Matrox M9140 and the matrox prop driver.  That combo provides
quad monitors with one graphics card.)

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 - unsupported video hardware

2013-03-06 Thread Dale Dellutri
On Wed, Mar 6, 2013 at 2:31 PM, Robert Moskowitz r...@htt-consult.com wrote:

 On 03/06/2013 02:51 PM, Craig White wrote:
 On Mar 6, 2013, at 12:24 PM, Robert Moskowitz wrote:

 I pulled one of my old OQO model 2 out of the junk bin and installed
 Centos 6.3 over Centos 5.3.

 The internal video does not work in graphics mode (text works fine),
 though a monitor attacked to the VGA port works fine.  Although my
 intension is to use this as a portable test server, it would be nice if
 the video was available.  How might I go about figuring out the Xorg
 magic to get it working?

When you say internal video does not work, what do you mean?
Is the laptop screen black, garbled, flickering, unresponsive?

If black, did you try startx for the command line?

Are there any errors (EE) or warnings (WW) in /var/log/Xorg.0.log?

Anything in /var/log/messages or dmesg?

What is the output of lspci | grep VGA?

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.3 - unsupported video hardware

2013-03-06 Thread Dale Dellutri
On Wed, Mar 6, 2013 at 3:03 PM, Robert Moskowitz r...@htt-consult.com wrote:

 On 03/06/2013 03:47 PM, Dale Dellutri wrote:

 On Wed, Mar 6, 2013 at 2:31 PM, Robert Moskowitz r...@htt-consult.com
 wrote:

 On 03/06/2013 02:51 PM, Craig White wrote:

 On Mar 6, 2013, at 12:24 PM, Robert Moskowitz wrote:

 I pulled one of my old OQO model 2 out of the junk bin and installed
 Centos 6.3 over Centos 5.3.

 The internal video does not work in graphics mode (text works fine),
 though a monitor attacked to the VGA port works fine.  Although my
 intension is to use this as a portable test server, it would be nice if
 the video was available.  How might I go about figuring out the Xorg
 magic to get it working?

 When you say internal video does not work, what do you mean?
 Is the laptop screen black, garbled, flickering, unresponsive?


 Scrolling flickering, blue and white image.


 If black, did you try startx for the command line?


 Have not switched to init 3 to try.


 Are there any errors (EE) or warnings (WW) in /var/log/Xorg.0.log?


 (EE) open /dev/fb0: No such device

 (WW) Falling back to old probe method for vesa
 (WW) Falling back to old probe method for fbdev
 (WW) CHROME(0): Manufacturer plainly copied main PCI IDs to subsystem/card
 IDs.
 (WW) CHROME(0): Unable to estimate virtual size
 (WW) CHROME(0): [XvMC] XvMC is not supported on this chipset
 (WW) Lid Switch: Don't know how to use device


 Anything in /var/log/messages or dmesg?


 what would I search for?

Error messages pertaining to the video controller.




 What is the output of lspci | grep VGA?

 01:00.0 VGA compatible controller: VIA Technologies, Inc. CX700/VX700 [S3
 UniChrome Pro] (rev 03)

Use the info in this line (VIA CX700 VX700 or UniChrome Pro) to do a
google search.  Add linux to the search terms to see what driver you need.


 Hope this points somewhere.





-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Off-Topic: Low Power Hardware

2013-01-11 Thread Dale Dellutri
On Fri, Jan 11, 2013 at 8:55 AM, SilverTip257 silvertip...@gmail.com wrote:
 Hello,

 I'm slightly off-topic here, but it is somewhat CentOS related!

 I'm in search of some hardware that consumes a low amount of power for use
 as a test-bed for Linux, various coding projects, and LAN services.

Google fanless pc or fanless computer.

Fanless systems tend to be low power consumption, or low power
systems tend to be manufactured by the same companies that
make fanless.

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 as Firewall/Router

2013-01-04 Thread Dale Dellutri
On Fri, Jan 4, 2013 at 11:01 AM, Tim Evans tkev...@tkevans.com wrote:
 I'm replacing an ancient Solaris 'ipf' firewall/router with a brand new
 CentOS 6.3 system.  In the olden days, I successfully used the attached
 iptables script (as /etc/rc.local) on Red Hat 5.x systems, but this doesn't
 seem to be quite working on the new system.

 Specifically, while it seems to be routing ok, you cannot connect to
 anything on the inside net (e.g., with ssh or a browser) and cannot connect
 to the system with ssh or anything else from elsewhere on the inside net.
 Yet arp shows this system active.

 Is there obsolete stuff here, and/or anything missing that would cause this?

You found the error, but I have a question about running this in rc.local.

Aren't you opening a very short time security hole by running this from
rc.local?  Service network starts up early in the startup sequence
(/etc/rc.d/rc3.d/S10network), and rc.local is at the very end.

Wouldn't it be better to run the iptables rules once, then do:
  service iptables save
This way, iptables rules would be in place (S08iptables) before
netowrk startup.

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6.3 as Firewall/Router

2013-01-04 Thread Dale Dellutri
On Fri, Jan 4, 2013 at 3:04 PM, Tim Evans tkev...@tkevans.com wrote:
 On 01/04/2013 03:03 PM, Dale Dellutri wrote:
 On Fri, Jan 4, 2013 at 11:01 AM, Tim Evans tkev...@tkevans.com wrote:
 I'm replacing an ancient Solaris 'ipf' firewall/router with a brand new
 CentOS 6.3 system.  In the olden days, I successfully used the attached
 iptables script (as /etc/rc.local) on Red Hat 5.x systems, but this doesn't
 seem to be quite working on the new system.

 Specifically, while it seems to be routing ok, you cannot connect to
 anything on the inside net (e.g., with ssh or a browser) and cannot connect
 to the system with ssh or anything else from elsewhere on the inside net.
 Yet arp shows this system active.

 Is there obsolete stuff here, and/or anything missing that would cause this?

 You found the error, but I have a question about running this in rc.local.

 Aren't you opening a very short time security hole by running this from
 rc.local?  Service network starts up early in the startup sequence
 (/etc/rc.d/rc3.d/S10network), and rc.local is at the very end.

 Wouldn't it be better to run the iptables rules once, then do:
service iptables save
 This way, iptables rules would be in place (S08iptables) before
 netowrk startup.


 Thanks, Dale.  I'm trying to remember why I did it this way (nearly 10
 years ago, when I did this first.)  Seems it had to do with not turning
 on routing until the very end (instead of enabling it in
 /etc/sysctl.conf), relying on the out-of-the-box iptables rules in the
 interim (iptables still starts normally). This script overlays its
 rules, then turns on NAT and routing.

Do the out-of-the-box iptables rules allow all entry to the system?

What's in /etc/sysconfig/iptables ?

I understand that the script does more than simply set iptables rules.
However, you could set the rules you want, then just turn on
NAT and routing in rc.local.

I'm not trying to criticize, just curious.

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Ethernet puzzle

2012-12-28 Thread Dale Dellutri
On Fri, Dec 28, 2012 at 12:56 PM, Ashley M. Kirchner ash...@pcraft.com wrote:
 But it is.  The MAC address on the motherboard port is NOT the same as the
 mystery device.  And it DOES match one of the entries in udev's rules, and
 it's operational right now as eth0 (as it should be.)  However, the mystery
 MAC address that's listed in udev's rules matches nothing in either lshw or
 lspci.

 Remember, udev's rules lists FOUR devices.  There are only THREE.

What does the BIOS say about ethernet devices?

Does the motherboard have a management interface card with its own
ethernet port, perhaps potential but not actually installed?

Is there a fiber-optics connector on the system which is coming up as
an ethernet port?

Is one of the cards old enough to still have a separate BNC connector?

 On Fri, Dec 28, 2012 at 11:36 AM, Frank Cox 
 thea...@melvilletheatre.comwrote:

 On Fri, 28 Dec 2012 11:21:22 -0700
 Ashley M. Kirchner wrote:

  Yeah, rpmforge or repoforge.  But, I'm looking for what exactly?  It only
  lists a single ethernet port (the built-in one).

 That's what you're looking for.  Now you know that the mysterious device
 isn't
 something that you didn't know aobout on the motherboard.

 --
 MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
 www.creekfm.com - FIFTY THOUSAND WATTS of POW WOW POWER!
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos


 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos



-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Basic KVM networking question

2012-09-10 Thread Dale Dellutri
On Mon, Sep 10, 2012 at 11:34 AM, Steve Thompson s...@vgersoft.com wrote:

 A CentOS 6.3 box (host) runs several KVM virtual machines, each of which
 has two interfaces attached to the two bridges br1 and br2 (and each thus
 has two IP's; one on 192.168.0.0/22 and one on 192.168.4.0/22);
 net.ipv4.ip_forward on the host is 1. Simplified diagram:

 host
   +---+
   |   |
net1 = 192.168.0.0/22  |   |  net2 = 192.168.4.0/22
---+  br1  br2 +-
|  |   ||
|  |   ||
Client A   +---+Client B
 (hosts KVM1, KVM2, etc)

 Each client uses the bridge's IP address on the same side as default
 gateway. Client A can successfully ping or ssh (for example) to a KVM
 machine by IP address by using the KVM machine's net1 IP address. Client B
 can likewise communicate using the KVM machine's net2 IP address. However,
 neither client can communicate by using the address on the opposing
 segment (eg, Client A using KVM1_net2_IP); I can see from tcpdump that the
 packets are received by the virtual machine but no reply is ever made. Any
 clue?

Routing problem?  What are the response to each of the commands below on
all five systems: host, Client A and B, KVM1 and 2:

# ip addr show
# ip route show

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Basic KVM networking question

2012-09-10 Thread Dale Dellutri
On Mon, Sep 10, 2012 at 12:37 PM, Steve Thompson s...@vgersoft.com wrote:
 On Mon, 10 Sep 2012, Dale Dellutri wrote:

 Routing problem?

 Not that I can see, but here is the info (omitting interfaces that are not
 up). I included on one KVM since the problem is common to the others, and
 they are all set up the same way.

 On the host:

 3: em2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen 1000
  link/ether 84:2b:2b:47:e8:7d brd ff:ff:ff:ff:ff:ff
  inet6 fe80::862b:2bff:fe47:e87d/64 scope link
 valid_lft forever preferred_lft forever
 4: p1p1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen 
 1000
  link/ether 00:1b:21:6f:2b:4c brd ff:ff:ff:ff:ff:ff
  inet6 fe80::21b:21ff:fe6f:2b4c/64 scope link
 valid_lft forever preferred_lft forever
 7: br1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN
  link/ether 84:2b:2b:47:e8:7d brd ff:ff:ff:ff:ff:ff
  inet 192.168.4.2/22 brd 192.168.7.255 scope global br1
  inet6 fe80::862b:2bff:fe47:e87d/64 scope link
 valid_lft forever preferred_lft forever
 8: br2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN
  link/ether 00:1b:21:6f:2b:4c brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.2/22 brd 192.168.3.255 scope global br2
  inet6 fe80::21b:21ff:fe6f:2b4c/64 scope link
 valid_lft forever preferred_lft forever
 10: virbr0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state 
 UNKNOWN
  link/ether 52:54:00:9d:ad:f7 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
 11: virbr0-nic: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN qlen 500
  link/ether 52:54:00:9d:ad:f7 brd ff:ff:ff:ff:ff:ff
 12: vnet0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state 
 UNKNOWN qlen 500
  link/ether fe:54:00:13:73:28 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::fc54:ff:fe13:7328/64 scope link
 valid_lft forever preferred_lft forever
 13: vnet1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state 
 UNKNOWN qlen 500
  link/ether fe:54:00:12:99:dd brd ff:ff:ff:ff:ff:ff
  inet6 fe80::fc54:ff:fe12:99dd/64 scope link
 valid_lft forever preferred_lft forever
 14: vnet2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state 
 UNKNOWN qlen 500
  link/ether fe:54:00:72:f5:33 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::fc54:ff:fe72:f533/64 scope link
 valid_lft forever preferred_lft forever

 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
 192.168.4.0/22 dev br1  proto kernel  scope link  src 192.168.4.2
 192.168.0.0/22 dev br2  proto kernel  scope link  src 192.168.0.2
 default via 192.168.0.1 dev br2

 On KVM1:

 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP 
 qlen 1000
  link/ether 52:54:00:13:73:28 brd ff:ff:ff:ff:ff:ff
  inet 192.168.3.253/22 brd 192.168.3.255 scope global eth0
  inet6 fe80::5054:ff:fe13:7328/64 scope link
 valid_lft forever preferred_lft forever
 3: eth1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP 
 qlen 1000
  link/ether 52:54:00:12:99:dd brd ff:ff:ff:ff:ff:ff
  inet 192.168.7.253/22 brd 192.168.7.255 scope global eth1
  inet6 fe80::5054:ff:fe12:99dd/64 scope link
 valid_lft forever preferred_lft forever

 192.168.4.0/22 dev eth1  proto kernel  scope link  src 192.168.7.253
 192.168.0.0/22 dev eth0  proto kernel  scope link  src 192.168.3.253
 default via 192.168.0.1 dev eth0

 On client A:

 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP 
 qlen 1000
  link/ether 00:14:22:27:9b:51 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.172/22 brd 192.168.3.255 scope global eth0
  inet6 fe80::214:22ff:fe27:9b51/64 scope link
 valid_lft forever preferred_lft forever

 192.168.0.0/22 dev eth0  proto kernel  scope link  src 192.168.0.172
 default via 192.168.0.2 dev eth0

 On client B:

 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast qlen 1000
  link/ether 00:19:b9:c7:23:ad brd ff:ff:ff:ff:ff:ff
  inet 192.168.5.241/22 brd 192.168.7.255 scope global eth0
  inet6 fe80::219:b9ff:fec7:23ad/64 scope link
 valid_lft forever preferred_lft forever

 192.168.4.0/22 dev eth0  proto kernel  scope link  src 192.168.5.241
 default via 192.168.4.1 dev eth0

This looks like it should work for Client A, but maybe not for Client B (see
below).  So maybe it's a firewall problem (iptables chain FORWARD) on the
host?

Client B's default route is 192.168.4.1.  This address is not on the host.
Did you mean to use .2?  If not, is .1 aware of the routing to the
192.168.0.0/22 network?

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] System crash -- no clue why

2012-07-10 Thread Dale Dellutri
On Tue, Jul 10, 2012 at 10:36 AM, Michael Eager ea...@eagerm.com wrote:
 Hi --

 My CentOS 5.8 server crashed, leaving no clue why.  The
 last entry in /var/log/messages is a dhcpd notice around
 4:00am, followed by the restart message when I rebooted.
 The only clue that I have is that the fan was running full
 speed when I restarted it.  The fan slowed to normal speed.

 Any ideas what I can do to find out the cause?

Power failure?

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Failing Network card

2012-06-20 Thread Dale Dellutri
On Wed, Jun 20, 2012 at 12:18 PM, Chris Beattie cbeat...@geninfo.com wrote:
 On 6/20/2012 9:34 AM, Gregory P. Ennis wrote:

 I have been chasing a problem with a pci-e TrendNet(TEG-ECTX) gigabit
 card.  After adding the card to a machine with a new Centos 6.2 install
 and naming it 'eth4' it works well for 6 to 12 hours and then fails.

 Try moving the network card to a new slot, especially if you can swap
 the network card with another card which is known to work.  Also, try
 swapping the card into a spare server.

 If the problem follows the network card, then the card is probably bad.
  If a known-good card misbehaves in the slot where you previously had
 the network card, then the slot may be bad as well.

Or it could mean that the PCI-e slots are not providing enough power
for this card, or the slots are specialized to run only certain types of
cards.  What motherboard does the OP have?

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] upgrade issue

2012-04-13 Thread Dale Dellutri
On Fri, Apr 13, 2012 at 12:19 PM, Paul A ra...@meganet.net wrote:
 I have an old dell 2450 that was running kernel 2.6.18-308.1.1.el5 I then
 upgraded it via yum to 2.6.18-308.1.1.el5. Now when the server boots to the
 new kernel, 2.6.18-308.1.1.el5 it hangs on starting iSCSI and the weird
 thing is when I tried to switch back to the older 2.6.18-308.1.1.el5 kernel
 it works fine but the network script fails to start. I'm not really sure
 what I should do, if someone can give me an idea on what I need to do to fix
 the iSCSId issue on the new kernel or revert back to the old kernel and fix
 the network issue. The odd thing is both kernel load the e100 network driver
 but on the older kernel I can get the network script to start.

 I would appreciate some help.

Do you need iscsi?  If not, boot with the old kernel, and disable iscsi

# chkconfig --list | grep iscsi
(will probably show iscsi and iscsid)

Then
# chkconfig iscsi off
# chkconfig iscsid off

Then reboot with the new kernel.

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] upgrade issue

2012-04-13 Thread Dale Dellutri
On Fri, Apr 13, 2012 at 2:02 PM, Paul A ra...@meganet.net wrote:
 I'm running Raid with scsi disks so I'm assuming it's needed correct?

iSCSI is for carrying SCSI command s and data over IP networks.
I don't know how your RAID is set up, but it isn't normally done with
iSCSI.  See, for example:
  http://en.wikipedia.org/wiki/ISCSI
versus
  http://en.wikipedia.org/wiki/RAID

 -Original Message-
 From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
 Of Dale Dellutri
 Sent: Friday, April 13, 2012 1:32 PM
 To: CentOS mailing list
 Subject: Re: [CentOS] upgrade issue

 On Fri, Apr 13, 2012 at 12:19 PM, Paul A ra...@meganet.net wrote:
 I have an old dell 2450 that was running kernel 2.6.18-308.1.1.el5 I
 then upgraded it via yum to 2.6.18-308.1.1.el5. Now when the server
 boots to the new kernel, 2.6.18-308.1.1.el5 it hangs on starting
 iSCSI and the weird thing is when I tried to switch back to the older
 2.6.18-308.1.1.el5 kernel it works fine but the network script fails
 to start. I'm not really sure what I should do, if someone can give me
 an idea on what I need to do to fix the iSCSId issue on the new kernel
 or revert back to the old kernel and fix the network issue. The odd
 thing is both kernel load the e100 network driver but on the older kernel
 I can get the network script to start.

 I would appreciate some help.

 Do you need iscsi?  If not, boot with the old kernel, and disable iscsi

 # chkconfig --list | grep iscsi
 (will probably show iscsi and iscsid)

 Then
 # chkconfig iscsi off
 # chkconfig iscsid off

 Then reboot with the new kernel.

 --
 Dale Dellutri
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos



-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] upgrade issue

2012-04-13 Thread Dale Dellutri
On Fri, Apr 13, 2012 at 2:25 PM, Paul A ra...@meganet.net wrote:
 Dale, I disabled it and the server came up but im seeing all sorts of kernel
 errors when its disabled ( see below ). If this can't be fixed I would
 really like to boot the previous kernel however the network script won't
 start. Im not really sure how upgrading the kernel caused the network to
 stop working on the previous kernel.

Nor do I know how upgrading could do that.  What other changes have
you made?

Two questions:
1. Is the previous kernel (with iscsi and iscsid enabled) giving any error
messages in the log when you attempt to boot it.
2. Is your RAID using local disks or disks on an iscsi target device?
If local, iscsi shouldn't have anything to do with RAID.  If on an iscsi
target device, then you need iscsi and iscsid enabled.

I'd suggest re-enabling iscsi and iscsid and try to solve the network problem
with the old kernel.

 -Original Message-
 From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
 Of Dale Dellutri
 Sent: Friday, April 13, 2012 3:07 PM
 To: CentOS mailing list
 Subject: Re: [CentOS] upgrade issue

 On Fri, Apr 13, 2012 at 2:02 PM, Paul A ra...@meganet.net wrote:
 I'm running Raid with scsi disks so I'm assuming it's needed correct?

 iSCSI is for carrying SCSI command s and data over IP networks.
 I don't know how your RAID is set up, but it isn't normally done with iSCSI.
 See, for example:
  http://en.wikipedia.org/wiki/ISCSI
 versus
  http://en.wikipedia.org/wiki/RAID

 -Original Message-
 From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
 Behalf Of Dale Dellutri
 Sent: Friday, April 13, 2012 1:32 PM
 To: CentOS mailing list
 Subject: Re: [CentOS] upgrade issue

 On Fri, Apr 13, 2012 at 12:19 PM, Paul A ra...@meganet.net wrote:
 I have an old dell 2450 that was running kernel 2.6.18-308.1.1.el5 I
 then upgraded it via yum to 2.6.18-308.1.1.el5. Now when the server
 boots to the new kernel, 2.6.18-308.1.1.el5 it hangs on starting
 iSCSI and the weird thing is when I tried to switch back to the
 older
 2.6.18-308.1.1.el5 kernel it works fine but the network script fails
 to start. I'm not really sure what I should do, if someone can give
 me an idea on what I need to do to fix the iSCSId issue on the new
 kernel or revert back to the old kernel and fix the network issue.
 The odd thing is both kernel load the e100 network driver but on the
 older kernel
 I can get the network script to start.

 I would appreciate some help.

 Do you need iscsi?  If not, boot with the old kernel, and disable
 iscsi

 # chkconfig --list | grep iscsi
 (will probably show iscsi and iscsid)

 Then
 # chkconfig iscsi off
 # chkconfig iscsid off

 Then reboot with the new kernel.

 --
 Dale Dellutri
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos



 --
 Dale Dellutri
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos



-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] Where is source address info of a route kept?

2011-11-16 Thread Dale Dellutri
I have an ethernet device in my lan with a primary address 192.168.5.205
and a secondary address .217.  I added the secondary address after network
startup established the primary address by an ip addr add command:

# ip addr add 192.168.5.217/24 broadcast 192.168.5.255 dev eth0

# ip addr show
...
2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 78:2b:cb:23:21:4c brd ff:ff:ff:ff:ff:ff
inet 192.168.5.205/24 brd 192.168.5.255 scope global eth0
inet 192.168.5.217/24 brd 192.168.5.255 scope global secondary eth0
inet6 fe80::7a2b:cbff:fe23:214c/64 scope link
   valid_lft forever preferred_lft forever
...

Then I add a new route via a network gateway but I want the route to use
the secondary address as a source.

# ip route add 11.11.11.11 via 192.168.5.148 src 192.168.5.217

And the ip route show command shows that it knows the source.

# ip route show
11.11.11.11 via 192.168.5.148 dev eth0  src 192.168.5.217

But where is the source address kept?  If I look at /proc/net/route,
it shows the route (0B0B0B0B = 11.11.11.11), but not the source
address.

# cat /proc/net/route
Iface Destination Gateway  Flags RefCnt Use Metric Mask MTU Window IRTT
eth0  0B0B0B0B9405A8C0 0007  0  0   0   0   0  0
...

Where is the source address kept?

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] pgadmin3 missing dependencies

2011-11-15 Thread Dale Dellutri
On Tue, Nov 15, 2011 at 2:46 PM, Alan McKay alan.mc...@gmail.com wrote:
 I searched the list archives and I found one answer to this which
 suggested I should install the PG yum repos.   I don't like that
 answer for reasons which follow.

 I'm running Centos 6.0 freshly installed, and I've decided that with
 this box I'm sticking as much as possible to just the CentOS repos
 that go with that release.  I figure in particular I do not need any
 PG features above what are offered in release 8.4 that comes from the
 CentOS repos, so I don't really want to install PG repos.

 But first of all I do not even see pgadmin3 in the CentOS repos
 anywhere.   Am I correct that in order to get this tool I need to get
 it from the PG repo?  It seems odd to me that CentOS would not have it
 but stranger things have happened.

 So I pull down the pgadmin3 RPM manually, and try to do a manual
 install only to find that a number of RPMs are missing and required.
 I guess at this point I could just install the repo for PG to yum it
 all, but I'd like to know what RPMs are required and I am unable to
 figure that out.  I figured out at least that I need libxslt, but
 cannot figure out from the below output what other RPMs are needed
 and where I get them.  libxslt I got from 6.0 yum repos.

 [root@cc-bc4d99dffae2 ~]# rpm --install pgadmin3-1.12.2-1.rhel6.i686.rpm

Instead of rpm, use
  yum install pgadmin3-1.12.2-1.rhel6.i686.rpm
assuming the rpm is in the present working directory.
Yum will note the dependencies and download them if they
are available in your currently enabled repos.  If not, you'll
have to install and enable other repos.

You might need:
  yum --nogpgcheck install pgadmin3-1.12.2-1.rhel6.i686.rpm

 warning: pgadmin3-1.12.2-1.rhel6.i686.rpm: Header V4 DSA/SHA1
 Signature, key ID 442df0f8: NOKEY
 error: Failed dependencies:
        libwx_baseu-2.8.so.0 is needed by pgadmin3-1.12.2-1.rhel6.i686
        libwx_baseu-2.8.so.0(WXU_2.8) is needed by pgadmin3-1.12.2-1.rhel6.i686
        libwx_baseu-2.8.so.0(WXU_2.8.5) is needed by 
 pgadmin3-1.12.2-1.rhel6.i686
        libwx_baseu_net-2.8.so.0 is needed by pgadmin3-1.12.2-1.rhel6.i686
        libwx_baseu_net-2.8.so.0(WXU_2.8) is needed by 
 pgadmin3-1.12.2-1.rhel6.i686
        libwx_baseu_xml-2.8.so.0 is needed by pgadmin3-1.12.2-1.rhel6.i686
        libwx_baseu_xml-2.8.so.0(WXU_2.8) is needed by 
 pgadmin3-1.12.2-1.rhel6.i686
        libwx_gtk2u_adv-2.8.so.0 is needed by pgadmin3-1.12.2-1.rhel6.i686
        libwx_gtk2u_adv-2.8.so.0(WXU_2.8) is needed by 
 pgadmin3-1.12.2-1.rhel6.i686
        libwx_gtk2u_aui-2.8.so.0 is needed by pgadmin3-1.12.2-1.rhel6.i686
        libwx_gtk2u_aui-2.8.so.0(WXU_2.8) is needed by 
 pgadmin3-1.12.2-1.rhel6.i686
        libwx_gtk2u_core-2.8.so.0 is needed by pgadmin3-1.12.2-1.rhel6.i686
        libwx_gtk2u_core-2.8.so.0(WXU_2.8) is needed by 
 pgadmin3-1.12.2-1.rhel6.i686
        libwx_gtk2u_html-2.8.so.0 is needed by pgadmin3-1.12.2-1.rhel6.i686
        libwx_gtk2u_html-2.8.so.0(WXU_2.8) is needed by 
 pgadmin3-1.12.2-1.rhel6.i686
        libwx_gtk2u_ogl-2.8.so.0 is needed by pgadmin3-1.12.2-1.rhel6.i686
        libwx_gtk2u_ogl-2.8.so.0(WXU_2.8) is needed by 
 pgadmin3-1.12.2-1.rhel6.i686
        libwx_gtk2u_qa-2.8.so.0 is needed by pgadmin3-1.12.2-1.rhel6.i686
        libwx_gtk2u_richtext-2.8.so.0 is needed by pgadmin3-1.12.2-1.rhel6.i686
        libwx_gtk2u_stc-2.8.so.0 is needed by pgadmin3-1.12.2-1.rhel6.i686
        libwx_gtk2u_stc-2.8.so.0(WXU_2.8) is needed by 
 pgadmin3-1.12.2-1.rhel6.i686
        libwx_gtk2u_xrc-2.8.so.0 is needed by pgadmin3-1.12.2-1.rhel6.i686
        libwx_gtk2u_xrc-2.8.so.0(WXU_2.8) is needed by 
 pgadmin3-1.12.2-1.rhel6.i686
        wxGTK is needed by pgadmin3-1.12.2-1.rhel6.i686
 [root@cc-bc4d99dffae2 ~]#


 --
 “Don't eat anything you've ever seen advertised on TV”
          - Michael Pollan, author of In Defense of Food
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos




-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] pgadmin3 missing dependencies

2011-11-15 Thread Dale Dellutri
On Tue, Nov 15, 2011 at 4:04 PM, John R Pierce pie...@hogranch.com wrote:
 On 11/15/11 1:12 PM, Alan McKay wrote:
 Thanks for the quick reponses guys - tried that and it still does not
 work which tells me I need those PG repos afterall, I guess.   No
 biggie.  My desired for a clean system has been smashed, but I'll
 live :-)

 did yum say what specific packages it needed ?  I'm pretty sure you have
 to use 'yum localinstall' to install from an rpm file, and not just
 'install'...

from man yum:
  * localinstall rpmfile1 [rpmfile2] [...]
 (maintained for legacy reasons only - use install)
and further:
  If the name is a file, then install works like localinstall.

Actually, I've been using localinstall, but I started to use
install a few months ago.

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Which file system to use for a USB backup

2011-03-09 Thread Dale Dellutri
On Wed, Mar 9, 2011 at 5:51 PM, Todd Cary t...@aristesoftware.com wrote:
 Les -

 A lot of the data needs to be moved in time to servers in other
 organizations (e.g. Rotary) or the data may be used as a
 repository for someone with just a notebook computer who would
 plug the HD into the computer.  This is not my main data backup;
 I use rsync for that.
 http://www.toddcary.com/rotary/ is one example of data that needs
 to be shared.

 Can rsync take ext4 data and copy it to a fat32 drive?

Yes, but you have to give up permissions and the modify time on a FAT32 is only
accurate to 2 seconds.  To rsync from an ext3/4 directory to a
plugged-in USB drive
use something like:

  rsync -av --no-p --modify-window=1 srcdir/ /media/volname/targetdir/

and you might need --delete.

More info at man rsync.

Another possibility: always use tar, and put something like a Windows version of
7zip executable on the USB drive as well as the data.  That way, Windows users
can get the files out the tar archive.

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] using a Laptop as a KVM console?

2010-10-13 Thread Dale Dellutri
On Wed, Oct 13, 2010 at 12:31 PM, Rudi Ahlers r...@softdux.com wrote:

 Hi all,

 Has anyone seen something like this before:

 I want to use a laptop as a KVM console. Basically when a technician
 goes to one of our datacentres, or clients he has to look for a free
 LCD, keyboard  mouse to connect to a server (no network access,
 reinstall, troubleshoot failed kernel / HDD, etc). And then hopefully
 there's an open power socker in that cabinet.

 So I'm thinking why not just use a laptop instead? It already has an
 LCD, keyboard, mouse  power. Surely someone has, or may still, build
 something that could connect to the laptop's USB port(s) and then to
 the server's VGA  USB / PS2 ports, then act as a KVM?

 --
 Kind Regards
 Rudi Ahlers
 SoftDux

 Website: http://www.SoftDux.com
 Technical Blog: http://Blog.SoftDux.com
 Office: 087 805 9573
 Cell: 082 554 7532


Your request inspired me to try a google search:

  linux laptop as kvm console

Apparently there is such a device (URL may wrap):


http://us.startech.com/product/NOTECONS01-Portable-USB-PS-2-KVM-Console-Adapter-for-Notebook-PCs

It may require a Windows XP  or Mac laptop, but at least one page says it
works on Linux, too.  You could try to contact StarTech, I guess.

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] force b/w printing

2010-08-03 Thread Dale Dellutri
On Tue, Aug 3, 2010 at 3:48 AM, Janez Kosmrlj postnali...@googlemail.comwrote:

 Has anyone an idea, how to force users to print b/w on a color printer.
 We are in the process to deploy color printers to some of our offices where
 they use centos 5.5 as their OS. They need the printers to print some
 advertisement material. But for everything else, they don't need it. And
 because of the costs of the color printing we would like to force them to
 use B/W where not explicitly necessary. Is there a way to force  a printer
 driver to be just B/W even if it is a color printer. So i could install a
 second color printer which would only be available to a special print user.


I assume that this is printer dependent.  So I'd look at
  man lpoptions
and try listing the various options available
  lpoption -p printer -l
and look at storing the needed options in
  ~/.cups/lpoptions
or
  /etc/cups/lpoptions

For example, on my HP L7590 (color all-in-one):

$ lpoptions -p home-printer -l
PrintoutMode/Printout Mode: Draft Draft.Gray *Normal Normal.Gray High
High.Gray PhotoBest PhotoHigh PhotoNormal
InputSlot/Media Source: *Default PhotoTray Upper Lower CDDVDTray Envelope
LargeCapacity Manual MPTray
PageSize/Page Size: Custom.WIDTHxHEIGHT *Letter A4 Photo Photo5x7
PhotoTearOff 3x5 5x8 A5 A6 A6TearOff B5JIS CDDVD80 CDDVD120 Env10 EnvC5
EnvC6 EnvDL EnvISOB5 EnvMonarch Executive FLSA Hagaki Legal Oufuku w558h774
w612h935
Duplex/Double-Sided Printing: DuplexNoTumble DuplexTumble *None
Quality/Resolution, Quality, Ink Type, Media Type: *FromPrintoutMode
300ColorCMYK 300DraftColorCMYK 300DraftGrayscaleCMYK 300FastDraftColorCMYK
300FastDraftGrayscaleCMYK 300GrayscaleCMYK 600ColorCMYK 600GrayscaleCMYK
600PhotoCMYK 600PhotoNormalCMYK 1200PhotoCMYK

So I assume that setting option Normal.Gray instead of Normal (the defaullt)
would give me gray-scale
printing.

YMMV, of course.

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Unable to execute a script , Permission denied

2010-05-26 Thread Dale Dellutri
On Tue, May 25, 2010 at 8:27 AM, Jatin Davey jasho...@cisco.com wrote:

 On 5/25/2010 6:44 PM, Bowie Bailey wrote:
  Jatin Davey wrote:
 
  Here is the script that i am trying to execute as a non-root user:
 
  #!/bin/sh
  ps -C java -o thcount  /home/proc_threads/tempfile
  awk ' { total += $1 } END { print total } ' /home/proc_threads/tempfile
 
  here is the output when i try to execute as a non-root user:
 
  ./javathreads: line 2: /home/proc_threads/tempfile: Permission denied
  awk: cmd. line:1: fatal: cannot open file
  `/home/proc_threads/tempfile' for reading (Permission denied)
 
  The script is running, but the 'awk' line is failing to read
  /home/proc_threads/tempfile.  What are the permissions on that file and
  directory?
 
 
   $ ls -ld /home/proc_threads
 
   $ ls -l /home/proc_threads/tempfile
 
 

 Thanks all

 I finally figured out that the tempfile that i was creating did not have
 proper permissions for the script to write into. Now i have fixed it
 using the chmod command and it is working fine.


If more than one other user executes this script at the same time,
tempfile may be overwritten by the second before the first can run
the awk line.  Change this to use a pipe.
-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] [OT] Small touch screens that works with CentOS

2010-03-19 Thread Dale Dellutri
On Fri, Mar 19, 2010 at 6:44 AM, Pascal Robert prob...@macti.ca wrote:

 Hi,

 We want to display on a small LCD screen next to our meeting rooms and
 optionally let people book the room from the panel. We looked at different
 providers and those solutions either works with Exchange or Lotus Notes...

 Since I already have code to fetch events from any CalDAV/WebDSV servers,
 I'm looking at building the system myself. So I'm wondering if any of you
 can recommend small LCD screen that works well with Linux (the app would be
 a full screen Web app, browser have to be Gecko or WebKit based), and even
 better if the screen can have « touch buttons » (so that people don't have
 to use a physical keyboard to book the room), that's even better. I guess my
 other option would be a iPad.


The following page lists touchscreen laptops and add-on touchscreens:

  http://tuxmobil.org/touch_laptops.html

including Magic Touch which claims Linux compatibility.

And supposedly Freescale will soon ship its 7 touchscreen tablet.

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Temperature sensor

2010-02-26 Thread Dale Dellutri
On Fri, Feb 26, 2010 at 10:00 AM, Bowie Bailey bowie_bai...@buc.com wrote:

 Does anyone know of a cheap temperature sensor that will work with
 Linux?  I don't need a fancy monitoring appliance, I just want a simple
 sensor that I can connect to one of my monitoring servers to let me know
 if the server room is getting hot.


I;m not sure what you consider cheap.  I've  used a Sensatronics Model E4,
for which I've written my own daemon software to take a reading and log it
every x minutes.  I've also had a Sensaphone Model 1104 which can
automatically call multiple phone numbers and play a message about
fault conditions.

Each of these were in the $400 to $600 range (with sensors).

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] OpenSSH-5.3p1 selinux problem on CentOS-5.4.

2010-02-03 Thread Dale Dellutri
On Wed, Feb 3, 2010 at 9:26 AM, James B. Byrne byrn...@harte-lyne.cawrote:


 On Wed, February 3, 2010 09:48, Ned Slider wrote:
  James B. Byrne wrote:
  Note: I am digest subscriber so if you could copy me directly on
  any reply to the list I would appreciate it very much.
 
 
  snip
 
   After a modest amount of research we decided that the
  best answer was to use a more recent version of OpenSSH
  (5.3p1)that supports chroot as a configurable option.
 
 
  I've not tested it, but I believe the chroot stuff was backported
  some while ago:
 

 Thank you very much for the information for I was not aware of this.

 Unfortunately, having tested the CentOS stock sshd server I discover
 that this back-port is very similar to that of the sftponly hack of
 several years ago.  It is not the configurable chroot of
 OpenSSH-5.3.  To begin with, it very much appears from the
 documentation as if this is an all or nothing setting; if it is on
 then all ssh users are chrooted. Further, to use this feature with
 interactive sessions one must copy all of the requisite system
 utilities into directories under the chroot directory.

 (For an interactive session this requires at least a shell,
 typically sh(1), and basic /dev nodes such as null(4), zero(4),
 stdin(4), stdout(4), stderr(4), arandom(4) and tty(4) devices.)

 This is not a viable alternative since the system is remotely managed.


You mention two problems:
 1. all or nothing setting
  2. copy all of the requisite system utilities

As for #1, you could run two separate SSH daemons (using different
ports), so that only 1 has the chroot option.  Here's a discussion about
how to run two separate SSH daemons:
  http://www.DaleDellutri.com/prog.html

As for #2, I don't understand how the fact that the system is remotely
managed makes copying the files not a viable alternative.  Do you
not have root access to the server?  (I'm not criticising, I simply don't
understand.)


 So, I am left still seeking answers to my original questions.

 1. Is it possible to mount the selinux filesystem twice on the same
 host having different roots?

 2. If so, then how is this accomplished?

 3. If not, then is there anything else that I can do, besides
 disabling selinux support in the sshd daemon, to get OpenSSH-5.3
 chroot to work with SELinux?


I am also interested in the answers to these questions.

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos