• Is there a bandwidth scheduler ?
• Does Bitflu support Multifile-Torrents ?
• My upload never reaches 'maxup' !
• chroot(/tmp) failed : Operation not permitted at ./bitflu.pl line 432
• Bitflu does not startup: 'bitflu.pl refuses to run with uid 0 (= root)
• Bitflu panics with 'Unhandled state : Too many open files'
• Is it possible to have the 'commited' directory on a different filesystem / harddisk ?

Yes, just use the schedule command to create a new job to change the value of upspeed:
schedule set upspeed 25 80@0015-0620
This would cause bitflu to change upspeed to 80 from 00:15 until 06:20, otherwise the value will be set to 25. See help schedule for more information.

---

Yes. Use the 'files' command

---

Bitflu may not be able to fillup the internal upload buffer, consider increasing the 'writepriority' option.
It's also possible that unchoked peers choose to not download anything: Bitflu reserves some bandwidth for each unchoked peer.

---

Using the chroot option forces you to startup bitflu as root. Also set 'runas_uid' and 'runas_gid' in order to have bitflu switch its own uid/gid after chroot()'ing itself.

---

There is no reason to run bitflu with uid/gid 0 (= as root user) unless you are using the 'chroot' option.
If you are using the 'chroot' option, you'll also have to set 'runas_uid' and 'runas_gid'. Bitflu will then switch its own uid/gid after chroot()'ing itself.

---

Bitflu will open up to ~450 tcp-sockets, this may exceed the default limit of your kernel. (OpenBSD 3.9 defaults to 64).
Use ulimit -n to view the current value. Setting the limit to 512 using ulimit -n 512 should solve the problem.

---

No. Mounting filesystems under workdir will break bitflu. If you need to free space use a cronjob to move stuff from the commited directory to a different disk.

---