On Tue, May 4, 2010 at 11:00 PM, Juan Romero Pardines <
xtr...@gmail.com> wrote:
> 2010/5/4 Jimmy Tang <
jcf...@gmail.com>:
>
>> [jtang@duo xbps-src]$ strace xbps-uhelper.static -r
>
> Erm, forgot to say please also use strace -f to trace child processes.
>
here's the trace...
[jtang@duo xbps-src]$ strace -f xbps-uhelper.static -r
/home/jtang/xbps-templates/masterdir sanitize-plist
/home/jtang/xbps-templates/masterdir/pkg-destdir/xbps-base-files-0.35/files.plist
execve("/home/jtang/XPBS/usr/local/sbin/xbps-uhelper.static",
["xbps-uhelper.static", "-r", "/home/jtang/xbps-templates/maste",
"sanitize-plist", "/home/jtang/xbps-templates/maste"], [/* 55 vars
*/]) = 0
uname({sys="Linux", node="duo", ...}) = 0
brk(0) = 0x2269000
brk(0x2269f60) = 0x2269f60
arch_prctl(ARCH_SET_FS, 0x2269890) = 0
brk(0x228af60) = 0x228af60
brk(0x228b000) = 0x228b000
access("/etc/selinux/", F_OK) = 0
open("/etc/selinux/config", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=447, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2b2e1d9a4000
read(3, "# This file controls the state o"..., 4096) = 447
read(3, "", 4096) = 0
close(3) = 0
munmap(0x2b2e1d9a4000, 4096) = 0
open("/proc/mounts", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2b2e1d9a5000
read(3, "rootfs / rootfs rw 0 0\n/dev/root"..., 4096) = 882
read(3, "", 4096) = 0
close(3) = 0
munmap(0x2b2e1d9a5000, 4096) = 0
open("/home/jtang/xbps-templates/masterdir/pkg-destdir/xbps-base-files-0.35/files.plist",
O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0600, st_size=10530, ...}) = 0
mmap(NULL, 12288, PROT_READ, MAP_SHARED, 3, 0) = 0x2b2e1d9a6000
close(3) = 0
madvise(0x2b2e1d9a6000, 12288, MADV_SEQUENTIAL) = 0
futex(0x226af0c, FUTEX_WAIT, 0, NULL) = -1 EINTR (Interrupted system call)
selinux is disabled...
[jtang@duo xbps-src]$ /usr/sbin/getenforce
Disabled
[jtang@duo xbps-src]$
and...
[jtang@duo xbps-src]$ rpm -qa | egrep 'kernel|glibc'
kernel-devel-2.6.18-128.4.1.el5.x86_64
kernel-module-fuse-2.6.18-128.4.1.el5-2.6.3-1.sl5.x86_64
kernel-xen-2.6.18-128.4.1.el5.x86_64
kernel-xen-devel-2.6.18-128.7.1.el5.x86_64
kernel-xen-devel-2.6.18-164.2.1.el5.x86_64
kernel-devel-2.6.18-128.7.1.el5.x86_64
kernel-devel-2.6.18-164.11.1.el5.x86_64
compat-glibc-headers-2.3.4-2.26.x86_64
glibc-2.5-42.i686
kernel-2.6.18-164.2.1.el5.x86_64
kernel-headers-2.6.18-164.11.1.el5.x86_64
glibc-headers-2.5-42.x86_64
kernel-devel-2.6.18-164.2.1.el5.x86_64
kernel-2.6.18-128.7.1.el5.x86_64
kernel-xen-devel-2.6.18-164.11.1.el5.x86_64
kernel-xen-devel-2.6.18-128.4.1.el5.x86_64
glibc-2.5-42.x86_64
glibc-devel-2.5-42.x86_64
kernel-module-fuse-2.6.18-128.4.1.el5xen-2.6.3-1.sl5.x86_64
kernel-module-fuse-2.6.18-128.7.1.el5xen-2.6.3-1.sl5.x86_64
kernel-xen-2.6.18-128.7.1.el5.x86_64
kernel-2.6.18-164.11.1.el5.x86_64
kernel-module-fuse-2.6.18-128.7.1.el5-2.6.3-1.sl5.x86_64
glibc-common-2.5-42.x86_64
glibc-devel-2.5-42.i386
kernel-xen-2.6.18-164.2.1.el5.x86_64
kernel-2.6.18-128.4.1.el5.x86_64
kernel-xen-2.6.18-164.11.1.el5.x86_64
everything is quite recent, mind you typically rhel5 the kernel
version is quite misleading they back port lots of changes from more
recent kernels, so even though the kernel is 2.6.18 it might really be
more like a 2.6.2x something or so...
jimmy