sm-sorcery-bugs AT lists.ibiblio.org
Subject: Bugs for Sorcery are reported here
List archive
[SM-Sorcery-Bugs] [Bug 13315] /dev/null is in the install log (WAS: "fuse: failed to daemonize program")
- From: bugzilla-daemon AT bugs.sourcemage.org
- To: sm-sorcery-bugs AT lists.ibiblio.org
- Subject: [SM-Sorcery-Bugs] [Bug 13315] /dev/null is in the install log (WAS: "fuse: failed to daemonize program")
- Date: 9 Dec 2006 19:08:26 -0000
http://bugs.sourcemage.org/show_bug.cgi?id=13315
------- Additional Comments From iuso AT sourcemage.org 2006-12-09 13:08 -------
BTW: Even though this bug is only about /dev/null appearing in the install
log, dispel certainly does delete it (and then creates a normal file of that
name with '> /dev/null'). Here's some output from right after the lftp cast
(comment #12):
# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 2006-12-09 20:57 /dev/null
# dispel lftp
Dispelled spell: lftp
# ls -l /dev/null
-rw-r--r-- 1 root root 313 2006-12-09 20:57 /dev/null
# cat /dev/null
libapi(1333): "sedit - /^lftp:.*:.*:.*:.*:.*$/D /var/state/sorcery/depends"
libstate(1333): "remove_sub_depends@324" "/var/state/sorcery/sub_depends"
"lftp" ".*"
libapi(1333): "sedit - /^lftp:.*:.*/D /var/state/sorcery/sub_depends"
libhash(1333): "hash_put() - VARIABLE_NAME=HASH_ALL_DISPELS_lftp_, data=yes"
Would you like me to file a separate bug about this behavior? Or is it
unnecessary to make dispel watch out for /dev/null because it shouldn't be in
the install log in the first place? Is that what you meant?
--
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
-
[SM-Sorcery-Bugs] [Bug 13315] /dev/null is in the install log (WAS: "fuse: failed to daemonize program"),
bugzilla-daemon, 12/08/2006
- <Possible follow-up(s)>
- [SM-Sorcery-Bugs] [Bug 13315] /dev/null is in the install log (WAS: "fuse: failed to daemonize program"), bugzilla-daemon, 12/09/2006
- [SM-Sorcery-Bugs] [Bug 13315] /dev/null is in the install log (WAS: "fuse: failed to daemonize program"), bugzilla-daemon, 12/09/2006
- [SM-Sorcery-Bugs] [Bug 13315] /dev/null is in the install log (WAS: "fuse: failed to daemonize program"), bugzilla-daemon, 12/09/2006
- [SM-Sorcery-Bugs] [Bug 13315] /dev/null is in the install log (WAS: "fuse: failed to daemonize program"), bugzilla-daemon, 12/09/2006
- [SM-Sorcery-Bugs] [Bug 13315] /dev/null is in the install log (WAS: "fuse: failed to daemonize program"), bugzilla-daemon, 12/09/2006
- [SM-Sorcery-Bugs] [Bug 13315] /dev/null is in the install log (WAS: "fuse: failed to daemonize program"), bugzilla-daemon, 12/09/2006
- [SM-Sorcery-Bugs] [Bug 13315] /dev/null is in the install log (WAS: "fuse: failed to daemonize program"), bugzilla-daemon, 12/10/2006
- [SM-Sorcery-Bugs] [Bug 13315] /dev/null is in the install log (WAS: "fuse: failed to daemonize program"), bugzilla-daemon, 12/10/2006
- [SM-Sorcery-Bugs] [Bug 13315] /dev/null is in the install log (WAS: "fuse: failed to daemonize program"), bugzilla-daemon, 12/13/2006
- [SM-Sorcery-Bugs] [Bug 13315] /dev/null is in the install log (WAS: "fuse: failed to daemonize program"), bugzilla-daemon, 12/16/2006
- [SM-Sorcery-Bugs] [Bug 13315] /dev/null is in the install log (WAS: "fuse: failed to daemonize program"), bugzilla-daemon, 12/17/2006
- [SM-Sorcery-Bugs] [Bug 13315] /dev/null is in the install log (WAS: "fuse: failed to daemonize program"), bugzilla-daemon, 12/20/2006
Archive powered by MHonArc 2.6.24.