06-01-2009
Can we have a calculation on the size that breaks even with a transfer from checking to saving and vice versa. For instance, if the average transfer is 100.000 bits, it should be charged with the same amount as starting one thread (or replying to a thread), which is 200 or 0.2% (or 100 at 0.1%). We need to see some break-even type of calculations which also show what we want the users to encourage to do: post messages, reply to messages, solve problems?
I also think some of the awards are quite high: for instance rating threads is 50 bits. Are we encouraging users to rate threads?
Last edited by figaro; 06-01-2009 at 04:23 AM..
6 More Discussions You Might Find Interesting
1. What is on Your Mind?
In case you did not know about this, and are a twitter user, here is the link to the forum twitter channel:
http://twitter.com/unixlinux
We currently have 406 followers...... (0 Replies)
Discussion started by: Neo
0 Replies
2. What is on Your Mind?
We are experimenting with a new project board to help forum members make extra cash; because we have some very talented members, why not make some extra cash working from your computer. See toolbar at bottom of page.
Any ideas or comments?
... (0 Replies)
Discussion started by: Neo
0 Replies
3. Post Here to Contact Site Administrators and Moderators
We added a new way to advertise (to guests and non-registered users) directly on the forums:
Advertise directly with The UNIX and Linux Forums
https://www.unix.com/members/1-albums112-picture605.png
Companies and individuals can buy display ads directly and submit their display ads... (0 Replies)
Discussion started by: Neo
0 Replies
4. How to Post in the The UNIX and Linux Forums
Hi ,
i am a new user to this forum can anyone please help me in navigation for this forum.
also when i am trying to open any thread i am getting below error.
Bad Request
Your browser sent a request that this server could not understand.]
Thanks. (1 Reply)
Discussion started by: nkchand
1 Replies
5. Post Here to Contact Site Administrators and Moderators
We work hard to make The UNIX and Linux Forums one of the best UNIX and Linux knowledge sources on the net. The site is certainly one of the top UNIX and Linux Q&A sites on the web. In order to provide certain members the best quality account services, you can now get some great extra features by... (2 Replies)
Discussion started by: Neo
2 Replies
6. What is on Your Mind?
Forum Moderation @UNIX.com | The UNIX and Linux Forums
https://youtu.be/WGwgibE4Rq0
Also note: In the video I mentioned removing legacy menu items in the ModCP which are unused. I have already "CSS'ed out" the unused menu items:
... (0 Replies)
Discussion started by: Neo
0 Replies
LEARN ABOUT BSD
thr_min_stack
thr_min_stack(3C) Standard C Library Functions thr_min_stack(3C)
NAME
thr_min_stack - return the minimum-allowable size for a thread's stack
SYNOPSIS
cc -mt [ flag... ] file...[ library... ]
#include <thread.h>
size_t thr_min_stack(void);
DESCRIPTION
When a thread is created with a user-supplied stack, the user must reserve enough space to run this thread. In a dynamically linked execu-
tion environment, it is very hard to know what the minimum stack requirments are for a thread. The function thr_min_stack() returns the
amount of space needed to execute a null thread. This is a thread that was created to execute a null procedure. A thread that does some-
thing useful should have a stack size that is thr_min_stack() + <some increment>.
Most users should not be creating threads with user-supplied stacks. This functionality was provided to support applications that wanted
complete control over their execution environment.
Typically, users should let the threads library manage stack allocation. The threads library provides default stacks which should meet the
requirements of any created thread.
thr_min_stack() will return the unsigned int THR_MIN_STACK, which is the minimum-allowable size for a thread's stack.
In this implementation the default size for a user-thread's stack is one mega-byte. If the second argument to thr_create(3C) is NULL, then
the default stack size for the newly-created thread will be used. Otherwise, you may specify a stack-size that is at least THR_MIN_STACK,
yet less than the size of your machine's virtual memory.
It is recommended that the default stack size be used.
To determine the smallest-allowable size for a thread's stack, execute the following:
/* cc thisfile.c -lthread */
#define _REENTRANT
#include <thread.h>
#include <stdio.h>
main() {
printf("thr_min_stack() returns %u
",thr_min_stack());
}
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|MT-Level |MT-Safe |
+-----------------------------+-----------------------------+
SEE ALSO
attributes(5), standards(5)
SunOS 5.10 12 May 1998 thr_min_stack(3C)