| View previous topic :: View next topic |
| Author |
Message |
ReD-BaRoN
Apprentice
Joined: 06 Feb 2004
Posts: 208
|
 Posted: Thu Apr 12, 2007 1:23 am Post subject: ls is seg faulting! |
 |
|
Check this out! Any ideas? Seems the wildcard is causing ls to segfault!
| Code: | init.d # ls /etc/init.d/*
Segmentation fault
init.d # ls /etc/init.d/
apache2 checkroot crypto-loop fetchmail hdparm local net.eth0 ntp-client rmnologin sshd urandom
bittorrent-tracker chpax depscan.sh firewall hostname localmount net.lo ntpd rsyncd svscan vixie-cron
bootmisc clock dhcp functions.sh iptables modules netmount numlock runscript.sh syslog-ng
checkfs consolefont dovecot halt.sh keymaps named nscd reboot.sh shutdown.sh twistd |
|
|
| Back to top |
|
 |
SocialSecurity
n00b
Joined: 10 Mar 2007
Posts: 19
|
| Posted: Thu Apr 12, 2007 2:41 am Post subject: |
|
|
| If I recall, the wildcard is handled by the shell, so perhaps not a problem with ls? |
|
| Back to top |
|
|
di1bert
l33t
Joined: 16 May 2002
Posts: 963
Location: Oslo, Norway
|
| Posted: Mon Apr 16, 2007 1:57 pm Post subject: |
|
|
I've had that problem before when the server has been compromised.
I would run either rkhunter or chkrootkit on the box just to be sure (both are in portage).
Either that or there is something else at play, perhaps faulty hardware / memory....
Just my 0.02c worth...
-m
_________________
choff. |
|
| Back to top |
|
|
i92guboj
Bodhisattva
Joined: 30 Nov 2004
Posts: 10315
Location: Córdoba (Spain)
|
| Posted: Mon Apr 16, 2007 2:04 pm Post subject: |
|
|
| A few things could be responsible. A rootkit is always a possibility, though more common ones are a faulty filesystem, a faulty toolchain (or a too "optimized" one) or a faulty kernel using a faulty filesystem. Also, does it happen if you disable colors in ls? I remember seeing somewhere a bug report about ls segfaulting only when color is enabled, though that was a long time ago. |
|
| Back to top |
|
|
ReD-BaRoN
Apprentice
Joined: 06 Feb 2004
Posts: 208
|
| Posted: Mon Apr 16, 2007 8:51 pm Post subject: |
|
|
| di1bert wrote: | I've had that problem before when the server has been compromised.
I would run either rkhunter or chkrootkit on the box just to be sure (both are in portage).
Either that or there is something else at play, perhaps faulty hardware / memory....
Just my 0.02c worth...
-m |
I ran rkhunter and chkrootkit, neither report anything suspicious. For some reason however, rkhunter skips doing the MD5 checks  .
| Code: | Rootkit Hunter 1.2.9 is running
Determining OS... Unknown
Warning: This operating system is not fully supported!
All MD5 checks will be skipped! |
|
|
| Back to top |
|
|
|
Other Things Gentoo
