Displaying 6 results from an estimated 6 matches for "sigblk".
Did you mean:
sibble
2005 Oct 10
0
process sigblk
Given the below info: what signal is SigBlk indicating?
THanks,
Jerry
------------
State: S (sleeping)
Tgid: 11542
Pid: 11542
PPid: 1
TracerPid: 0
Uid: 0 0 0 0
Gid: 0 0 0 0
FDSize: 256
Groups: 0 1 2 3 4 6 10
VmSize: 4888 kB
VmLck: 0 kB
VmRSS: 1944 kB
VmData: 692 k...
2005 Dec 23
4
sshd blocks SIGALRM
...e regarding the sshd daemon on our
SuSE system. For some reasons, the /usr/sbin/sshd process blocks SIGALRM as
shown in the /proc/pid/status:
$ cat /proc/`cat /var/run/sshd.init.pid`/status
Name: sshd
State: S (sleeping)
SleepAVG: 0%
[...]
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000002000 <-- SIGALRM is blocked
SigIgn: 0000000000001000
As a result, any descendent processes shall inherit this mask. The bad news
is that some commands rely on SIGALRM being unmasked, e.g. those invoking
alarm() or similar. If those commands are started from a "ssh shell"...
2012 Jul 27
1
Samba 3.6.x: smbd receives sigpipe and crashes
...with Samba 3.6.0 up to 3.6.6. Forked smbd processes
are closing unexpectedly and sometimes smbd server exits. (In Samba
3.5.16 everything works).
When invoke smbd from gdb and turn off SIGPIPE passing (by command
"handle SIGPIPE nostop nopass") everything works fine. I found out that
SigBlk flag of forked smbd processes in /proc/*/status is:
0000000000000880 and should be 0000000000001880 (It works in Samba 3.5.16).
This flag changes after invoking getpwnam function, after passing string
"guest+workgroup" to it.
There is probably a memory leak or something.
Does anyone ha...
2014 Jan 16
0
Processed: user debian-qa@lists.debian.org, found 728743 in 331.20-1, tagging 728743, tagging 735576 ...
Processing commands for control at bugs.debian.org:
> user debian-qa at lists.debian.org
Setting user to debian-qa at lists.debian.org (was anbe at debian.org).
> found 728743 331.20-1
Bug #728743 [libgl1-nvidia-glx] corrupts the signal block mask (SigBlk) breaking unrelated
Bug #733816 [libgl1-nvidia-glx] khotkeys launches actions with SIGHUP blocked, leading to unclosable xterms
Marked as found in versions nvidia-graphics-drivers/331.20-1.
Marked as found in versions nvidia-graphics-drivers/331.20-1.
> tags 728743 + fixed-upstream
Bug #728743 [...
2013 Jul 24
1
Cpus_allowed_list issue in RHEL6.4
...k: 19364 kB
VmSize: 19356 kB
VmLck: 0 kB
VmHWM: 1544 kB
VmRSS: 1544 kB
VmData: 328 kB
VmStk: 88 kB
VmExe: 140 kB
VmLib: 2348 kB
VmPTE: 52 kB
VmSwap: 0 kB
Threads: 1
SigQ: 1/256326
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000001000
SigCgt: 00000001a0016623
CapInh: 0000000000000000
CapPrm: ffffffffffffffff
CapEff: fffffffffffffeff
CapBnd: ffffffffffffffff
Cpus_allowed: 7fff7fff
Cpus_allowed_list: 0-14,16-30
Mems_allowed: 00000000,00000000,00000000,00000000,00000000,00000000,0...
2011 Jul 27
4
Creating a vm with a non-existent /dev/mapper/ tap2 device effectively hangs dom0 system
...Size: 64
Groups:
VmPeak: 23056 kB
VmSize: 21644 kB
VmLck: 21640 kB
VmHWM: 3848 kB
VmRSS: 3232 kB
VmData: 364 kB
VmStk: 88 kB
VmExe: 224 kB
VmLib: 2460 kB
VmPTE: 64 kB
Threads: 1
SigQ: 2/6081
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000001000
SigCgt: 0000000181000242
CapInh: 0000000000000000
CapPrm: ffffffffffffffff
CapEff: ffffffffffffffff
CapBnd: ffffffffffffffff
Cpus_allowed: 1
Cpus_allowed_list: 0
Mems_allowed: 1
Mems_allowed_list: 0
voluntary_ctxt_switches: 4155
nonvol...