[CentOS] httpd crashes after signal HUP

[RedShift]

Hello


I'm running CentOS 5.3 with httpd-2.2.3-22.el5.centos.x86_64 and 
php-5.1.6-23.2.el5_3.x86_64. When the logrotate scripts run and send the HUP 
signal to httpd, the httpd process quits instead of reloading. The only thing I 
can find in the logs is this:

[Sun Apr 19 04:02:04 2009] [notice] seg fault or similar nasty error detected 
in the parent process

There wasn't any segfault reported in dmesg and I couldn't find anything else 
in the other logs (messages, etc...)

It's reproducable every time, when I send the HUP signal to the master httpd 
process the same thing happens.

My configuration is nothing special, just the stock one, with a few unnecesary 
modules commented out and one virtual host.


Thanks,


Glenn


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

Re: [CentOS] httpd crashes after signal HUP

[RedShift]

>- Oorspronkelijk bericht -
>Van
: RedShift [mailto:redsh...@pandora.be]
>Verzonden
: zondag
, april
 19, 2009 09:42 AM
>Aan
: centos@centos.org
>Onderwerp
: [CentOS] httpd crashes after signal HUP
>
>Hello
>
>
>I'm running CentOS 5.3 with httpd-2.2.3-22.el5.centos.x86_64 and 
>php-5.1.6-23.2.el5_3.x86_64. When the logrotate scripts run and send the HUP 
>signal to httpd, the httpd process quits instead of reloading. The only thing 
>I can find in the logs is this:
>
>[Sun Apr 19 04:02:04 2009] [notice] seg fault or similar nasty error detected 
>in the parent process
>
>There wasn't any segfault reported in dmesg and I couldn't find anything else 
>in the other logs (messages, etc...)
>
>It's reproducable every time, when I send the HUP signal to the master httpd 
>process the same thing happens.
>
>My configuration is nothing special, just the stock one, with a few unnecesary 
>modules commented out and one virtual host.
>

A follow-up, I cannot seem to reproduce this on my laptop (using i386 instead 
of x86_64) with the same configuration.


Glenn


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

Re: [CentOS] httpd crashes after signal HUP

[Per Qvindesland]

Have you tried this:
http://www.electrictoolbox.com/seg-fault-or-similar-nasty-error/

Per

--- Original message follows ---
SUBJECT: Re: [CentOS] httpd crashes after signal HUP
FROM:  "RedShift"
TO: "CentOS mailing list"
DATE: 19-04-2009 9:49

>- Oorspronkelijk bericht -
>Van
: RedShift [mailto:redsh...@pandora.be]
>Verzonden
: zondag
, april
19, 2009 09:42 AM
>Aan
: centos@centos.org
>Onderwerp
: [CentOS] httpd crashes after signal HUP
>

>Hello
>
>
>I'm running CentOS 5.3 with httpd-2.2.3-22.el5.centos.x86_64 and
php-5.1.6-23.2.el5_3.x86_64. When the logrotate scripts run and send
the HUP signal to httpd, the httpd process quits instead of reloading.
The only thing I can find in the logs is this:
>
>[Sun Apr 19 04:02:04 2009] [notice] seg fault or similar nasty error
detected in the parent process
>
>There wasn't any segfault reported in dmesg and I couldn't find
anything else in the other logs (messages, etc...)
>
>It's reproducable every time, when I send the HUP signal to the
master httpd process the same thing happens.
>
>My configuration is nothing special, just the stock one, with a few
unnecesary modules commented out and one virtual host.
>

A follow-up, I cannot seem to reproduce this on my laptop (using i386
instead of x86_64) with the same configuration.

Glenn

___
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

Re: [CentOS] httpd crashes after signal HUP

[RedShift]

Per Qvindesland wrote:
> Have you tried this:
> http://www.electrictoolbox.com/seg-fault-or-similar-nasty-error/
> 
> Per

Yes, I have tried it, but that's a workaround, not a real solution.


Glenn

