Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 13315] /dev/null is in the install log (WAS: "fuse: failed to daemonize program")

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • 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: 11 Dec 2006 00:04:16 -0000

http://bugs.sourcemage.org/show_bug.cgi?id=13315





------- Additional Comments From dmlb2000 AT gmail.com 2006-12-10 18:04 -------
Okay I think I know what's going on here with staged install off it uses the
old
installwatch tracking code to get the installed file list. However,
installwatch
tends to touch /dev/null quite a bit in its tracking logs (castfs doesn't at
all). When the !filter code was also added to devel sorcery (will be explained
in the future with some docs) there was code that appended /dev/null onto a
grep
list having /dev/null in both of the RID_LIST and the NOT_RID_LIST in the
filter() and filter_in() functions in libsorcery is causing /dev/null to be
tracked.

as for the fuse filesystem not daemonizing I think its because /dev/null went
missing since I use the mount call to run castfs and mount.fuse is a shell
script.

Could you please verify by running the following with and without /dev/null?
(Please set the STAGE_LOCATION MOUNT_LOCATION CASTFS_LOGFILE locations
appropriately).

export CASTFS_LOGFILE="$(pwd)/cast.logfile"
export CASTFS_DBGLVL="255"
mount -t fuse -o
"stage=$STAGE_LOCATION,defaults,ignore=/tmp,ignore=/usr/src,ignore=/var/state/sorcery,ignore=/etc/sorcery"
castfs "$MOUNT_LOCATION"

--
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.




Archive powered by MHonArc 2.6.24.

Top of Page