[02:41:23] --- Russ has left: Disconnected
[04:02:12] --- dev-zero@jabber.org_ has become available
[04:17:47] --- SecureEndpoints has left: Replaced by new connection
[07:14:41] --- SecureEndpoints has become available
[07:17:26] --- dragos.tatulea has become available
[07:28:26] --- dev-zero@jabber.org_ has left
[07:46:35] --- edgester has become available
[07:48:03] --- edgester has left
[08:47:47] <dragos.tatulea> hi
[08:50:39] <shadow@gmail.com/owlDF21EF7C> hi
[08:50:53] <dragos.tatulea> Does afs_daemon operate on several threads or is it just one background thread doing misc stuff.
[08:51:35] <shadow@gmail.com/owlDF21EF7C> er. assuming i understan question, multiple threads
[08:51:56] <dragos.tatulea> :)
[08:53:07] <dragos.tatulea> I want to make a thread that updates files that have been modified somewhere else (for pinning).
[08:57:33] <shadow@gmail.com/owlDF21EF7C> why a thread and not just another service done by the periodic jobs?
[08:58:12] <dragos.tatulea> aka daemon?
[09:02:25] <shadow@gmail.com/owlDF21EF7C> the checkserver daemon, basically
[09:06:00] <dragos.tatulea> Can I ask for a small description of each thread in the afs client. You explained a few months ago, but I can't find it and can't remember either.
[09:17:46] <shadow@gmail.com/owlDF21EF7C> um. doesn't the linux thing that creates kthreads have a short
description of each?
[09:18:30] <dragos.tatulea> let me see
[09:22:02] <dragos.tatulea> there's in afsd_thread a switch that multiplexes: START_RXCALLBACK, START_AFS, START_BKG, START_TRUNCDAEMON, START_CS, START_RXEVENT_DAEMON, RX_LISTENERDAEMON
[09:22:12] <dragos.tatulea> those should be the threads
[09:22:15] <dragos.tatulea> right?
[09:22:53] <shadow@gmail.com/owlDF21EF7C> yes
[09:23:08] <shadow@gmail.com/owlDF21EF7C> but there should be a text description (short) of each in there too
[09:23:44] <dragos.tatulea> yeah
[09:23:47] <dragos.tatulea> un UKERNEL
[09:23:52] <dragos.tatulea> s/un/in
[09:32:11] <dragos.tatulea> who builds aklog?
[09:32:11] <dragos.tatulea> ?
[09:32:50] --- dev-zero@jabber.org_ has become available
[09:33:53] <shadow@gmail.com/owlDF21EF7C> you do.
[09:34:19] <dragos.tatulea> apparently not
[09:34:34] <dragos.tatulea> I missed a config option maybe
[09:34:39] <shadow@gmail.com/owlDF21EF7C> configured --with-krb5 and it greed with you?
[09:35:11] <dragos.tatulea> I passed --with-krb5-config=/path/to/krb5-config
[09:35:40] <shadow@gmail.com/owlDF21EF7C> --with-krb5-conf would probably work better
[09:35:57] <dragos.tatulea> yeah
[09:36:01] <dragos.tatulea> thanks
[09:46:08] <dragos.tatulea> one more question for you, shadow
[09:47:25] <dragos.tatulea> Where/when is the client notified by the server that a certain file has changed?
[10:47:17] <jhutz@jis.mit.edu/owl> I will, when it's ready
[10:50:45] <jhutz@jis.mit.edu/owl> The server notifies the client that something has changed by breaking a
callback, but only if there _is_ an outstanding callback.  The break
happens via an RPC to RXAFSCB_CallBack(), which is handled in
src/afs/afs_callback.c.  But you must be very careful what you do there;
the CM only has one thread handling RXAFSCB RPC's, and it must not block
unnecessarily.
[11:10:23] --- dev-zero@jabber.org_ has left
[12:58:22] --- Russ has become available
[14:21:59] --- edgester has become available
[15:40:15] --- dev-zero@jabber.org_ has become available
[17:04:27] <edgester> stevenjenkins: Hi Steven
[17:45:40] --- edgester has left: Replaced by new connection
[17:45:40] --- edgester has become available
[18:13:52] --- dev-zero@jabber.org has left
[18:14:01] --- edgester has left
[18:17:04] --- edgester has become available
[18:18:41] --- dev-zero@jabber.org has become available
[18:44:15] --- edgester has left
[22:28:36] --- Russ has left: Disconnected