> 
> --- Original message follows ---
> 
> *Subject: *Re: [CentOS] httpd crashes after signal HUP
> *From:  *"RedShift" 
> *To: *"CentOS mailing list" 
> *Date: *19-04-2009 9:49
> 
> 
>  >- Oorspronkelijk bericht -
>  >Van
> : RedShift [mailto:redsh...@pandora.be]
>  >Verzonden
> : zondag
> , april
> 19, 2009 09:42 AM
>  >Aan
> : centos@centos.org
>  >Onderwerp
> : [CentOS] httpd crashes after signal HUP
>  >
>  >Hello
>  >
>  >
>  >I'm running CentOS 5.3 with httpd-2.2.3-22.el5.centos.x86_64 and
> php-5.1.6-23.2.el5_3.x86_64. When the logrotate scripts run and send
> the HUP signal to httpd, the httpd process quits instead of
> reloading. The only thing I can find in the logs is this:
>  >
>  >[Sun Apr 19 04:02:04 2009] [notice] seg fault or similar nasty
> error detected in the parent process
>  >
>  >There wasn't any segfault reported in dmesg and I couldn't find
> anything else in the other logs (messages, etc...)
>  >
>  >It's reproducable every time, when I send the HUP signal to the
> master httpd process the same thing happens.
>  >
>  >My configuration is nothing special, just the stock one, with a
> few unnecesary modules commented out and one virtual host.
>  >
> 
> A follow-up, I cannot seem to reproduce this on my laptop (using
> i386 instead of x86_64) with the same configuration.
> 
> 
> Glenn
> 
> 

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

Re: [CentOS] Local root vulnerability in udev

[Lanny Marcus]

On Sun, Apr 19, 2009 at 12:10 AM, D Tucny  wrote:
> 2009/4/19 Lanny Marcus 
>> I just saw this thread in the OLM forum. Possibly of interest, since
>> they say it includes CentOS 5, if the update hasn't been released yet.
>> Always good  to keep boxes updated, for security and stability
>> reasons.
>>
>> 
>
> FYI, advisory IDs mentioned by upstream are
>
> CVE-2009-1185
> RHSA-2009:0427-01
>
> The CentOS update hasn't been released yet, but, I would expect it to make
> it out this weekend...

Anyone who has a CentOS 5 server with web sites on it should pay
attention to this one.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] httpd crashes after signal HUP

[Kai Schaetzl]

RedShift wrote on Sun, 19 Apr 2009 10:20:32 +0200:

> Yes, I have tried it, but that's a workaround, not a real solution.

Well, after reading just the first few lines I think the point is that a 
PHP accelerator (APC) is involved.

Kai

-- 
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com



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

Re: [CentOS] httpd crashes after signal HUP

[RedShift]

Kai Schaetzl wrote:
> RedShift wrote on Sun, 19 Apr 2009 10:20:32 +0200:
> 
>> Yes, I have tried it, but that's a workaround, not a real solution.
> 
> Well, after reading just the first few lines I think the point is that a 
> PHP accelerator (APC) is involved.
> 
> Kai
> 

There is no PHP accelerator involved. It's all standard.


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

Re: [CentOS] OT: Possible for Malware against Windows boxes to attack Firefox on Linux?

[mouss]

Robert Heller a écrit :
> [snip]
> 
> Linux does not care about file *names*. 

indeed Linux does not. but desktop managers do. That said, *.exe attacks
should only affect systems running Wine.


> [snip]
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] httpd crashes after signal HUP

[RedShift]

RedShift wrote:
> Hello
> 
> 
> I'm running CentOS 5.3 with httpd-2.2.3-22.el5.centos.x86_64 and 
> php-5.1.6-23.2.el5_3.x86_64. When the logrotate scripts run and send the HUP 
> signal to httpd, the httpd process quits instead of reloading. The only thing 
> I can find in the logs is this:
> 
> [Sun Apr 19 04:02:04 2009] [notice] seg fault or similar nasty error detected 
> in the parent process
> 
> There wasn't any segfault reported in dmesg and I couldn't find anything else 
> in the other logs (messages, etc...)
> 
> It's reproducable every time, when I send the HUP signal to the master httpd 
> process the same thing happens.
> 
> My configuration is nothing special, just the stock one, with a few 
> unnecesary modules commented out and one virtual host.
> 
> 
> Thanks,
> 
> 
> Glenn
> 
> 

