WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 139] xend stops logging entirely after startup

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 139] xend stops logging entirely after startup
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 04 Aug 2005 21:11:15 +0000
Delivery-date: Thu, 04 Aug 2005 21:11:19 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=139





------- Additional Comments From sean@xxxxxxxxx  2005-08-04 21:11 -------
There is a very good reason that xend doesn't log anything, it has no access to
it's log file.  This is a dump from /proc for the xend parent process:

root@fry:~/xen-unstable/tools/python> ls -l /proc/8818/fd/
total 22
lrwx------  1 root root 64 Aug  4 17:10 0 -> /dev/null
lrwx------  1 root root 64 Aug  4 17:10 1 -> /dev/null
lr-x------  1 root root 64 Aug  4 17:10 10 -> /dev/urandom
l-wx------  1 root root 64 Aug  4 17:10 11 -> pipe:[58031]
lrwx------  1 root root 64 Aug  4 17:10 12 -> socket:[58032]
lrwx------  1 root root 64 Aug  4 17:10 13 -> socket:[58034]
lrwx------  1 root root 64 Aug  4 17:10 14 -> /proc/xen/privcmd
lrwx------  1 root root 64 Aug  4 17:10 15 -> socket:[58035]
lrwx------  1 root root 64 Aug  4 17:10 17 -> /proc/xen/privcmd
lrwx------  1 root root 64 Aug  4 17:10 19 -> /proc/xen/privcmd
l-wx------  1 root root 64 Aug  4 17:10 2 -> /var/log/xend-debug.log
lr-x------  1 root root 64 Aug  4 17:10 20 -> pipe:[58289]
lrwx------  1 root root 64 Aug  4 17:10 21 -> /proc/xen/privcmd
lrwx------  1 root root 64 Aug  4 17:10 22 -> /proc/xen/privcmd
lr-x------  1 root root 64 Aug  4 17:10 24 -> pipe:[58290]
lrwx------  1 root root 64 Aug  4 17:10 3 -> socket:[58025]
lrwx------  1 root root 64 Aug  4 17:10 4 -> socket:[58027]
lrwx------  1 root root 64 Aug  4 17:10 5 -> socket:[58300]
lrwx------  1 root root 64 Aug  4 17:10 6 -> /proc/xen/privcmd
lrwx------  1 root root 64 Aug  4 17:10 7 -> socket:[58029]
lrwx------  1 root root 64 Aug  4 17:10 8 -> /proc/xen/privcmd
lr-x------  1 root root 64 Aug  4 17:10 9 -> pipe:[58031]

As compared to xcs:

root@fry:~/xen-unstable/tools/python> ls -l /proc/8817/fd/
total 12
l-wx------  1 root root 64 Aug  4 17:12 0 -> /var/log/xcs.log
l-wx------  1 root root 64 Aug  4 17:12 1 -> /var/log/xcs.log
lr-x------  1 root root 64 Aug  4 17:12 10 -> /dev/urandom
l-wx------  1 root root 64 Aug  4 17:12 11 -> /var/log/xcs.log
lrwx------  1 root root 64 Aug  4 17:12 2 -> socket:[58026]
lrwx------  1 root root 64 Aug  4 17:12 3 -> /proc/xen/privcmd
lrwx------  1 root root 64 Aug  4 17:12 4 -> /dev/xen/evtchn
l-wx------  1 root root 64 Aug  4 17:12 5 -> /var/log/xend.log
lrwx------  1 root root 64 Aug  4 17:12 6 -> /proc/xen/privcmd
lrwx------  1 root root 64 Aug  4 17:12 7 -> socket:[58017]
lrwx------  1 root root 64 Aug  4 17:12 8 -> /proc/xen/privcmd
lrwx------  1 root root 64 Aug  4 17:12 9 -> socket:[58028]




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 139] xend stops logging entirely after startup, bugzilla-daemon <=