On Fri, 2008-12-19 at 18:52 -0500, Brian Marshall wrote: > if I was on a Windows box would that correspond to C:\Temp?
Yes, it should. > If I leave off the Logfile, will it just go to activity log as normal? No, it won't go to activity.log, because that is the log file of the daemon, not the glue. The glue could be executed on a machine that is different from the daemon, hence the glue can't log output in the daemon log file. > On Fri, Dec 19, 2008 at 6:34 PM, Kristis Makris <[email protected]> > wrote: > > Yes, I believe it goes to /tmp/scmbug.glue (or something like that) > > > > On Fri, 2008-12-19 at 17:26 -0500, Brian Marshall wrote: > >> I modified the following line in glue.conf > >> > >> #log4perl.category.Glue = WARN, AppWarn, AppRest #original > >> value > >> log4perl.category.Glue = DEBUG, AppWarn, AppRest, Logfile > >> > >> My activitiy.log in var/log/scmbug did not show anymore information. > >> Does Logfile cause the output to go to a different place? > >> > >> > >> On Fri, Dec 19, 2008 at 4:47 PM, Kristis Makris <[email protected]> > >> wrote: > >> > Thanks, this is informative. > >> > > >> > On Fri, 2008-12-19 at 15:53 -0500, Brian Marshall wrote: > >> >> 2008/12/19 10:22:05 Scmbug WARN> > >> >> Process.pm:886:Scmbug::Daemon::Process::process_activity_verify - > >> >> 127.0.0.1:6699 Processing an 'activity_verify' for bug id '2' from SCM > >> >> user 'marshallb' > >> > > >> >> 2008/12/19 10:22:25 Scmbug WARN> > >> >> Process.pm:867:Scmbug::Daemon::Process::process_activity_commit - > >> >> 127.0.0.1:6701 Processing an 'activity_commit' for bug id '2' from SCM > >> >> user 'marshallb' > >> > > >> > It seems that after the activity_verify it takes the Scmbug glue 20 > >> > seconds before it issues the activity_commit. This is unusual. > >> > > >> > Try raising 'logging' in glue.conf by modifying this line: > >> > > >> > log4perl.category.Glue = WARN, AppWarn, AppRest > >> > > >> > into > >> > > >> > log4perl.category.Glue = DEBUG, AppWarn, AppRest, Logfile > >> > > >> > > >> > Try to commit after this change and you should see a verbose log of the > >> > steps Scmbug takes, along with timestamps. This should help pinpoint the > >> > problem. > >> > > >> >> > Also, can you check how long it takes to commit if you disable the > >> >> > glue > >> >> > in glue.conf ? > >> >> > >> >> With enabled=>0 the commit happens in < 2 seconds. > >> > > >> > This is clearly a Scmbug issue then. > >> > > >> > http://bugzilla.mkgnu.net/show_bug.cgi?id=1308 > >> > > >
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
