Issue with logical operator using SetEnvIF in OHS

We have a requirement to set constant value in ssl.conf (OHS) based on Request_URI & referrer. For example, if (Request_URI=/forms/base/login) and (Referer=http://example.com), then we need to set variable value with 1. Similarly we some more conditions. I am trying to use 'SetEnvIf', but it is not allowing to use logical operations (and, or, &, |).
Can any let us know in resolving issues?

Just to confuse matters, this problem is intermittent and I haven't been able to successfully replicate it in our Test environment.
That would seem to indicate something else was going on in the DB that was interfering with the clear, but the logs aren't showing any errors, locks, etc that could have caused the problem.

Similar Messages

Performance issues with Logic Pro 9

Hi,
I'm experiencing quite big performance issues with Logic Pro 9:
bad midi timing and sync, user interface is kinda slowing and less reactive, ...
Mac Pro 2x2.26 Ghz Quad, 4Gb ram, early 2009, shipped with 10.5.6 now upgraded to 10.5.8
Should I upgrade to 10.6.2?
Thanx

Hi,
I'm using the same machine ...
I never get any performance issues
I bought my mac in March 2009 and I was ben ready to work in less that 3 days without issue...
so more details about your setup are required to answare!
4GB ram???
I suggest to check your ram!!!
Ram must be compatible with Xeon Nehalem Try specification!
if you add 1GB of ram from nor clear manufactor.. i suggest to disconnect the addition 1GB RAM
G

I am having major issues with Logic 8 and want to reinstall.

I am having a lot of issues with Logic 8 and want to do a re-install. What is the procedure and what do I need to uninstall first. I need to be careful, because I don't want to affect my Logic 7.
Any suggestions?

What problems?
The first thing to do is trash the preferences. As far as affecting Logic 7, once you install 8, 7 is "forgotten" about. I'm assuming your L8 is a real version, not a "borrowed from the interweb" one.

Regular expression evaluation with logical operator

Hi All,
I am bit confuse with expression evaluation with logical operator. I am trying to understand below expression.
eXa.getTrue() && eXa.getFalse() || eXa.getFalse() && eXa.getTrue() || eXa.getFalse() comes as false and True Count: 1 False Count: 3
As per understanding it should be true with True Count: 1 False Count: 3
it should execute 1st getTrue() and then 1stGetFalse() and then 2nd getfalse() and should skip 2nd getTrue() and execute 3rd fetFalse()
eXa.getTrue() && eXa.getTrue() || eXa.getFalse() && eXa.getTrue() || eXa.getFalse() comes as true and True Count: 2 False Count: 0
As per understanding it should be true with True Count: 3 False Count: 0
it should execute 1st 2 getTrue() and skip 1st getFalse() and then execute 3rd getTrue() and skip last getFalse().
eXa.getTrue() || eXa.getFalse() && eXa.getFalse() || eXa.getTrue() && eXa.getFalse() comes as true and True Count: 1 False Count: 0
As per understanding it should be true with True Count: 2 False Count: 2
it should execute 1st getTrue() and skip 1st getFalse() and then execute 2nd getFalse() and then execute 2nd getTrue() and then 3rd getFalse()
Please help me to understand above expressions.
Here is the methods definition:
private boolean getTrue() {
          trueCount++;
          boolean retrunValue = 4 > 3;
          return retrunValue;
private boolean getFalse() {
          falseCount++;
          boolean retrunValue = 3 > 4;
          return retrunValue;
Thanks for ur help

>
adding parenthesis to make order of ops more obvious. adding "?" to show un-executed calls.
(eXa.getTrue() && eXa.getFalse()) || (eXa.getFalse() && eXa.getTrue()) || eXa.getFalse() comes as false and True Count: 1 False Count: 3
(T && F) = F
(F && ?) = F
(F) = F
F || F || F = F
(eXa.getTrue() && eXa.getTrue()) || (eXa.getFalse() && eXa.getTrue()) || eXa.getFalse() comes as true and True Count: 2 False Count: 0
(T && T) = T
(? && ?) = ?
(?) = ?
T || ? || ? = T
eXa.getTrue() || (eXa.getFalse() && eXa.getFalse()) || (eXa.getTrue() && eXa.getFalse()) comes as true and True Count: 1 False Count: 0
(T) = T
(? && ?) = ?
(? && ?) = ?
T || ? || ? = T

Compatibility issue with developer 6i using (64 bit) OS

Hi All,
I am using oracle 9iR2 (32 bit) on Linux Red Hat (32 bit) with developer 6i. Now i want to upgrade OS Red Hat (64 bit) and migrate database 10gR2 (64 bit).Is there any compatibility issue with developer 6i using 64 bit Red Hat OS / Oracle Database ?
Thanks

Is there any compatibility issue with developer 6i using 64 bit Red Hat OS / Oracle Database ?
No, as long as developer 6i is at least patch 16. We use it.

Metronome click issue with Logic 8

Hello.
I'm having a strange issue with Logic 8 where the first click after hitting play or record is lower in volume than the rest of the clicks and sometimes isn't there at all - every subsequent click sounds fine. I have checked the metronome preferences and made sure the bar click is the same velocity as the beat click. I've double checked my entire configuration to see if there is a problem somewhere and everything seems to be right. I figured this might be just a bug but I wanted to post this to make sure.
Any ideas on how to fix this?
Here is the configuration I'm working with which has all the latest drivers and updates:
Mac Pro 3.2 GHz 8-core Intel
Mac OS 10.5.2
14 GB RAM
Logic Pro 8
Apogee Ensemble
Trilogy with the Intel wrapper (this might be pertinent)

You need to add more RAM.

Issue with parallel operation of SAP NW SSO 2.0 and SNC Client Encryption (Logon Groups)

Hi!
One of our customers is using the SNC Client Encryption solution to ensure encryption using SNC (based on Kerberos Technology) for their SAP GUI Dialog connections. They have lots of SAP backends DEV, QAS, PRD all with the SNC Client Encryption SNC Lib installed. The profile parameter snc/identity/as contains the following value: p:CN=SAP/<ServiceAccount>@<DOMAIN>.
Example: p:CN=SAP/[email protected]
The customer is using one AD Service Account "SNCServiceUser" with one registered SPN "SAP/SNCServiceUser" for all systems (yes, this is not recommended... but the case).
Important: All users use group entries in the SAP Logon (saplogin.ini). Means, for SAP logon the SNC name can not be manually configured on the SAP Front End. With group logons, the application server's SNC name is dynamically requested by the message server each time a SAP GUI connection is started. The SNC Name is greyed out in this case as dynamically obtained from the applications servers profile parameter snc/identity/as.
Now our customer implements SAP NetWeaver Single Sign-On 2.0 within his landscape. Based on the Secure Login Server 2.0 (SP3) he likes to use X.509 based authentication to his AS ABAP backends using SAP GUI SNC while others still use SNC Client Encryption.
Replacing the SNC Library on the AS ABAP
The Secure Login Library 2.0 (SP3) has been installed on one of the ABAP systems and the SNC Client Encryption SNC Library (which is based on SSO 1.0) is no longer used, thus we changed the parameter snc/gssapi_lib to point to the new SNC library. We removed the old PSE.ZIP containing the keytab and created the new SAPSNCSKERB.PSE incl. the keytab and proper credentials. To ensure parallel operation, we kept the snc/identity/as value as is = p:CN=SAP/[email protected].
After restarting the system with initialized Secure Login Library 2.0, still the SNC client encryption works fine for existing users.
The problem
We created on the Secure Login Server an SNC certificate for the AS ABAP which has the following X.509 Distinguised Name Fomat: CN=SAP/[email protected] This is to avoid having to change the snc/identity/as to an "real" X.509 DN which would lead to non-working SNC Client Encryption for all the other users using SAP GUI and logon groups.
As soon as we install the PSE via STRUST on the system the SNC Client Encryption solution stops working with error „Server refuses kerberos key exchange“.
As part of an pilot implementation we have installed Secure Login Client 2.0 (SP3) on some test PCs. The test PC with SLC is able to perform Single Sign-On with SNC based on X.509 (incl. Encryption) to the ABAP system.
Seems the SAP System now only tries to do X.509 based authentication thus key exchange fails. The problem is, we cannot change the snc/identity/as value because of the logon groups. If we were able to do so, we would in any case set the server identity to X.509 DN and in addition create the SAPSNCSKERB.PSE incl. keytab. This should work, as confirmed by SAP see this post.
Any ideas how to solve this and have both solutions in parallel?
Appreciate any help.
Regards,
Carsten

Hi all,
we was able to fix the issue. It was an issue with the customers cluster configuration and the $SECUDIR variable. This tricky issue leads to non working or sporadic working SNC Client Encryption...
This was how the configuration looks before:
Environment variable $SECUDIR is defined:
"/ABCDEF<SID>/usr/sap/<SID>/DVEBMGSxx/sec“
sapgenpse seclogin -l -v
running seclogin with USER="<SID>adm"
Credentials for username '<SID>adm':
0 (LPS:OFF):
         (LPS:OFF): /ABCDEF<SID>/usr/sap/<SID>/DVEBMGSxx/sec/SAPSNCSKERB.pse
1 (LPS:OFF):
         (LPS:OFF): /usr/sap/<SID>/DVEBMGSxx/sec/SAPSNCS.pse
After changing the $SECUDIR to "/usr/sap/<SID>/DVEBMGSxx/sec“ and re-creating the credentials, it worked like a charm.
As a result of this we can confirm, this configuration and SNC Client Encryption works with CommonCryptoLib in parallel to the SSO configuration.
And Valerie was right with 2. SLC starting from V. 1.0 SP2 PL3 was able to convert the CN= part of the SNC Name into an SPN, was my mistake. In addition SNC Client Encryption starting from Version 1 SP1 PL1 does this also.. just to make this clear
Thread closed hope this helps someone
Carsten

Oxygen25 midi issue with Logic 9.1.8

Just recently bought a Oxygen25 midi keyboard controller and I'm running it on the latest macbook pro (10.8.2), with logic pro 9.1.8 - 32 bit. Everything functions on the midi keyboard expect the 8 controller Knobs, no matter what I do I can't get the knobs to recorded functions into Logic. I've download the latest directlink mode drivers and installed them correctly, I've gone into controller assignment window using learn mode button and assigned each knob to certain functions, cutoff, speed on ES2 synth. When you play the keyboard and turn the knobs the sounds work fine (no problem) but when I hit recorded the sounds play but will not record into logic. The pitch bend shows and works in the hyper editor and the All velocities but there's nothing coming through on the rest (Volume, Pan, Modulation, Ch. Pressure, Poly Program and Program.
I'm I missing something really simple here or does this keyboard just not work with logic ? I've been on M-audio website and there's no solutions, I've also looked on discussion board but had no luck. Any advice or help would be welcome, please help me get back into making some music.
Found this article on M-audio but not sure what it relates to - (These knobs map to control the track volume for the currently active bank of eight tracks)
Thank-you
Andrew

I'm having the exact same issue with the Multipressor in Logic (but not in Waveburner). What gives?

Having some weird issues with logic 8

i am almost Positive! that i pushed some buttons or selected something to mess it up, i would be indebted to anyone who can help me with like three issues i'm having
I run my M-audio mobile pre into logic and am having these issues:
#1. track 1 and two seem to be tied together even though i select mono tracks... so i need to leave track two blank otherwise it interferes with whatever is on track one. and on the bar where i drag the loop i was using it has two O's that make like a vinn diagram symbol.
#2. the volume controll (the bottom left fader one) can increase the Db but not decrease...
#3 through my headphones the signal only comes out the right side. i am inputting my guitar/vox into the right input on the mobile pre, but i thought if the tracks were mono, it wouldn't matter.
please please please help, i need to get recording soon!
thanks.

i figured out the volume issue, with the weird stereo track, i needed to adjust it on both tracks (even though one was empty haha duh)

Presonus Faderport - issues with Logic?

Hi - I've just gotten the Presonus single-channel faderport - great and affordable little product; however, it's causing a strange issue in Logic despite their claim that it's compatible, and their tech support has led me to one possible issue I wanted to ask about...the faderport sends data exclusively on MIDI channel 1 apparently, which makes sense because when it's hooked up, any external sampler I have will not play out of channel 1. This seems like a fatal flaw - they said it could have to do with my environment setup, ie if any instrument has its MIDI port set to all...why would that be? I have multi-instruments that have each channel going to 1 of 16, and there are some old icons in the environment of instruments no longer attached that say "All". Otherwise, seems fine.
Any ideas of whether this is my Logic environment setup or the faderport? The faderport by the way is set up and installed correctly.
thanks!

update on this issue - I've found that the faderport can be installed and work without bottle-necking MIDI channel 1 and anything external that transmits on it only if it is installed while any external samplers are shut down and booted up after faderport installation.
however, the issue with it losing its connection to Logic quite frequently still occurs way too often making it too frustrating to use thus far- would love to know if anyone's figured out how to eliminate this problem and use the unit productively, because it has potential to be a great studio addition.
thanks, look forward to any feedback-

Focusrite Scarlett 2i2 clapping and crackling issues with Logic Pro x new iMac 27"

Hi, I have just purchased a brand new iMac and downloaded Logic Pro x, I also purchased the Focusrite Scarlett 2i2 interface. I have downloaded the drivers from the focusrite website and everything is set up, when I plug in guitar or mic I get really bad clapping and crackling to the point where the sound cuts out altogether. I have changed buffer size and sample rates and everything else I can think of but nothing seems to fix the problem. I also deleted the 2i2 drivers and logic and reinstalled them both but still have the same issue, when I record using the iMac built in mic everything is fine so it's deffinately something to do with the interface. I am waiting to hear back from Focusrite tech help. Does anyone else have this problem? Any help would be appreciated.

I'm having a similar issue which might indicate that the problem is not your interface.
Yesterday I migrated all my stuff from my 2009 iMac to a brand new iMac 27", and when I did a quick test to play back some old projects in Logic there was loads of annoying clicks and pops. My interface is a Roland Octa-Capture.
I also noticed some weird CPU spikes from time to time, which I never had on my older, much less powerful iMac...

Latency Issue with Logic 8 and Reason

Hello evryone,
I am using Logic 8 with Reason 3.0 and have a Digi 002 as my audio interface. I have set up an aux track in Logic with inputs being RW:L/R and outputs 1&2. When I open Reason after I have opened Logic and go to play an instrument in reason there is massive latency. I've tried messing with the plu-in delay compensation in Logic's prefs. and it didn't have any effect. When I use this set-up with Protools it works beautifully and I don't have any issues like this. Does anyone have any answers or suggestions. Thanks, E.M

Hi and thanks for the response. I forgot to mention in my previous post that I have indeed changed the buffer size time and time again and it has not helped. What is going on forum? This seems to be a common problem I am having with Logic. Why is it so easy to have a set up like this in PT but not in Logic. Ever since I bought this program I have had nothing but stupid little problems like this. Apple, what's going on with the design of this program. How can you have so many cool features and yet not have the most basic things work properly? I am at my wits end as I am wasting time with this product and am about to throw it out the window, trash it to other musicians/composers and go back to PT. Really, where is the Apple support team on this?

Having a strange issue with Logic, don't know what to do.

Aright, so I'm having a really weird problem with Logic. It all started about 20 minutes ago. I'm working with 12 midi tracks; all logic instruments. Every first Snare midi note plays extra soft and then every midi note after that plays at its correct velocity. Don't know why. I tried deleting the note and pasting a new and that didn't work so I saved and quit. I then took a look in my console and this is what came up:
11/7/11 12:21:53 AM
bootlog[43]
BOOT_TIME: 1320650503 0
11/7/11 12:22:12 AM
loginwindow[31]
USER_PROCESS: 31 console
11/7/11 12:29:13 AM
loginwindow[31]
DEAD_PROCESS: 31 console
11/7/11 12:29:15 AM
loginwindow[202]
USER_PROCESS: 202 console
11/7/11 1:32:51 AM
loginwindow[202]
DEAD_PROCESS: 202 console
11/7/11 1:32:52 AM
shutdown[2714]
SHUTDOWN_TIME: 1320654772 505951
11/7/11 1:33:14 AM
bootlog[46]
BOOT_TIME: 1320654783 0
11/7/11 1:33:17 AM
loginwindow[35]
USER_PROCESS: 35 console
11/7/11 8:18:59 AM
loginwindow[35]
DEAD_PROCESS: 35 console
11/7/11 8:19:06 AM
loginwindow[349]
USER_PROCESS: 349 console
11/7/11 8:28:02 AM
reboot[1018]
BOOT_TIME: 1320679682 95944
11/7/11 8:28:45 AM
bootlog[51]
BOOT_TIME: 1320679715 0
11/7/11 9:15:22 AM
loginwindow[40]
USER_PROCESS: 40 console
11/7/11 9:56:40 AM
loginwindow[40]
DEAD_PROCESS: 40 console
11/7/11 9:56:48 AM
loginwindow[242]
USER_PROCESS: 242 console
11/7/11 9:59:01 AM
reboot[835]
BOOT_TIME: 1320685141 69936
11/7/11 9:59:29 AM
bootlog[48]
BOOT_TIME: 1320685155 0
11/7/11 10:08:33 AM
loginwindow[37]
USER_PROCESS: 37 console
11/7/11 1:20:53 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/7/11 1:20:57 PM
shutdown[7541]
SHUTDOWN_TIME: 1320697257 332087
11/7/11 1:21:22 PM
bootlog[50]
BOOT_TIME: 1320697269 0
11/7/11 1:21:50 PM
loginwindow[39]
USER_PROCESS: 39 console
11/7/11 2:30:13 PM
loginwindow[39]
DEAD_PROCESS: 39 console
11/7/11 2:30:31 PM
shutdown[1377]
SHUTDOWN_TIME: 1320701431 300114
11/7/11 2:31:00 PM
bootlog[48]
BOOT_TIME: 1320701445 0
11/7/11 2:58:14 PM
loginwindow[37]
USER_PROCESS: 37 console
11/7/11 3:02:19 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/7/11 3:02:20 PM
shutdown[206]
SHUTDOWN_TIME: 1320703340 498493
11/7/11 3:02:42 PM
bootlog[48]
BOOT_TIME: 1320703352 0
11/7/11 4:33:21 PM
loginwindow[37]
USER_PROCESS: 37 console
11/7/11 5:57:24 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/7/11 5:57:24 PM
shutdown[404]
SHUTDOWN_TIME: 1320713844 888171
11/7/11 5:57:58 PM
bootlog[48]
BOOT_TIME: 1320713868 0
11/7/11 5:58:21 PM
loginwindow[37]
USER_PROCESS: 37 console
11/7/11 6:01:48 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/7/11 6:01:48 PM
shutdown[169]
SHUTDOWN_TIME: 1320714108 381468
11/7/11 11:48:22 PM
bootlog[48]
BOOT_TIME: 1320734891 0
11/7/11 11:48:45 PM
loginwindow[37]
USER_PROCESS: 37 console
11/8/11 4:19:03 AM
loginwindow[37]
DEAD_PROCESS: 37 console
11/8/11 4:19:03 AM
shutdown[641]
SHUTDOWN_TIME: 1320751143 318155
11/8/11 8:36:13 AM
bootlog[45]
BOOT_TIME: 1320766559 0
11/8/11 8:36:30 AM
loginwindow[34]
USER_PROCESS: 34 console
11/8/11 8:10:50 PM
loginwindow[34]
DEAD_PROCESS: 34 console
11/8/11 8:10:50 PM
shutdown[183]
SHUTDOWN_TIME: 1320808250 610564
11/8/11 8:12:08 PM
bootlog[48]
BOOT_TIME: 1320808315 0
11/8/11 8:12:22 PM
loginwindow[37]
USER_PROCESS: 37 console
11/8/11 9:44:19 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/8/11 9:44:20 PM
shutdown[385]
SHUTDOWN_TIME: 1320813860 87755
11/9/11 10:30:35 AM
bootlog[48]
BOOT_TIME: 1320859824 0
11/9/11 10:31:05 AM
loginwindow[37]
USER_PROCESS: 37 console
11/9/11 1:01:13 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/9/11 1:01:13 PM
shutdown[292]
SHUTDOWN_TIME: 1320868873 995966
11/9/11 1:02:02 PM
bootlog[48]
BOOT_TIME: 1320868909 0
11/9/11 1:02:15 PM
loginwindow[37]
USER_PROCESS: 37 console
11/9/11 3:13:01 PM
login[5975]
USER_PROCESS: 5975 ttys000
11/9/11 3:13:01 PM
login[5975]
DEAD_PROCESS: 5975 ttys000
11/10/11 5:32:55 AM
loginwindow[37]
DEAD_PROCESS: 37 console
11/10/11 5:32:55 AM
shutdown[6997]
SHUTDOWN_TIME: 1320928375 628779
11/10/11 8:41:31 PM
bootlog[45]
BOOT_TIME: 1320982876 0
11/10/11 8:42:42 PM
loginwindow[34]
USER_PROCESS: 34 console
11/10/11 9:29:47 PM
loginwindow[34]
DEAD_PROCESS: 34 console
11/10/11 9:29:48 PM
loginwindow[180]
USER_PROCESS: 180 console
11/10/11 9:30:20 PM
reboot[283]
BOOT_TIME: 1320985820 923753
11/10/11 9:31:10 PM
bootlog[45]
BOOT_TIME: 1320985858 0
11/10/11 9:31:43 PM
shutdown[98]
SHUTDOWN_TIME: 1320985903 450229
11/11/11 12:05:40 PM
bootlog[45]
BOOT_TIME: 1321038331 0
11/11/11 12:06:10 PM
loginwindow[34]
USER_PROCESS: 34 console
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 5:08:26 PM
kernel
11/12/11 6:01:11 PM
loginwindow[34]
DEAD_PROCESS: 34 console
11/12/11 6:01:11 PM
shutdown[459]
SHUTDOWN_TIME: 1321146071 420746
11/12/11 9:39:44 PM
bootlog[45]
BOOT_TIME: 1321159171 0
11/12/11 9:40:04 PM
loginwindow[34]
USER_PROCESS: 34 console
11/12/11 10:59:25 PM
loginwindow[34]
DEAD_PROCESS: 34 console
11/12/11 10:59:25 PM
shutdown[190]
SHUTDOWN_TIME: 1321163965 560483
11/13/11 12:15:33 AM
bootlog[45]
BOOT_TIME: 1321168520 0
11/13/11 12:15:55 AM
loginwindow[34]
USER_PROCESS: 34 console
11/13/11 2:02:40 AM
loginwindow[34]
DEAD_PROCESS: 34 console
11/13/11 2:02:40 AM
shutdown[324]
SHUTDOWN_TIME: 1321174960 535970
11/13/11 10:54:04 AM
bootlog[45]
BOOT_TIME: 1321206832 0
11/13/11 10:54:19 AM
loginwindow[34]
USER_PROCESS: 34 console
11/13/11 11:02:13 AM
loginwindow[34]
DEAD_PROCESS: 34 console
11/13/11 11:02:13 AM
shutdown[154]
SHUTDOWN_TIME: 1321207333 741020
11/13/11 4:11:30 PM
bootlog[45]
BOOT_TIME: 1321225878 0
11/13/11 4:12:00 PM
loginwindow[34]
USER_PROCESS: 34 console
11/13/11 4:14:40 PM
loginwindow[34]
DEAD_PROCESS: 34 console
11/13/11 4:14:41 PM
shutdown[152]
SHUTDOWN_TIME: 1321226081 279428
11/13/11 4:15:01 PM
bootlog[45]
BOOT_TIME: 1321226090 0
11/13/11 4:15:18 PM
loginwindow[34]
USER_PROCESS: 34 console
11/13/11 4:54:48 PM
loginwindow[34]
DEAD_PROCESS: 34 console
11/13/11 4:54:48 PM
shutdown[178]
SHUTDOWN_TIME: 1321228488 443594
11/13/11 10:11:05 PM
bootlog[45]
BOOT_TIME: 1321247453 0
11/13/11 10:11:39 PM
loginwindow[34]
USER_PROCESS: 34 console
11/14/11 2:34:46 AM
loginwindow[34]
DEAD_PROCESS: 34 console
11/14/11 2:34:47 AM
shutdown[283]
SHUTDOWN_TIME: 1321263287 223296
11/14/11 11:02:03 AM
bootlog[45]
BOOT_TIME: 1321293712 0
11/14/11 11:03:19 AM
loginwindow[34]
USER_PROCESS: 34 console
11/14/11 5:14:25 PM
loginwindow[34]
DEAD_PROCESS: 34 console
11/14/11 5:14:25 PM
shutdown[345]
SHUTDOWN_TIME: 1321316065 545760
11/14/11 5:16:14 PM
bootlog[45]
BOOT_TIME: 1321316165 0
11/14/11 5:16:33 PM
loginwindow[34]
USER_PROCESS: 34 console
11/14/11 5:44:15 PM
loginwindow[34]
DEAD_PROCESS: 34 console
11/14/11 5:44:16 PM
shutdown[187]
SHUTDOWN_TIME: 1321317856 83312
11/15/11 12:48:10 AM
bootlog[45]
BOOT_TIME: 1321343279 0
11/15/11 12:48:38 AM
loginwindow[34]
USER_PROCESS: 34 console
11/15/11 3:26:19 AM
loginwindow[34]
DEAD_PROCESS: 34 console
11/15/11 3:26:19 AM
shutdown[365]
SHUTDOWN_TIME: 1321352779 718218
11/15/11 11:32:51 AM
bootlog[45]
BOOT_TIME: 1321381958 0
11/15/11 11:33:07 AM
loginwindow[34]
USER_PROCESS: 34 console
11/15/11 11:50:40 AM
loginwindow[34]
DEAD_PROCESS: 34 console
11/15/11 11:50:40 AM
shutdown[173]
SHUTDOWN_TIME: 1321383040 949601
11/15/11 3:13:03 PM
bootlog[48]
BOOT_TIME: 1321395171 0
11/15/11 3:13:16 PM
loginwindow[37]
USER_PROCESS: 37 console
11/15/11 3:28:56 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/15/11 3:28:56 PM
shutdown[169]
SHUTDOWN_TIME: 1321396136 717878
11/15/11 3:31:06 PM
bootlog[48]
BOOT_TIME: 1321396254 0
11/15/11 3:31:21 PM
loginwindow[37]
USER_PROCESS: 37 console
11/16/11 2:38:00 AM
loginwindow[37]
DEAD_PROCESS: 37 console
11/16/11 2:38:00 AM
shutdown[1961]
SHUTDOWN_TIME: 1321436280 560702
11/16/11 11:30:09 AM
bootlog[47]
BOOT_TIME: 1321468198 0
11/16/11 11:30:48 AM
loginwindow[36]
USER_PROCESS: 36 console
11/16/11 4:34:51 PM
loginwindow[36]
DEAD_PROCESS: 36 console
11/16/11 4:34:51 PM
shutdown[341]
SHUTDOWN_TIME: 1321486491 583341
11/16/11 4:36:11 PM
bootlog[48]
BOOT_TIME: 1321486559 0
11/16/11 4:36:34 PM
loginwindow[37]
USER_PROCESS: 37 console
11/16/11 9:59:04 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/16/11 9:59:05 PM
shutdown[371]
SHUTDOWN_TIME: 1321505945 161871
11/17/11 12:20:08 AM
bootlog[48]
BOOT_TIME: 1321514397 0
11/17/11 12:20:32 AM
shutdown[106]
SHUTDOWN_TIME: 1321514432 588785
11/17/11 12:21:30 AM
bootlog[48]
BOOT_TIME: 1321514481 0
11/17/11 12:21:45 AM
loginwindow[37]
USER_PROCESS: 37 console
11/17/11 12:39:52 AM
login[174]
USER_PROCESS: 174 ttys000
11/17/11 12:40:12 AM
login[174]
DEAD_PROCESS: 174 ttys000
11/17/11 12:40:15 AM
login[180]
USER_PROCESS: 180 ttys000
11/17/11 12:54:34 AM
login[180]
DEAD_PROCESS: 180 ttys000
11/17/11 2:28:30 AM
loginwindow[37]
DEAD_PROCESS: 37 console
11/17/11 2:28:30 AM
shutdown[331]
SHUTDOWN_TIME: 1321522110 593580
11/17/11 4:37:08 PM
bootlog[48]
BOOT_TIME: 1321573005 0
11/17/11 4:38:49 PM
loginwindow[37]
USER_PROCESS: 37 console
11/17/11 7:39:32 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/17/11 7:39:32 PM
shutdown[386]
SHUTDOWN_TIME: 1321583972 773529
11/18/11 1:41:17 AM
bootlog[48]
BOOT_TIME: 1321605668 0
11/18/11 1:41:40 AM
loginwindow[37]
USER_PROCESS: 37 console
11/18/11 3:48:55 AM
loginwindow[37]
DEAD_PROCESS: 37 console
11/18/11 3:48:55 AM
shutdown[355]
SHUTDOWN_TIME: 1321613335 819965
11/18/11 10:23:51 AM
bootlog[48]
BOOT_TIME: 1321637021 0
11/18/11 10:24:13 AM
loginwindow[37]
USER_PROCESS: 37 console
11/18/11 10:28:27 AM
kernel
11/18/11 10:28:27 AM
kernel
11/18/11 10:28:27 AM
kernel
11/18/11 10:28:27 AM
kernel
11/18/11 10:28:27 AM
kernel
11/18/11 10:28:27 AM
kernel
11/18/11 10:28:27 AM
kernel
11/18/11 10:28:27 AM
kernel
11/18/11 10:28:27 AM
kernel
11/18/11 10:28:27 AM
kernel
11/18/11 2:15:52 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/18/11 2:15:59 PM
shutdown[770]
SHUTDOWN_TIME: 1321650959 323280
11/18/11 2:16:33 PM
bootlog[48]
BOOT_TIME: 1321650971 0
11/18/11 2:16:52 PM
loginwindow[37]
USER_PROCESS: 37 console
11/18/11 6:30:25 PM
loginwindow[37]
DEAD_PROCESS: 37 console
11/18/11 6:30:27 PM
shutdown[1470]
SHUTDOWN_TIME: 1321666227 362936
11/18/11 6:31:47 PM
bootlog[38]
BOOT_TIME: 1321666248 0
11/18/11 6:32:34 PM
loginwindow[26]
USER_PROCESS: 26 console
11/18/11 8:24:46 PM
loginwindow[26]
DEAD_PROCESS: 26 console
11/18/11 8:24:56 PM
shutdown[205]
SHUTDOWN_TIME: 1321673096 424661
11/18/11 8:25:23 PM
bootlog[40]
BOOT_TIME: 1321673108 0
11/18/11 8:26:03 PM
loginwindow[26]
USER_PROCESS: 26 console
11/18/11 8:37:36 PM
loginwindow[26]
DEAD_PROCESS: 26 console
11/18/11 8:37:37 PM
loginwindow[210]
USER_PROCESS: 210 console
11/18/11 8:38:12 PM
reboot[264]
BOOT_TIME: 1321673892 663474
11/18/11 8:38:43 PM
bootlog[40]
BOOT_TIME: 1321673906 0
11/18/11 8:39:06 PM
loginwindow[27]
USER_PROCESS: 27 console
11/18/11 9:45:07 PM
loginwindow[27]
DEAD_PROCESS: 27 console
11/18/11 9:45:08 PM
shutdown[387]
SHUTDOWN_TIME: 1321677908 37081
11/18/11 10:20:09 PM
bootlog[40]
BOOT_TIME: 1321680000 0
11/18/11 10:20:44 PM
loginwindow[28]
USER_PROCESS: 28 console
11/18/11 11:56:22 PM
loginwindow[28]
DEAD_PROCESS: 28 console
11/18/11 11:56:22 PM
shutdown[328]
SHUTDOWN_TIME: 1321685782 469361
11/19/11 5:41:15 AM
bootlog[40]
BOOT_TIME: 1321706467 0
11/19/11 5:42:10 AM
shutdown[99]
SHUTDOWN_TIME: 1321706530 778985
11/19/11 5:49:24 AM
bootlog[40]
BOOT_TIME: 1321706956 0
11/19/11 5:49:52 AM
loginwindow[29]
USER_PROCESS: 29 console
11/19/11 12:35:11 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/19/11 12:35:11 PM
shutdown[658]
SHUTDOWN_TIME: 1321731311 570256
11/19/11 4:26:55 PM
bootlog[40]
BOOT_TIME: 1321745206 0
11/19/11 4:27:31 PM
loginwindow[29]
USER_PROCESS: 29 console
11/19/11 4:49:55 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/19/11 4:49:55 PM
shutdown[214]
SHUTDOWN_TIME: 1321746595 832157
11/19/11 4:50:36 PM
bootlog[40]
BOOT_TIME: 1321746619 0
11/19/11 4:51:00 PM
loginwindow[29]
USER_PROCESS: 29 console
11/19/11 6:34:58 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/19/11 6:34:58 PM
shutdown[266]
SHUTDOWN_TIME: 1321752898 862103
11/20/11 12:48:24 AM
bootlog[40]
BOOT_TIME: 1321775295 0
11/20/11 12:48:50 AM
loginwindow[29]
USER_PROCESS: 29 console
11/20/11 12:50:56 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/20/11 12:50:56 AM
shutdown[190]
SHUTDOWN_TIME: 1321775456 727774
11/20/11 12:51:57 AM
bootlog[40]
BOOT_TIME: 1321775508 0
11/20/11 12:52:15 AM
loginwindow[29]
USER_PROCESS: 29 console
11/20/11 2:44:47 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/20/11 2:44:48 AM
shutdown[287]
SHUTDOWN_TIME: 1321782288 27378
11/20/11 9:40:35 AM
bootlog[40]
BOOT_TIME: 1321807226 0
11/20/11 9:45:38 AM
loginwindow[29]
USER_PROCESS: 29 console
11/20/11 1:10:45 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/20/11 1:10:45 PM
shutdown[376]
SHUTDOWN_TIME: 1321819845 699702
11/20/11 2:47:41 PM
bootlog[40]
BOOT_TIME: 1321825653 0
11/20/11 2:48:05 PM
loginwindow[29]
USER_PROCESS: 29 console
11/21/11 3:18:25 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/21/11 3:18:25 AM
shutdown[738]
SHUTDOWN_TIME: 1321870705 862572
11/21/11 1:41:49 PM
bootlog[40]
BOOT_TIME: 1321908100 0
11/21/11 1:42:31 PM
loginwindow[29]
USER_PROCESS: 29 console
11/21/11 1:45:37 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/21/11 1:45:37 PM
shutdown[199]
SHUTDOWN_TIME: 1321908337 723401
11/21/11 1:46:42 PM
bootlog[40]
BOOT_TIME: 1321908393 0
11/21/11 1:47:01 PM
loginwindow[29]
USER_PROCESS: 29 console
11/21/11 2:47:30 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/21/11 2:47:31 PM
shutdown[221]
SHUTDOWN_TIME: 1321912051 100508
11/21/11 9:57:25 PM
bootlog[40]
BOOT_TIME: 1321937836 0
11/21/11 10:00:25 PM
loginwindow[29]
USER_PROCESS: 29 console
11/21/11 10:05:34 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/21/11 10:05:34 PM
shutdown[197]
SHUTDOWN_TIME: 1321938334 457516
11/21/11 10:05:55 PM
bootlog[40]
BOOT_TIME: 1321938345 0
11/21/11 10:06:14 PM
loginwindow[29]
USER_PROCESS: 29 console
11/21/11 10:36:32 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/21/11 10:36:32 PM
shutdown[249]
SHUTDOWN_TIME: 1321940192 772946
11/22/11 5:47:52 PM
bootlog[40]
BOOT_TIME: 1322009263 0
11/22/11 5:48:18 PM
loginwindow[29]
USER_PROCESS: 29 console
11/22/11 5:57:09 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/22/11 5:57:10 PM
shutdown[180]
SHUTDOWN_TIME: 1322009830 100353
11/22/11 5:57:52 PM
bootlog[40]
BOOT_TIME: 1322009862 0
11/22/11 6:03:27 PM
loginwindow[29]
USER_PROCESS: 29 console
11/22/11 8:17:23 PM
login[262]
USER_PROCESS: 262 ttys000
11/22/11 8:25:20 PM
login[262]
DEAD_PROCESS: 262 ttys000
11/22/11 10:02:20 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/22/11 10:02:20 PM
shutdown[501]
SHUTDOWN_TIME: 1322024540 841538
11/23/11 11:09:36 AM
bootlog[40]
BOOT_TIME: 1322071768 0
11/23/11 11:12:10 AM
loginwindow[29]
USER_PROCESS: 29 console
11/23/11 11:16:40 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/23/11 11:16:40 AM
shutdown[201]
SHUTDOWN_TIME: 1322072200 484093
11/23/11 11:17:01 AM
bootlog[40]
BOOT_TIME: 1322072211 0
11/23/11 11:17:22 AM
loginwindow[29]
USER_PROCESS: 29 console
11/23/11 11:57:01 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/23/11 11:57:01 AM
shutdown[219]
SHUTDOWN_TIME: 1322074621 710897
11/23/11 6:10:29 PM
bootlog[40]
BOOT_TIME: 1322097020 0
11/23/11 6:11:30 PM
shutdown[107]
SHUTDOWN_TIME: 1322097090 157202
11/23/11 6:11:48 PM
bootlog[40]
BOOT_TIME: 1322097100 0
11/23/11 6:12:07 PM
loginwindow[29]
USER_PROCESS: 29 console
11/23/11 6:43:45 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/23/11 6:43:45 PM
shutdown[212]
SHUTDOWN_TIME: 1322099025 671753
11/24/11 3:06:36 AM
bootlog[40]
BOOT_TIME: 1322129187 0
11/24/11 3:07:23 AM
loginwindow[29]
USER_PROCESS: 29 console
11/24/11 3:25:50 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/24/11 3:26:16 AM
shutdown[263]
SHUTDOWN_TIME: 1322130376 181854
11/24/11 3:41:59 PM
bootlog[40]
BOOT_TIME: 1322174510 0
11/24/11 3:42:29 PM
loginwindow[29]
USER_PROCESS: 29 console
11/24/11 5:41:41 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/24/11 5:41:44 PM
shutdown[182]
SHUTDOWN_TIME: 1322181704 304082
11/24/11 5:42:27 PM
bootlog[40]
BOOT_TIME: 1322181730 0
11/24/11 5:42:44 PM
shutdown[107]
SHUTDOWN_TIME: 1322181764 200841
11/25/11 1:06:30 AM
bootlog[40]
BOOT_TIME: 1322208382 0
11/25/11 1:07:20 AM
loginwindow[29]
USER_PROCESS: 29 console
11/25/11 2:02:05 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/25/11 2:02:05 AM
shutdown[243]
SHUTDOWN_TIME: 1322211725 412106
11/25/11 12:19:23 PM
bootlog[40]
BOOT_TIME: 1322248755 0
11/25/11 12:19:50 PM
loginwindow[29]
USER_PROCESS: 29 console
11/25/11 12:21:18 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/25/11 12:21:19 PM
shutdown[185]
SHUTDOWN_TIME: 1322248879 181508
11/25/11 12:21:40 PM
bootlog[40]
BOOT_TIME: 1322248891 0
11/25/11 12:21:58 PM
loginwindow[29]
USER_PROCESS: 29 console
11/25/11 2:31:25 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/25/11 2:31:25 PM
shutdown[388]
SHUTDOWN_TIME: 1322256685 817758
11/25/11 3:55:28 PM
bootlog[40]
BOOT_TIME: 1322261718 0
11/25/11 3:55:55 PM
loginwindow[29]
USER_PROCESS: 29 console
11/25/11 3:57:10 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/25/11 3:57:11 PM
shutdown[159]
SHUTDOWN_TIME: 1322261831 182162
11/25/11 5:12:01 PM
bootlog[40]
BOOT_TIME: 1322266311 0
11/25/11 5:12:20 PM
loginwindow[29]
USER_PROCESS: 29 console
11/25/11 5:22:48 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/25/11 5:22:48 PM
shutdown[196]
SHUTDOWN_TIME: 1322266968 596246
11/25/11 5:50:55 PM
bootlog[40]
BOOT_TIME: 1322268646 0
11/25/11 6:04:42 PM
loginwindow[29]
USER_PROCESS: 29 console
11/26/11 12:28:03 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/26/11 12:28:03 AM
shutdown[527]
SHUTDOWN_TIME: 1322292483 989128
11/26/11 9:56:40 AM
bootlog[40]
BOOT_TIME: 1322326592 0
11/26/11 10:16:17 AM
loginwindow[29]
USER_PROCESS: 29 console
11/26/11 10:18:14 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/26/11 10:18:14 AM
shutdown[203]
SHUTDOWN_TIME: 1322327894 987763
11/26/11 10:18:35 AM
bootlog[40]
BOOT_TIME: 1322327907 0
11/26/11 10:18:54 AM
loginwindow[29]
USER_PROCESS: 29 console
11/27/11 12:51:27 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/27/11 12:51:28 AM
shutdown[592]
SHUTDOWN_TIME: 1322380288 289445
11/27/11 8:33:25 PM
bootlog[40]
BOOT_TIME: 1322451196 0
11/27/11 8:34:08 PM
loginwindow[29]
USER_PROCESS: 29 console
11/27/11 8:35:39 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/27/11 8:35:39 PM
shutdown[158]
SHUTDOWN_TIME: 1322451339 576729
11/27/11 8:35:59 PM
bootlog[40]
BOOT_TIME: 1322451350 0
11/27/11 8:36:16 PM
loginwindow[29]
USER_PROCESS: 29 console
11/28/11 2:20:14 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/28/11 2:20:17 AM
shutdown[330]
SHUTDOWN_TIME: 1322472017 680079
11/28/11 11:32:31 AM
bootlog[40]
BOOT_TIME: 1322505141 0
11/28/11 11:33:01 AM
loginwindow[29]
USER_PROCESS: 29 console
11/28/11 6:34:50 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/28/11 6:34:50 PM
shutdown[473]
SHUTDOWN_TIME: 1322530490 514177
11/29/11 12:49:32 AM
bootlog[40]
BOOT_TIME: 1322552963 0
11/29/11 12:51:15 AM
loginwindow[29]
USER_PROCESS: 29 console
11/29/11 4:40:24 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/29/11 4:40:24 AM
shutdown[609]
SHUTDOWN_TIME: 1322566824 951691
11/29/11 9:00:52 AM
bootlog[40]
BOOT_TIME: 1322582442 0
11/29/11 9:01:10 AM
loginwindow[29]
USER_PROCESS: 29 console
11/29/11 9:44:53 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/29/11 9:44:53 AM
shutdown[176]
SHUTDOWN_TIME: 1322585093 264673
11/29/11 10:54:01 AM
bootlog[40]
BOOT_TIME: 1322589232 0
11/29/11 10:54:17 AM
loginwindow[29]
USER_PROCESS: 29 console
11/29/11 11:12:07 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/29/11 11:12:07 AM
shutdown[162]
SHUTDOWN_TIME: 1322590327 902267
11/29/11 8:32:30 PM
bootlog[40]
BOOT_TIME: 1322623940 0
11/29/11 8:32:50 PM
loginwindow[29]
USER_PROCESS: 29 console
11/29/11 9:35:59 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/29/11 9:35:59 PM
shutdown[188]
SHUTDOWN_TIME: 1322627759 382014
11/29/11 9:36:59 PM
bootlog[40]
BOOT_TIME: 1322627810 0
11/29/11 9:39:05 PM
loginwindow[29]
USER_PROCESS: 29 console
11/29/11 9:39:35 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/29/11 9:39:35 PM
shutdown[158]
SHUTDOWN_TIME: 1322627975 625235
11/29/11 9:42:45 PM
bootlog[40]
BOOT_TIME: 1322628157 0
11/29/11 9:43:17 PM
loginwindow[29]
USER_PROCESS: 29 console
11/30/11 2:15:04 AM
loginwindow[29]
DEAD_PROCESS: 29 console
11/30/11 2:15:04 AM
shutdown[440]
SHUTDOWN_TIME: 1322644504 701322
11/30/11 3:26:41 PM
bootlog[40]
BOOT_TIME: 1322691992 0
11/30/11 3:27:50 PM
loginwindow[29]
USER_PROCESS: 29 console
11/30/11 3:29:39 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/30/11 3:29:40 PM
shutdown[188]
SHUTDOWN_TIME: 1322692180 264860
11/30/11 3:30:15 PM
bootlog[40]
BOOT_TIME: 1322692207 0
11/30/11 3:30:41 PM
loginwindow[29]
USER_PROCESS: 29 console
11/30/11 3:52:12 PM
loginwindow[29]
DEAD_PROCESS: 29 console
11/30/11 3:52:12 PM
shutdown[194]
SHUTDOWN_TIME: 1322693532 474756
11/30/11 9:18:14 PM
bootlog[40]
BOOT_TIME: 1322713080 0
11/30/11 9:18:46 PM
loginwindow[29]
USER_PROCESS: 29 console
12/1/11 5:57:47 AM
loginwindow[29]
DEAD_PROCESS: 29 console
12/1/11 5:57:47 AM
shutdown[869]
SHUTDOWN_TIME: 1322744267 855950
12/1/11 9:52:39 AM
bootlog[40]
BOOT_TIME: 1322758350 0
12/1/11 9:53:01 AM
loginwindow[29]
USER_PROCESS: 29 console
12/1/11 10:24:02 AM
loginwindow[29]
DEAD_PROCESS: 29 console
12/1/11 10:24:03 AM
shutdown[234]
SHUTDOWN_TIME: 1322760243 279103
12/1/11 10:24:22 AM
bootlog[40]
BOOT_TIME: 1322760253 0
12/1/11 10:24:41 AM
loginwindow[29]
USER_PROCESS: 29 console
12/1/11 10:41:30 AM
loginwindow[29]
DEAD_PROCESS: 29 console
12/1/11 10:41:31 AM
shutdown[240]
SHUTDOWN_TIME: 1322761291 172303
12/1/11 10:48:01 AM
bootlog[40]
BOOT_TIME: 1322761671 0
12/1/11 10:50:46 AM
loginwindow[29]
USER_PROCESS: 29 console
12/1/11 11:44:03 AM
loginwindow[29]
DEAD_PROCESS: 29 console
12/1/11 11:44:03 AM
shutdown[244]
SHUTDOWN_TIME: 1322765043 549953
12/2/11 12:51:18 AM
bootlog[40]
BOOT_TIME: 1322812270 0
12/2/11 12:51:49 AM
loginwindow[29]
USER_PROCESS: 29 console
12/2/11 2:06:17 AM
loginwindow[29]
DEAD_PROCESS: 29 console
12/2/11 2:06:17 AM
shutdown[245]
SHUTDOWN_TIME: 1322816777 845146
12/2/11 10:48:28 AM
bootlog[40]
BOOT_TIME: 1322848098 0
12/2/11 10:48:50 AM
loginwindow[29]
USER_PROCESS: 29 console
12/3/11 1:49:58 AM
loginwindow[29]
DEAD_PROCESS: 29 console
12/3/11 1:49:59 AM
shut

Why did you put up with all those issues for a year?

Anyone else having an issue with TCP connections using iCloud for Windows?

Hi,
Before I asked this question, I did wait to see if any related questions came up, but none did, so I submit it now.
On my admittedly older laptop running Windows 7 64b Home, I've run into difficulties with the iCloud for Windows app to the extent that I had to uninstall it.
It would that, as my laptop was running, in the background, iCloudServices.exe would endlessly iterate TCP connections, which, while not actively sending or receiving any data, after some hours would number over 100 instances, taking up resources, and grinding my laptop's WiFi connection to a grindingly slow pace. I ended up, within the app, turning off everything, iCloud Drive and Photos, (I never used bookmarks), but still this would continue to occur.
I contacted Apple Support, explaining what was going on, and they stated they only dealt with IOS and gave me a Microsoft Support number. When I called Microsoft support, I came more and more to the realization that the issue was specifically with the iCloud for Windows app, as that was the only software that was endlessly creating and not closing TCP connections as it was. How was Microsoft supposed to solve an issue with Apple code?
So I called Apple back, whereupon they insisted it was a Microsoft issue. I explained other cloud services installed on the same computer were not having the same issue, it was unique to ICloudServices.exe. They stated they only dealt with IOS. I stated I purchased an iPad Air less than 7 months ago, and was trying to run iCloud in support of that. They again stated they only dealt with IOS, and suggested I again try Microsoft. I asked them if it was reasonable to expect Microsoft to solve issues with Apple code? They said regardless, there was zero support offered for anything having to do with Windows, and all I could do was uninstall the app, which I did, though that did not feel very satisfactory to me. My thinking is, if Apple writes a Windows app in support of their hardware, they should offer support for it.
Anyway, I was just wondering, is this an issue unique to me? or have others experienced a similar issue? I found this issue by opening the Windows Resource Monitor, looking under the Networking tab, and scrolling through the TCP Connections section to find 100+ concurrent iCloudServices.exe instances listed, whereas even Chrome, with multiple tabs and extensions, topped out at around 20.
My one month old Desktop, DYI, sports a solid Asus 1150 MoBo, i7-4790k cpu, 16GB Ram, and an EVGA GTX 970 video card. I list some specs only to illustrate this computer has no hardware issues in comparison to my long in tooth laptop. On this desktop, running Win 8.1 Pro 64b, at least as many, identifiably Apple, background service TCP connections are created even compared to Chrome, regardless of many tabs being open, many extensions, and even some related apps. Adobe does not even come close, though I run the full CC subscription. On this new computer, running Windows 8.1 Pro 64b, there are currently over 50 TCP connections and loopbacks that do not identify themselves, with just a - for the Image, and PID. With the experience on my laptop, I wonder how many of these are generated by Apple software, if not specifically iCloud software?
The frustrating aspect of these connections is they seem in no way active, While the Chrome and Adobe connections can be seen to be transferring data, as long as I am not running iTunes, or so have my iPad actually plugged in, it seems 99% of the time these iCloudServices.exe connections are just taking up ports, neither sending nor receiving any data discernable to me under the Processes with Network Activity, or Network Activity lists, both displayed in the same window as the TCP Connections in the Windows Resource Monitor.
Though I am fairly ignorant as regards coding, it seems as if there is no call to close a connection, very specifically, iCloudServices.exe, when it is no longer needed, and the next time a connection is needed, a new one is opened, rather than accessing the one previously opened. The only other reason I could imagine this might be occurring is if my Norton Internet Security software might mask and/or block the port after a certain time of inactivity.
Anyone out there have any ideas or advice about this? Thanks in advance.

Thanks jared,
I'm still dealing with this issue through Apple. Some time after I posted this, I contacted Apple again. They did start a case up for me, as I was experiencing the same behavior on two different machines, with two different versions of Windows.
So far it remains unsolved. I've logged iClouds for Windows on my desktop, which is brand new, then logged for awhile after completely uninstalling Norton Security Suite, depending on the Microsoft security for some time, and finally logged after I uninstalled iCloud for Windows, restarted, installed a clean download, and connected using a completely different test account, which Apple set up for me. None of this made any difference. Looking at the logs, it seems every 10 minutes, iCloudServices.exe creates a new TCP connection to confirm I'm using less than 5GB on iCloud, (which I am by a good margin, using less than 2GB), it seems this connection is not closed, and when the next iteration rolls around 10 minutes later, a new TCP connection is created. I come very close to having 6 TCP connections created per hour, until I restart my computer. This works out to... 6 x 24 = 144/day.
Perhaps the article you posted will shed some further light on this. I'm thinking seeing the state of the connection through netstats, at the least, could help.
For the last week, I've been putting a hold on further logging, as Apple wants me to create a new user account on one of my computers, install iCloud for Windows there, and log it running in the other account. This however basically means I cannot use my computer for a fair number of hours, and I've been busy enough with work the past week that I haven't the time or energy to afford to set this up and run it. I've had need of my computers too much for the past week.

Issues with pagination when using Adobe table with Web dynpro for ABAP

Hi All,
I am facing strange issue with table text.
I have three cols in table, one is of type Char255 and other two cols are of type string.
The text in the col 1 is displayed perfectly but in other two cols of type string whenever we have pagination the text in table is getting truncated and in next page new row starts.
Could you please tell me the settings that will enable flowing of text in the row of table to next page.
Thanks,
Arti.

Check the properties of the text field you use for those columns (if you want to control it on this level) or check the same attribute for the row subform (one level up control): "allow page break within content".
Regards Otto
p.s.: we all have deadlines... and manage to pay something back. Think about it.

Issue with logical operator using SetEnvIF in OHS

Similar Messages

Maybe you are looking for