*Synopsis*: pkill fails on native and sn1 branded zones
CR 6793120 changed on Feb 25 2009 by <User 1-5Q-3253>
=== Field ============ === New Value ============= === Old Value =============
Integrated in Build snv_109
Status 10-Fix Delivered 8-Fix Available
====================== =========================== ===========================
*Change Request ID*: 6793120
*Synopsis*: pkill fails on native and sn1 branded zones
Product: solaris
Category: shell
Subcategory: korn93
Type: Defect
Subtype:
Status: 10-Fix Delivered
Substatus:
Priority: 3-Medium
Introduced In Release: solaris_nevada
Introduced In Build: snv_106
Responsible Engineer: <User 1-5Q-12274>
Keywords: oss-request, oss-sponsor
=== *Description* ============================================================
Running the zone testsuite v1.70 during snv_106 test campaign in ON_PIT,
testcase pkill_001 failed on native and sn1 branded zones but passed on lnx
zones.
This is new to this build, testcase passed on all kinds of branded zones in
snv_105.
Testcase pkill_001 starts sleep commands in the background in a local zone :
zlogin -l root sauce-z2 /usr/bin/sleep 128301 &
And then tries to pkill them as follow :
pkill -z 2 -f "^/usr/bin/sleep 128301"
However this does not succeed
The same is reproducible manually :
<email address omitted>:...ts/z_func_other/1.70,19/source# pkill -z 2 -f
"^/usr/bin/sleep 128301" <email address
omitted>:...ts/z_func_other/1.70,19/source# echo $?
1
<email address omitted>:...ts/z_func_other/1.70,19/source# pkill -z 2
"^/usr/bin/sleep" <email address
omitted>:...ts/z_func_other/1.70,19/source# echo $?
1
<email address omitted>:...ts/z_func_other/1.70,19/source# pkill -z 2 "sleep"
<email address
omitted>:...ts/z_func_other/1.70,19/source# echo $?
1
Here are the log for this testcase :
Test_Case_Start| 235982 tests/os/functional/pkill_1/pkill_001 | 19:12:32 0 |
stdout|
stdout| ASSERTION pkill_001_native: From the global zone, "pkill -z valid_zoneid
stdout| valid_pattern" run as root, will kill all processes, regardless of
stdout| user, in zone "valid_zoneid" that match "valid_pattern".
stdout| pkill_001: starting 3 processes as user zones1 in zone mitikas-a-z3
stdout| pkill_001: starting 3 processes as user zones1 in zone mitikas-a-z1
stdout| pkill_001: starting 3 processes as user zones1 in zone mitikas-a-z4
stdout| pkill_001: starting 3 processes as user zones1 in zone mitikas-a-z2
stdout| pkill_001: starting 3 processes as user zones1 in zone global
stdout| pkill_001: starting 3 processes as user root in zone mitikas-a-z3
stdout| pkill_001: starting 3 processes as user root in zone mitikas-a-z1
stdout| pkill_001: starting 3 processes as user root in zone mitikas-a-z4
stdout| pkill_001: starting 3 processes as user root in zone mitikas-a-z2
stdout| pkill_001: starting 3 processes as user root in zone global
stderr| pkill_001: Ignore all "Terminated" information - this is expected
stderr| pkill_001 : pkill returned unexpected non-zero return value
stderr| Terminated
stderr| Terminated
stderr| Terminated
stderr| Terminated
stderr| Terminated
stderr| Terminated
stderr| Terminated
Test_Case_End| 235982 tests/os/functional/pkill_1/pkill_001 | UNRESOLVED |
19:12:35 0 |
*** (#1 of 1): 2009-01-13 13:20:19 GMT+00:00 <User 1-237X3Z>
=== *Public Comments* ========================================================
Appears to be due to ksh93 update:
# ptree 101659
100557 /usr/lib/ssh/sshd
100924 /usr/lib/ssh/sshd
100925 /usr/lib/ssh/sshd
100945 -ksh
100951 sh
101659 zlogin -l root nv /usr/bin/sleep 3600
101660 sh -c /usr/bin/sleep 3600
101663 /usr/bin/ksh93 /usr/bin/sleep 3600
sleep is a ksh93 script, so it's "-f" full process name is:
/usr/bin/ksh93 /usr/bin/sleep 3600
This happens for the global zone as well:
$ /usr/bin/sleep 3600&
$ pkill sleep
THe above does not kill the sleep, which appears as a process named
/usr/bin/ksh93 /usr/bin/sleep 3600
Same goes for
$ sleep 3600 &
$ pkill sleep
/usr/bin/sleep is a ksh93 script which calls it's own sleep builtin.
function.
For scripts which implement "sleep-for-syncronization" hackary, this could
easily break them.
*** (#1 of 1): 2009-01-14 00:47:44 GMT+00:00 <User 1-5Q-7415>
=== *Workaround* =============================================================
=== *Additional Details* =====================================================
Targeted Release: solaris_nevada
Commit To Fix In Build: snv_109
Fixed In Build: snv_109
Integrated In Build: snv_109
Verified In Build:
See Also: 6619428, 6800929
Duplicate of:
Hooks:
Hook1:
Hook2:
Hook3:
Hook4:
Hook5: <email address omitted>
Hook6: <email address omitted>
Program Management:
Root Cause: Poor Feature Interaction
Fix Affects Documentation: No
Fix Affects Localization: No
=== *History* ================================================================
Date Submitted: 2009-01-13 13:20:19 GMT+00:00
Submitted By: <User 1-237X3Z>
Status Changed Date Updated Updated By
6-Fix Understood 2009-02-05 13:16:16 GMT+00:00 <User 1-5Q-12274>
7-Fix in Progress 2009-02-12 14:51:58 GMT+00:00 <User 1-5Q-12274>
8-Fix Available 2009-02-13 17:31:43 GMT+00:00 <User 1-5HNZ8F>
10-Fix Delivered 2009-02-25 18:29:50 GMT+00:00 <User 1-5Q-3253>
=== *Service Request* ========================================================
Impact: Significant
Functionality: Primary
Severity: 2
Product Name: solaris
Product Release: solaris_nevada
Product Build: snv_106
Operating System: snv_106
Hardware: generic
Submitted Date: 2009-01-13 13:20:19 GMT+00:00
=== *Multiple Release (MR) Cluster* - 0 ======================================
