How is Coda's performance these days? I remember some benchmarks being
posted back in the 4.x days.
I just got a new 8GB disk; I may end up allocating a big of it to a
Coda FS. I'm doing a demo of Coda in a couple of weeks; hopefully by
the time I get to the demo, I will know enough about Coda
I've sent two messages from work with a '[EMAIL PROTECTED]' address
in the last two weeks or so which never showed up on the list. Is there
some sort of policy to only allow list subsribers to send to the list? If
so, why haven't I recieved some sort of bounce message?
I know I must still be subs
[EMAIL PROTECTED] said:
| I've sent two messages from work with a '[EMAIL PROTECTED]'
| address in the last two weeks or so which never showed up on the list.
| Is there some sort of policy to only allow list subsribers to send to
| the list? If so, why haven't I recieved some sort of bounce mess
This is kind of ambitious. Why don't you first play with it a bit, to
find out if it suits your needs.
- Peter -
Kevin Day wrote:
>
> If this isn't the correct place to ask these questions, let me know and i'll
> repost elsewhere. :)
>
> I'm currently using NFS in a smallish network, where
Many months ago (9/16/1998), Troy Benjegerdes said:
| Untarring linux-2.1.121 on nfs:
| 4.18user 3.97system 1:14.74elapsed 10%CPU (0avgtext+0avgdata 0maxresident)k
| 0inputs+0outputs (3163major+9197minor)pagefaults 0swaps
|
| Untarring linux-2.1.121 on coda:
| 4.44user 2.84system 1:00:55elapsed
I have two servers set up to evaluate coda, and for performance reasons,
I put the RVM log partition on a separate disk (along with some extra
swap partitions). This disk, being rather old, then proceeded to crash
about two weeks ago.
Because of coda's replication (and limited use of the machine
Other than digging around in /usr/coda/etc/console, is there a quick way
to check what the write disconnect status of a coda client is?
I'd like to be able to use some 'cfs status' command to tell me if I'm
fully connected, write disconnected, and possibly what the status of
reintegration is.
Ma
Robert V. Baron wrote:
>
> I have forwarded Aurora's mail to codalist@telemann which is the general
> discussion/information list for more comments.
>
I have coda-5.0.1 (with krb5 support) on a Linux-2.2 system, and if I
run
/etc/rc.d/init.d/venus stop, the CODA modules remains loaded with 1
'us
[EMAIL PROTECTED] said:
| I have coda-5.0.1 (with krb5 support) on a Linux-2.2 system, and if I
| run /etc/rc.d/init.d/venus stop, the CODA modules remains loaded with
| 1 'use' reference, thus making it impossible to unload the module or
| start another venus.
| This requires a reboot to make t
[EMAIL PROTECTED] said:
| I have two servers set up to evaluate coda, and for performance
| reasons, I put the RVM log partition on a separate disk (along with
| some extra swap partitions). This disk, being rather old, then
| proceeded to crash about two weeks ago.
|
| Because of coda's replica
[EMAIL PROTECTED] said:
| Other than digging around in /usr/coda/etc/console, is there a quick
| way to check what the write disconnect status of a coda client is?
| I'd like to be able to use some 'cfs status' command to tell me if I'm
| fully connected, write disconnected, and possibly what the
On Mon, 15 Mar 1999 [EMAIL PROTECTED] wrote:
>
> Many months ago (9/16/1998), Troy Benjegerdes said:
>
> | Untarring linux-2.1.121 on nfs:
> | 4.18user 3.97system 1:14.74elapsed 10%CPU (0avgtext+0avgdata 0maxresident)k
> | 0inputs+0outputs (3163major+9197minor)pagefaults 0swaps
> |
> | Untarrin
[EMAIL PROTECTED] said:
| Write disconnected operation is definitely faster, but still has bugs
| in it.. I've ended up reinitializeing servers twice because of it. ;)
I haven't seen any good server corruption for a while now... and we've
been discussing/working on a change in the kernel-venus p
13 matches
Mail list logo
