Bugs for Sorcery are reported here

[bugzilla-daemon AT bugs.sourcemage.org]

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


Thomas Orgis <sobukus AT sourcemage.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|size of TMPFS should be     |TMPFS should be tunable
                   |possible to set in DETAILS  |(DETAILS and default)




--- Comment #2 from Thomas Orgis <sobukus AT sourcemage.org>  2011-05-20 
03:41:17 ---
I'm running a hacked libgrimoire now that does that:

function real_mk_source_dir() {

  debug  "libgrimoire" "Running mk_source_dir() on $SOURCE_DIRECTORY"

  local NEW_DIR=$1
  local NEW_DIR=${NEW_DIR:=$SOURCE_DIRECTORY}

  local SIZE=$2
  local SIZE=${SIZE:=$TMPFS_SIZE}
  local SIZE=${SIZE:=1g}

  if  [  -n  "$NEW_DIR"  ];  then

    rm_source_dir  $NEW_DIR
    mkdir -p $NEW_DIR  &&
    if  [[  "$TMPFS" == on  ]] || [[ "$TMPFS_FORCE" == on ]]; then
      mount  -o  size=$SIZE,nr_inodes=1m  -t  tmpfs  tmpfs  $NEW_DIR
    fi
  fi

}

So, I introduced TMPFS_SIZE and TMPFS_FORCE as global configuration parameters
(set in /etc/sorcery/local/config). I think this would be a first valuable
step: Let the user configure how big she wants her tmpfs directories to be by
default and also allow to override any TMPFS=off in spell's DETAILS, as those
are written with the idea of less than 8 G of RAM being available, I presume.

What I did not hack was integration of those settings into the sorcery
configuration dialog, but that shouldn't be the showstopper. What do you think
about the basic approach?

-- 
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.