I figured out it was coming from a PHP extension called MAPI, that comes 
shipped with a piece of software I use (Zarafa). This problem didn't occur on 
my laptop because it didn't have the mapi.so extension loaded. So this is not a 
CentOS problem.

For reference: http://forums.zarafa.com/viewtopic.php?f=9&t=2225


Best regards,


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

Re: [CentOS] OT: Possible for Malware against Windows boxes to attack Firefox on Linux?

[Robert Heller]

At Sun, 19 Apr 2009 15:07:05 +0200 CentOS mailing list  
wrote:

> 
> Robert Heller a écrit :
> > [snip]
> > 
> > Linux does not care about file *names*. 
> 
> indeed Linux does not. but desktop managers do. That said, *.exe attacks

Are you sure?  I would think that *Linux*-based desktop managers would
do something 'smart' like use the results of file (specificly 'file -i
..') rather than depend on the file name itself.  I know that since
MS-Windows lacks anything like the file command (as part of the native
O/S install), it uses the file extension as a 'type'.

> should only affect systems running Wine.
> 
> 
> > [snip]
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
> 
>  

-- 
Robert Heller -- 978-544-6933
Deepwoods Software-- Download the Model Railroad System
http://www.deepsoft.com/  -- Binaries for Linux and MS-Windows
hel...@deepsoft.com   -- http://www.deepsoft.com/ModelRailroadSystem/

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

Re: [CentOS] Weird performance problem

[JohnS]

On Sat, 2009-04-18 at 15:54 -0400, Ugo Bellavance wrote:
> JohnS wrote:
> 
> > -
> > That's a known problem with the Kernel and VM Kernel. You need the fixed
> > kernel.
> 
> Do you have an URL of the bug or something?
> 
> I updated to the latest kernel.
> 
> I was running 2.6.18-92.1.18.el5.028stab060.2PAE.
> 
> Regards,
---
There are one or two people that have recompiled a kernel to be
compatable with CentOS and it is on there site which they can join in
and give you the site.

Please read:
http://www.vmware.com/pdf/vmware_timekeeping.pdf

I don't reacall any one really saying if there was indeed a fix put into
that PAE or any Specific Kernel for CentOS. Can the CentOS Kernel
Builder Comment Please?

Also See: +1
http://wiki.centos.org/TipsAndTricks/VMWare_Server?highlight=(100hz)

JohnStanley

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

Re: [CentOS] Weird performance problem

[Akemi Yagi]

On Sun, Apr 19, 2009 at 8:34 AM, JohnS  wrote:

> I don't reacall any one really saying if there was indeed a fix put into
> that PAE or any Specific Kernel for CentOS. Can the CentOS Kernel
> Builder Comment Please?
>
> Also See: +1
> http://wiki.centos.org/TipsAndTricks/VMWare_Server?highlight=(100hz)
>
> JohnStanley

As noted at the top of that wiki page, the contents need to be
updated.  When I added that note, I intended to do it asap but have
not had a chance to do so.  However, the link referenced in there (
http://kb.vmware.com/kb/1006427 ) is the best source for timekeeping
at this moment.  In short, CentOS no longer offers 100Hz kernels
because the divider=10 kernel option now works.

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

Re: [CentOS] Weird performance problem

[JohnS]

On Sun, 2009-04-19 at 09:02 -0700, Akemi Yagi wrote:
> On Sun, Apr 19, 2009 at 8:34 AM, JohnS  wrote:
> 
> > I don't reacall any one really saying if there was indeed a fix put into
> > that PAE or any Specific Kernel for CentOS. Can the CentOS Kernel
> > Builder Comment Please?
> >
> > Also See: +1
> > http://wiki.centos.org/TipsAndTricks/VMWare_Server?highlight=(100hz)
> >
> > JohnStanley
> 
> As noted at the top of that wiki page, the contents need to be
> updated.  When I added that note, I intended to do it asap but have
> not had a chance to do so.  However, the link referenced in there (
> http://kb.vmware.com/kb/1006427 ) is the best source for timekeeping
> at this moment.  In short, CentOS no longer offers 100Hz kernels
> because the divider=10 kernel option now works.
> 
> Akemi

Thanks Akemi for the update on it. That should fix hin up,

JohnStanley

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

[CentOS] X won't start

[Robert]

This machine is running CentOS 5.3, fully updated Linux 
mavis.localdomain 2.6.18-128.1.6.el5 #1
SMP Wed Apr 1 09:19:18 EDT 2009 i686 athlon i386 GNU/Linux. Video is an 
ATI Radeon 9000.
X froze overnight and attempts to restart it fail.  I tried an old 
kernel (2.6.18-92.1.22.el5)
before realizing that root can start X and a virgin user can start X. I 
still can't use my
original user name.  I'm sure the last line of this is telling me 
something that I'm missing.

(**) RADEON(0): RADEONDRIStop
(**) RADEON(0): EngineRestore (16/16)
(**) RADEON(0): RADEONDisplayPowerManagementSet(0,0x0)
(**) RADEON(0): RADEONRestore
(**) RADEON(0): RADEONRestoreMode()
(**) RADEON(0): RADEONRestoreMode(0x9d2831c)
(**) RADEON(0): RADEONRestoreMemMapRegisters() :
(**) RADEON(0):   MC_FB_LOCATION   : 0x1fff
(**) RADEON(0):   MC_AGP_LOCATION  : 0x27ff2000
(**) RADEON(0):   Map Changed ! Applying ...
(**) RADEON(0):   Map applied, resetting engine ...
(**) RADEON(0): Updating display base addresses...
(**) RADEON(0): Memory map updated.
(**) RADEON(0): Programming CRTC1, offset: 0x
(**) RADEON(0): Wrote: 0x000c 0x00030065 0x (0xa400)
(**) RADEON(0): Wrote: rd=12, fd=101, pd=3
(**) RADEON(0): Disposing accel...
(**) RADEON(0): Disposing cusor info
(**) RADEON(0): Disposing DGA
(**) RADEON(0): Unmapping memory
(**) RADEON(0): RADEONDRICloseScreen
FreeFontPath: FPE "unix/:7100" refcount is 2, should be 1; fixing.

If it matters I normally boot into run level 3, log in and issue
"startx" from the BASH prompt.

Any ideas welcome.


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

Re: [CentOS] OT: Possible for Malware against Windows boxes to attack Firefox on Linux?

[mouss]

Robert Heller a écrit :
> At Sun, 19 Apr 2009 15:07:05 +0200 CentOS mailing list  
> wrote:
> 
>> Robert Heller a écrit :
>>> [snip]
>>>
>>> Linux does not care about file *names*. 
>> indeed Linux does not. but desktop managers do. That said, *.exe attacks
> 
> Are you sure?  I would think that *Linux*-based desktop managers would
> do something 'smart' like use the results of file (specificly 'file -i
> ..') rather than depend on the file name itself. 

I just tried: renaming a .mp3 to a .gif and double clicking. I get an
error saying something like "bad gif file"...

The problem with the "file type" is that users don't see it. when I
click to open a file, I somewhat "trust" the extension. If I open
foo.png, it's because I want top open an image, not to run latex or make.

maybe the solution would be to check that the extension matches the file
type and if not warn the user.


> I know that since
> MS-Windows lacks anything like the file command (as part of the native
> O/S install), it uses the file extension as a 'type'.
> 

While that was inherited from DOS, the fact that windows took the "it's
all about clicking" way, they didn't have much choice. and it gets
annoying anyway:

- when I double click on a ".pl", do I want to run perl or do I want to
edit the file?

- sometimes, when you remove an application (on windows xp), the system
can no more find the "most appropriate" application (even if you have
many apps that would be ok).

- many applications have a tendency to "steal" a lot of extensions.
under windows, I never let such an app to register any association!

...

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

Re: [CentOS] X won't start

[JohnS]

On Sun, 2009-04-19 at 12:25 -0500, Robert wrote:
> This machine is running CentOS 5.3, fully updated Linux 
> mavis.localdomain 2.6.18-128.1.6.el5 #1
> SMP Wed Apr 1 09:19:18 EDT 2009 i686 athlon i386 GNU/Linux. Video is an 
> ATI Radeon 9000.
> X froze overnight and attempts to restart it fail.  I tried an old 
> kernel (2.6.18-92.1.22.el5)
> before realizing that root can start X and a virgin user can start X. I 
> still can't use my
> original user name.  I'm sure the last line of this is telling me 
> something that I'm missing.
> 
> (**) RADEON(0): RADEONDRIStop
> (**) RADEON(0): EngineRestore (16/16)
> (**) RADEON(0): RADEONDisplayPowerManagementSet(0,0x0)
> (**) RADEON(0): RADEONRestore
> (**) RADEON(0): RADEONRestoreMode()
> (**) RADEON(0): RADEONRestoreMode(0x9d2831c)
> (**) RADEON(0): RADEONRestoreMemMapRegisters() :
> (**) RADEON(0):   MC_FB_LOCATION   : 0x1fff
> (**) RADEON(0):   MC_AGP_LOCATION  : 0x27ff2000
> (**) RADEON(0):   Map Changed ! Applying ...
> (**) RADEON(0):   Map applied, resetting engine ...
> (**) RADEON(0): Updating display base addresses...
> (**) RADEON(0): Memory map updated.
> (**) RADEON(0): Programming CRTC1, offset: 0x
> (**) RADEON(0): Wrote: 0x000c 0x00030065 0x (0xa400)
> (**) RADEON(0): Wrote: rd=12, fd=101, pd=3
> (**) RADEON(0): Disposing accel...
> (**) RADEON(0): Disposing cusor info
> (**) RADEON(0): Disposing DGA
> (**) RADEON(0): Unmapping memory
> (**) RADEON(0): RADEONDRICloseScreen
> FreeFontPath: FPE "unix/:7100" refcount is 2, should be 1; fixing.
> 
> If it matters I normally boot into run level 3, log in and issue
> "startx" from the BASH prompt.
> 
> Any ideas welcome.
---
IDEA ONLY! Caution!
Perhaps the ATIRadeon Kernel Module is not loaded into the kernel?
So maybe a modprobe ? then startx
ATI seems to have a slew of these problems.
Alternative: Try another card..

JohnStanley

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

Re: [CentOS] X won't start

[William L. Maltby]

On Sun, 2009-04-19 at 12:25 -0500, Robert wrote:
> This machine is running CentOS 5.3, fully updated Linux 
> mavis.localdomain 2.6.18-128.1.6.el5 #1
> SMP Wed Apr 1 09:19:18 EDT 2009 i686 athlon i386 GNU/Linux. Video is an 
> ATI Radeon 9000.
> X froze overnight and attempts to restart it fail.  I tried an old 
> kernel (2.6.18-92.1.22.el5)
> before realizing that root can start X and a virgin user can start X. I 
> still can't use my
> original user name.  I'm sure the last line of this is telling me 
> something that I'm missing.
> 
> (**) RADEON(0): RADEONDRIStop
> (**) RADEON(0): EngineRestore (16/16)
> (**) RADEON(0): RADEONDisplayPowerManagementSet(0,0x0)
> (**) RADEON(0): RADEONRestore
> (**) RADEON(0): RADEONRestoreMode()
> (**) RADEON(0): RADEONRestoreMode(0x9d2831c)
> (**) RADEON(0): RADEONRestoreMemMapRegisters() :
> (**) RADEON(0):   MC_FB_LOCATION   : 0x1fff
> (**) RADEON(0):   MC_AGP_LOCATION  : 0x27ff2000
> (**) RADEON(0):   Map Changed ! Applying ...
> (**) RADEON(0):   Map applied, resetting engine ...
> (**) RADEON(0): Updating display base addresses...
> (**) RADEON(0): Memory map updated.
> (**) RADEON(0): Programming CRTC1, offset: 0x
> (**) RADEON(0): Wrote: 0x000c 0x00030065 0x (0xa400)
> (**) RADEON(0): Wrote: rd=12, fd=101, pd=3
> (**) RADEON(0): Disposing accel...
> (**) RADEON(0): Disposing cusor info
> (**) RADEON(0): Disposing DGA
> (**) RADEON(0): Unmapping memory
> (**) RADEON(0): RADEONDRICloseScreen
> FreeFontPath: FPE "unix/:7100" refcount is 2, should be 1; fixing.
> 
> If it matters I normally boot into run level 3, log in and issue
> "startx" from the BASH prompt.
> 
> Any ideas welcome.

I'm now expert, but have done some programming in the past. I suspect
that the X font server is either running already or scrogged the
cleanup.

Try

# ps -eaf|grep xfs
xfs   2927 1  0 07:12 ?00:00:00 xfs -droppriv -daemon

and see if it is still running. If so, maybe a simple telinit 3 and then
telinit 5 will clean it up and let you get going. Regardless, if it is
running, something like this might give you enough to continue.

# lsof -p 2927
COMMAND  PID USER   FD   TYPE DEVICESIZE NODE NAME
xfs 2927  xfs  cwdDIR  253,040962 /


xfs 2927  xfs3u  unix 0xf5ded580 10315 /tmp/.font-unix/fs7100
xfs 2927  xfs4u  unix 0xf5c74700 13635 /tmp/.font-unix/fs7100

These lst two lines seem to be the socket setup the xfs uses. After
making sure the xfs daemon is not running, you may be able to remove
them. However, I believe they should disappear if you get the xfs
shutdown cleanly. If there is an old socket left in the fs from some
kind of previous error, this may not clean up properly.

I do think a telinit 3/5 combo might do it. If not, a reboot should
remove the /tmp file system and recreate it new. Then you should be OK.

# ls -l /tmp/.font-unix/*7100*
srwxrwxrwx 1 xfs xfs 0 Apr 19 07:12 /tmp/.font-unix/fs7100

> 

Again, I'm not really knowledgeable about this stuff.

HTH
-- 
Bill

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

Re: [CentOS] X won't start

[William L. Maltby]

On Sun, 2009-04-19 at 14:10 -0400, William L. Maltby wrote:
> 

> I'm now expert, but have done some programming in the past. I suspect

s/now/no/   # <*chagrin*>

> 

-- 
Bill

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

Re: [CentOS] httpd crashes after signal HUP

[Kai Schaetzl]

RedShift wrote on Sun, 19 Apr 2009 14:41:50 +0200:

> There is no PHP accelerator involved. It's all standard.

Maybe for you. There's probably an Apache module or a PHP extension 
installed that is causing this.

Ah, I just saw your next message. So, you know the reason now.

Kai

-- 
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com



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

Re: [CentOS] X won't start

[Robert]

William L. Maltby wrote:
> On Sun, 2009-04-19 at 12:25 -0500, Robert wrote:
>   


>> 
>> 
>
> Again, I'm not really knowledgeable about this stuff.
>
> HTH
>   
First, thanks to both you and John Stanley and anyone else whose reply I 
lost.

Finally, after beating up on myself, I found an   
~/.Xclients-default file.  Not missing, but empty!
Copying the file from the newly created user fixed the problem.

This is after the repair:
[...@mavis ~]$ ls -l  ~/.X*
-rw--- 1 rj rj 222 Mar 19 11:52 /home/rj/.Xauthority
-rwxr-xr-x 1 rj rj 189 Jun 20  2007 /home/rj/.Xclients
-rwxr-xr-x 1 rj rj 189 Apr 19 13:09 /home/rj/.Xclients-default


I don't understand why .Xclients and .Xclients-default are the same 
length (or even why both are needed).

[...@mavis ~]$ cat .Xclients
#! /bin/bash

# Created by Red Hat Desktop Switcher

if [ -e "$HOME/.Xclients-$HOSTNAME$DISPLAY" ]; then
exec $HOME/.Xclients-$HOSTNAME$DISPLAY
else
exec $HOME/.Xclients-default
fi
[...@mavis ~]$

and

[...@mavis ~]$ cat .Xclients-default
#! /bin/bash
# Created by Red Hat Desktop Switcher

WM="startkde"
WMPATH="/usr/bin /opt/bin /usr/local/bin /usr/X11R6/bin"

for p in $WMPATH ; do
[ -x $p/$WM ] && exec $p/$WM
done

exit 1
[...@mavis ~]$


But startx sure grows disappointed in a hurry if the latter is empty.



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

Re: [CentOS] X won't start

[JohnS]

On Sun, 2009-04-19 at 13:54 -0500, Robert wrote:
> 
> William L. Maltby wrote:
> > On Sun, 2009-04-19 at 12:25 -0500, Robert wrote:
> >   
> 
> 
> >> 
> >> 
> >
> > Again, I'm not really knowledgeable about this stuff.
> >
> > HTH
> >   
> First, thanks to both you and John Stanley and anyone else whose reply I 
> lost.
> 
> Finally, after beating up on myself, I found an   
> ~/.Xclients-default file.  Not missing, but empty!
> Copying the file from the newly created user fixed the problem.
> 
> This is after the repair:
> [...@mavis ~]$ ls -l  ~/.X*
> -rw--- 1 rj rj 222 Mar 19 11:52 /home/rj/.Xauthority
> -rwxr-xr-x 1 rj rj 189 Jun 20  2007 /home/rj/.Xclients
> -rwxr-xr-x 1 rj rj 189 Apr 19 13:09 /home/rj/.Xclients-default
> 
> 
> I don't understand why .Xclients and .Xclients-default are the same 
> length (or even why both are needed).
> 
> [...@mavis ~]$ cat .Xclients
> #! /bin/bash
> 
> # Created by Red Hat Desktop Switcher
> 
> if [ -e "$HOME/.Xclients-$HOSTNAME$DISPLAY" ]; then
> exec $HOME/.Xclients-$HOSTNAME$DISPLAY
> else
> exec $HOME/.Xclients-default
> fi
> [...@mavis ~]$
> 
> and
> 
> [...@mavis ~]$ cat .Xclients-default
> #! /bin/bash
> # Created by Red Hat Desktop Switcher
> 
> WM="startkde"
> WMPATH="/usr/bin /opt/bin /usr/local/bin /usr/X11R6/bin"
> 
> for p in $WMPATH ; do
> [ -x $p/$WM ] && exec $p/$WM
> done
> 
> exit 1
> [...@mavis ~]$
> 
> 
> But startx sure grows disappointed in a hurry if the latter is empty.
---
Interesting.. Upstream mentions in bugzilla that the kernel module is
not loaded. Maybe if that specific file is not present that is what
happens also?>

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

Re: [CentOS] OT: Possible for Malware against Windows boxes to attack Firefox on Linux?

[Robert Heller]

At Sun, 19 Apr 2009 20:06:43 +0200 CentOS mailing list  
wrote:

> 
> Robert Heller a écrit :
> > At Sun, 19 Apr 2009 15:07:05 +0200 CentOS mailing list  
> > wrote:
> > 
> >> Robert Heller a écrit :
> >>> [snip]
> >>>
> >>> Linux does not care about file *names*. 
> >> indeed Linux does not. but desktop managers do. That said, *.exe attacks
> > 
> > Are you sure?  I would think that *Linux*-based desktop managers would
> > do something 'smart' like use the results of file (specificly 'file -i
> > ..') rather than depend on the file name itself. 
> 
> I just tried: renaming a .mp3 to a .gif and double clicking. I get an
> error saying something like "bad gif file"...

I'd consider that a 'bug' with the desktop manager (if I were to use
such as thing -- I don't/won't).

> 
> The problem with the "file type" is that users don't see it. when I
> click to open a file, I somewhat "trust" the extension. If I open
> foo.png, it's because I want top open an image, not to run latex or make.

Many naive users save their images or document as 'my image' and don't
explicitly add an extension.  (Under MS-Windows the O/S or application
sticks an extension on and never displays it -- a really *bad* thing
that is commonly exploited by E-Mail virus writers ala foo.jpeg.exe.) 
MacOS(X) lets users save any sort of file with any sort of name and
makes no attempt to add or enforce file name extension conventions. 
Old school UNIX users add extensions mostly by convention and for
convience. Only compiler execs (eg gcc) and the like pay any attention
to the extensions most of the time.

> 
> maybe the solution would be to check that the extension matches the file
> type and if not warn the user.

The *original* desktop manager / GUI O/S, MacOS, uses a special file
(finder info) to save the application code of the application (4 [text]
bytes, one long word) and the file 'type' (also 4 [text] bytes, one
long word) whenever a file was created. The 'finder info' was part of
the file system 'meta data'. The file 'name' (with or without any
'extension') was NEVER used to determine how to deal with the file.  I
believe MacOSX still does something similar (I don't know if MacOSX uses
file system 'meta data' or if MacOSX uses the file utility (or something
like the file utility).

> 
> 
> > I know that since
> > MS-Windows lacks anything like the file command (as part of the native
> > O/S install), it uses the file extension as a 'type'.
> > 
> 
> While that was inherited from DOS, the fact that windows took the "it's
> all about clicking" way, they didn't have much choice. and it gets
> annoying anyway:

Not really inherited from DOS, since DOS (like CP/M) did not really do
anything *itself* with file extensions (other than having a directory
structure that stored file names as a pair of fixed-length text strings
(ala struct {char name[8]; char ext[3];}).

> 
> - when I double click on a ".pl", do I want to run perl or do I want to
> edit the file?

Under the MacOS 'way' clicking on it would be to run perl.  I believe
something like Apple-Click (or shift or ctrl)-click would pop up a menu
of possible applications to open with, based on the *type*, which would
include a text editor (since a perl script would be of type TEXT, with
an app code of something like PERL).

> 
> - sometimes, when you remove an application (on windows xp), the system
> can no more find the "most appropriate" application (even if you have
> many apps that would be ok).
> 
> - many applications have a tendency to "steal" a lot of extensions.
> under windows, I never let such an app to register any association!
> 
> ...
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
> 
>   

-- 
Robert Heller -- 978-544-6933
Deepwoods Software-- Download the Model Railroad System
http://www.deepsoft.com/  -- Binaries for Linux and MS-Windows
hel...@deepsoft.com   -- http://www.deepsoft.com/ModelRailroadSystem/

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

[CentOS] rpmbuild failure

[lhecking]

 I'm trying to rebuild nx-3.2.0-8.el5.centos.src.rpm from the extras repo.
 It works on a machine running 5.1, but fails on another running 5.3. The
 working machine is arch=x86_64, the other i386. The strange bit is the line
 rpmbuild complains about: it's the last line in the spec file, at the end
 of the %changelog section:

[...]
Processing files: nx-debuginfo-3.2.0-8
Finding  Provides: /usr/src/redhat/SOURCES/nxfind-provides.sh
error: line 352: Dependency tokens must begin with alpha-numeric, '_' or '/': - 
Updated SuSE package to work with Fedora

error: Failed to find Provides:
Requires(rpmlib): rpmlib(PayloadFilesHavePrefix) <= 4.0-1 
rpmlib(CompressedFileNames) <= 3.0.4-1
Checking for unpackaged file(s): /usr/lib/rpm/check-files 
/var/tmp/nx-3.2.0-8-root-root


RPM build errors:
line 352: Dependency tokens must begin with alpha-numeric, '_' or '/': - 
Updated SuSE package to work with Fedora

Failed to find Provides:
# 


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

Re: [CentOS] The law difference between country

[Hidetsugu Hiraki]

Dear Toshaan,

Thank you for your teaching.

Hiraki
On Sat, Apr 18, 2009 at 6:26 PM, Tosh  wrote:
> Hidetsugu Hiraki wrote:
>> Dear Madam or Sir,
>>
>> I live in Japan. So I must comply with the nation's law.
>> When I install software for Linux, is there any easy way to know
>> whether the the installation and use of the software is legal or not?
>>
>> Please teach me.
>>
>> Hiraki
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> http://lists.centos.org/mailman/listinfo/centos
>>
> As CentOS is GPLv2 compliant, you can use it freely for your own purpose.
> Only if you want to redistribute or use it for commercial purposes that
> you have to keep account with many factors you need to comply with.
>
>
> --
> Toshaan  - http://www.toshaan.be
> ___
> 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

Re: [CentOS] The law difference between country

[Hidetsugu Hiraki]

Dear Ms. or Mr. nate,

Thanks.

Hiraki

On Sat, Apr 18, 2009 at 2:08 PM, nate  wrote:
> Hidetsugu Hiraki wrote:
>> Dear Madam or Sir,
>>
>> I live in Japan. So I must comply with the nation's law.
>> When I install software for Linux, is there any easy way to know
>> whether the the installation and use of the software is legal or not?
>
> Worst case you can always use TurboLinux, been around since 1992
> and headquartered in Japan.
>
> http://www.turbolinux.com/
>
> In general I don't think you have anything to worry about.
>
> nate
>
>
> ___
> 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