<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ksyncer_daemon in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ksyncer-daemon/m-p/3914820#M285107</link>
    <description>&lt;BR /&gt;Have you applied the latest synce patch?  I believe it is PHKL_31500&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 18 Dec 2006 16:22:09 GMT</pubDate>
    <dc:creator>DCE</dc:creator>
    <dc:date>2006-12-18T16:22:09Z</dc:date>
    <item>
      <title>ksyncer_daemon</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ksyncer-daemon/m-p/3914818#M285105</link>
      <description>rx7620 11.23 - when system gets busy, I notice the ksyncer_daemon process using large amounts of cpu cycles. It seems to be adding to the load of the server and can't seem to find out what it does or why it is so high in the processing queue.  Have seen it using 180% (w%) of a cpu - something we never saw with the PA-RISC N class.  This is a fairly highend 8way machine with 32gig of memory and don't understand why this process should be interfering with regular production.  Any comments would be appreciated.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 18 Dec 2006 14:52:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ksyncer-daemon/m-p/3914818#M285105</guid>
      <dc:creator>Stan PIetkiewicz_1</dc:creator>
      <dc:date>2006-12-18T14:52:23Z</dc:date>
    </item>
    <item>
      <title>Re: ksyncer_daemon</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ksyncer-daemon/m-p/3914819#M285106</link>
      <description>Hi Colin,&lt;BR /&gt;&lt;BR /&gt;I wasn't able to find any overt references to ksyncer_daemon.  However, a little investigation reveals that it handles syncing for file system integrity.&lt;BR /&gt;&lt;BR /&gt;From the following output, you can see that its ppid is 0 (swapper), and that it is started after lvmschedd but before lvmdevd.&lt;BR /&gt;&lt;BR /&gt;# uname -mr&lt;BR /&gt;B.11.23 9000/800&lt;BR /&gt;# ps -ef | awk '{if ($3==0) print}' | sort -n -k2&lt;BR /&gt;    root     0     0  0  Dec  8  ?         0:21 swapper&lt;BR /&gt;    root     1     0  0  Dec  8  ?         0:09 init&lt;BR /&gt;    root     2     0  0  Dec  8  ?         0:18 vhand&lt;BR /&gt;    root     3     0  0  Dec  8  ?         0:48 statdaemon&lt;BR /&gt;    root     4     0  0  Dec  8  ?         0:04 unhashdaemon&lt;BR /&gt;    root     8     0  0  Dec  8  ?         0:00 kmemdaemon&lt;BR /&gt;    root     9     0  0  Dec  8  ?         0:00 ioconfigd&lt;BR /&gt;    root    10     0  0  Dec  8  ?         0:36 nfsktcpd&lt;BR /&gt;    root    11     0  0  Dec  8  ?         0:00 autofskd&lt;BR /&gt;    root    12     0  0  Dec  8  ?         0:00 lvmkd&lt;BR /&gt;    root    13     0  0  Dec  8  ?         0:00 lvmkd&lt;BR /&gt;    root    14     0  0  Dec  8  ?         0:00 lvmkd&lt;BR /&gt;    root    15     0  0  Dec  8  ?         0:00 lvmkd&lt;BR /&gt;    root    16     0  0  Dec  8  ?         0:00 lvmkd&lt;BR /&gt;    root    17     0  0  Dec  8  ?         0:00 lvmkd&lt;BR /&gt;    root    18     0  0  Dec  8  ?         0:00 lvmschedd&lt;BR /&gt;    root    19     0  0  Dec  8  ?         1:04 ksyncer_daemon&lt;BR /&gt;    root    20     0  0  Dec  8  ?         0:01 lvmdevd&lt;BR /&gt;    root    21     0  0  Dec  8  ?         0:00 lvmattachd&lt;BR /&gt;    root    22     0  0  Dec  8  ?         7:54 pagetableinit_daemon&lt;BR /&gt;    root    23     0  0  Dec  8  ?         0:00 supsched&lt;BR /&gt;    root    24     0  0  Dec  8  ?         0:00 strmem&lt;BR /&gt;    root    25     0  0  Dec  8  ?         0:00 strweld&lt;BR /&gt;    root    26     0  0  Dec  8  ?         0:00 strfreebd&lt;BR /&gt;    root    27     0  0  Dec  8  ?         0:06 progressdaemon&lt;BR /&gt;    root    28     0  0  Dec  8  ?         0:00 ttisr&lt;BR /&gt;    root    29     0  0  Dec  8  ?         0:00 ipmid&lt;BR /&gt;    root    36     0  0  Dec  8  ?         1:21 schedcpu&lt;BR /&gt;    root    37     0  0  Dec  8  ?         0:06 pagezerod&lt;BR /&gt;    root    38     0  0  Dec  8  ?         0:26 smpsched&lt;BR /&gt;    root    39     0  0  Dec  8  ?         0:26 smpsched&lt;BR /&gt;    root    40     0  0  Dec  8  ?         0:00 sblksched&lt;BR /&gt;    root    41     0  0  Dec  8  ?         0:00 sblksched&lt;BR /&gt;    root    42     0  0  Dec  8  ?         0:00 kend&lt;BR /&gt;    root    48     0  0  Dec  8  ?        17:01 vxfsd&lt;BR /&gt;    root    67     0  0  Dec  8  ?         0:00 rng&lt;BR /&gt;&lt;BR /&gt;See syncer(1M) for more information.&lt;BR /&gt;&lt;BR /&gt;PCS</description>
      <pubDate>Mon, 18 Dec 2006 15:57:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ksyncer-daemon/m-p/3914819#M285106</guid>
      <dc:creator>spex</dc:creator>
      <dc:date>2006-12-18T15:57:31Z</dc:date>
    </item>
    <item>
      <title>Re: ksyncer_daemon</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ksyncer-daemon/m-p/3914820#M285107</link>
      <description>&lt;BR /&gt;Have you applied the latest synce patch?  I believe it is PHKL_31500&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 18 Dec 2006 16:22:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ksyncer-daemon/m-p/3914820#M285107</guid>
      <dc:creator>DCE</dc:creator>
      <dc:date>2006-12-18T16:22:09Z</dc:date>
    </item>
    <item>
      <title>Re: ksyncer_daemon</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ksyncer-daemon/m-p/3914821#M285108</link>
      <description>Thanks for the comments ... will check the patches and let you know how it goes.</description>
      <pubDate>Thu, 28 Dec 2006 13:16:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ksyncer-daemon/m-p/3914821#M285108</guid>
      <dc:creator>Stan PIetkiewicz_1</dc:creator>
      <dc:date>2006-12-28T13:16:12Z</dc:date>
    </item>
    <item>
      <title>Re: ksyncer_daemon</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ksyncer-daemon/m-p/3914822#M285109</link>
      <description>Hi ... did some checking and seems patches are uptodate.  PHKL_31500 is there as well as PHKL_32055.  Any suggestions?  Seems that when there is a significant load on the server - high I/O as well, this process climbs to the top and consumes way more than we expect it to.&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Mon, 08 Jan 2007 10:20:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ksyncer-daemon/m-p/3914822#M285109</guid>
      <dc:creator>Stan PIetkiewicz_1</dc:creator>
      <dc:date>2007-01-08T10:20:36Z</dc:date>
    </item>
  </channel>
</rss>

