<?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: kill -1 in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/kill-1/m-p/5063093#M94412</link>
    <description>Hey&lt;BR /&gt;&lt;BR /&gt;you can use it for the trap command. how syslogd it handles you see in the previous posts.&lt;BR /&gt;&lt;BR /&gt;here a silly example:&lt;BR /&gt;$ cat trapexp.sh&lt;BR /&gt;#!/usr/bin/ksh&lt;BR /&gt;&lt;BR /&gt;trap "echo 'killed'" 1&lt;BR /&gt;&lt;BR /&gt;while true ; do&lt;BR /&gt;echo blah&lt;BR /&gt;sleep 5&lt;BR /&gt;done&lt;BR /&gt;&lt;BR /&gt;$ ./trapexp.sh&lt;BR /&gt;blah&lt;BR /&gt;blah&lt;BR /&gt;blah&lt;BR /&gt;killed #here i do a "kill -1 pid_of_trapexp.sh from an other session&lt;BR /&gt;blah&lt;BR /&gt;&lt;BR /&gt;hope this helps&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;</description>
    <pubDate>Wed, 15 Aug 2007 10:03:03 GMT</pubDate>
    <dc:creator>Oviwan</dc:creator>
    <dc:date>2007-08-15T10:03:03Z</dc:date>
    <item>
      <title>kill -1</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kill-1/m-p/5063089#M94408</link>
      <description>Hello guys1&lt;BR /&gt;&lt;BR /&gt;I'm using B.11.11 U 9000/800.&lt;BR /&gt;&lt;BR /&gt;Please, how can explain what the effect to the command below: I read the man of the kill but I didn't understand.&lt;BR /&gt;&lt;BR /&gt;kill -1 `cat /var/run/syslog.pid`&lt;BR /&gt;&lt;BR /&gt;What's happens with the syslog process?&lt;BR /&gt;Please could someone give me a help?&lt;BR /&gt;&lt;BR /&gt;Thanks!</description>
      <pubDate>Wed, 15 Aug 2007 09:37:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kill-1/m-p/5063089#M94408</guid>
      <dc:creator>cfeitosa</dc:creator>
      <dc:date>2007-08-15T09:37:42Z</dc:date>
    </item>
    <item>
      <title>Re: kill -1</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kill-1/m-p/5063090#M94409</link>
      <description>This cause syslogd to reread configuration: &lt;BR /&gt;&lt;BR /&gt;"To make syslogd, re-read its configuration file, send it a HANGUP signal: &lt;BR /&gt;&lt;BR /&gt;kill -HUP `cat /var/run/syslog.pid` "&lt;BR /&gt;&lt;BR /&gt;See man page for more.&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;ivan</description>
      <pubDate>Wed, 15 Aug 2007 09:47:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kill-1/m-p/5063090#M94409</guid>
      <dc:creator>Ivan Krastev</dc:creator>
      <dc:date>2007-08-15T09:47:18Z</dc:date>
    </item>
    <item>
      <title>Re: kill -1</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kill-1/m-p/5063091#M94410</link>
      <description>You need to check the man page for syslogd.  There it tells you that you can make syslogd re-read it's configuration file by sending it a hangup signal, which is exactly what "kill -1 `cat /var/run/syslog.pid`" does.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Wed, 15 Aug 2007 09:47:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kill-1/m-p/5063091#M94410</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2007-08-15T09:47:23Z</dc:date>
    </item>
    <item>
      <title>Re: kill -1</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kill-1/m-p/5063092#M94411</link>
      <description>Thanks!&lt;BR /&gt;&lt;BR /&gt;I undestood!</description>
      <pubDate>Wed, 15 Aug 2007 09:56:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kill-1/m-p/5063092#M94411</guid>
      <dc:creator>cfeitosa</dc:creator>
      <dc:date>2007-08-15T09:56:45Z</dc:date>
    </item>
    <item>
      <title>Re: kill -1</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kill-1/m-p/5063093#M94412</link>
      <description>Hey&lt;BR /&gt;&lt;BR /&gt;you can use it for the trap command. how syslogd it handles you see in the previous posts.&lt;BR /&gt;&lt;BR /&gt;here a silly example:&lt;BR /&gt;$ cat trapexp.sh&lt;BR /&gt;#!/usr/bin/ksh&lt;BR /&gt;&lt;BR /&gt;trap "echo 'killed'" 1&lt;BR /&gt;&lt;BR /&gt;while true ; do&lt;BR /&gt;echo blah&lt;BR /&gt;sleep 5&lt;BR /&gt;done&lt;BR /&gt;&lt;BR /&gt;$ ./trapexp.sh&lt;BR /&gt;blah&lt;BR /&gt;blah&lt;BR /&gt;blah&lt;BR /&gt;killed #here i do a "kill -1 pid_of_trapexp.sh from an other session&lt;BR /&gt;blah&lt;BR /&gt;&lt;BR /&gt;hope this helps&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;</description>
      <pubDate>Wed, 15 Aug 2007 10:03:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kill-1/m-p/5063093#M94412</guid>
      <dc:creator>Oviwan</dc:creator>
      <dc:date>2007-08-15T10:03:03Z</dc:date>
    </item>
    <item>
      <title>Re: kill -1</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kill-1/m-p/5063095#M94414</link>
      <description>You can convert bogus kill numbers to intelligible names by listing all signals using "kill -l".&lt;BR /&gt;&lt;BR /&gt;So the proper command would be:&lt;BR /&gt;# kill -HUP $(&amp;lt; /var/run/syslog.pid)&lt;BR /&gt;&lt;BR /&gt;(Oops lost the slash)</description>
      <pubDate>Thu, 16 Aug 2007 00:44:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kill-1/m-p/5063095#M94414</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2007-08-16T00:44:00Z</dc:date>
    </item>
  </channel>
</rss>

