Eben King wrote:
> What could cause this?
>
> root@pc:/# /etc/init.d/sysklogd stop
> * Stopping system log daemon...
> /etc/init.d/sysklogd: line 71: /sbin/start-stop-daemon: cannot execute
> binary file
>
> [fail]
>
> root@pc:/# stat /sbin/start-stop-daemon
> File: `/sbin/start-stop-daemon'
> Size: 18520 Blocks: 40 IO Block: 4096 regular file
> Device: 1602h/5634d Inode: 226463 Links: 1
> Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
> Access: 2006-07-18 13:53:39.000000000 -0400
> Modify: 2005-09-24 13:39:30.000000000 -0400
> Change: 2006-01-30 17:45:06.000000000 -0500
>
> root@pc:/# lsattr /sbin/start-stop-daemon
> ----------------- /sbin/start-stop-daemon
>
> root@pc:/#
What do the following commands show:
# file /sbin/start-stop-daemon
# ldd /sbin/start-stop-daemon
Also check to see if the file is full of nulls.
# od -x /sbin/start-stop-daemon
If you see nothing but 0000's, the file has been zeroed out. We usually
see this when file is open for writing when a system running XFS is
powered off abruptly. Hooray for metadata journaled filesystems (where
the actual data isn't journalled).
- Ian C. Blenke <ian@blenke.com> http://ian.blenke.com/
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 14:48:04 EDT