search for: lrwx

...00000000 .... root> ps aux .... root 10932 0.0 1.6 3068 2080 ? D Nov07 0:17 rsync --daemon root 2191 0.0 0.8 2076 1052 ? D 03:45 0:00 rsync --daemon .... root> ls -l /proc/2191/* -r--r--r-- 1 root root 0 Nov 8 10:09 /proc/2191/cmdline lrwx------ 1 root root 0 Nov 8 10:09 /proc/2191/cwd -> /home/mail/virtual -r-------- 1 root root 0 Nov 8 10:09 /proc/2191/environ lrwx------ 1 root root 0 Nov 8 10:09 /proc/2191/exe -> /usr/bin/rsync pr--r--r-- 1 root root 0 No...

...lhost: On battery. root 1719510 1550505 0 14:40 pts/2 00:00:00 grep ups root at fricka:~# fuser /var/run/nut/upssched.pipe /run/nut/upssched.pipe: 1716171 root at fricka:/proc/1716171/fd# ls -la total 0 dr-x------ 2 root root 0 Jun 13 14:36 . dr-xr-xr-x 9 root root 0 Jun 13 14:35 .. lrwx------ 1 root root 64 Jun 13 14:36 0 -> /dev/null lrwx------ 1 root root 64 Jun 13 14:36 1 -> /dev/null lrwx------ 1 root root 64 Jun 13 14:36 10 -> 'socket:[16424722]' lrwx------ 1 root root 64 Jun 13 14:36 2 -> /dev/null lrwx------ 1 root root 64 Jun 13 14:36 3 -> 'socke...

...lhost: On battery. root 1719510 1550505 0 14:40 pts/2 00:00:00 grep ups root at fricka:~# fuser /var/run/nut/upssched.pipe /run/nut/upssched.pipe: 1716171 root at fricka:/proc/1716171/fd# ls -la total 0 dr-x------ 2 root root 0 Jun 13 14:36 . dr-xr-xr-x 9 root root 0 Jun 13 14:35 .. lrwx------ 1 root root 64 Jun 13 14:36 0 -> /dev/null lrwx------ 1 root root 64 Jun 13 14:36 1 -> /dev/null lrwx------ 1 root root 64 Jun 13 14:36 10 -> 'socket:[16424722]' lrwx------ 1 root root 64 Jun 13 14:36 2 -> /dev/null lrwx------ 1 root root 64 Jun 13 14:36 3 -> 'socke...

On Wed, Feb 11, 2015 at 10:27:50AM +0100, Nacho del Rey wrote: > Hi Volker and the list > > Yesterday the problem appeared again > > I could launch a strace command over a samba PID to see what was going on > and this is the result > > [PRO] [root at pf3il0024 ~]# strace -frp 57686 > Process 57686 attached - interrupt to quit > 0.000000 fcntl(14, F_SETLKW,

...ell. Debuging the application and the ssh process using strace I realized about something strange: Having the following file descriptors in the sshd process lr-x------ 1 root root 64 Feb 15 17:12 9 -> pipe:[383586491] lr-x------ 1 root root 64 Feb 15 17:12 8 -> /var/lib/sss/mc/group lrwx------ 1 root root 64 Feb 15 17:12 7 -> socket:[383586484] lrwx------ 1 root root 64 Feb 15 17:12 6 -> socket:[383586478] lrwx------ 1 root root 64 Feb 15 17:12 5 -> socket:[383586458] lrwx------ 1 root root 64 Feb 15 17:12 4 -> socket:[383586457] lrwx------ 1 root ro...

https://bugs.freedesktop.org/show_bug.cgi?id=79823 Priority: medium Bug ID: 79823 Assignee: nouveau at lists.freedesktop.org Summary: Mozilla apps freeze on startup with nouveau-dri-10.2.1 libs on dual-screen Severity: normal Classification: Unclassified OS: Linux (All) Reporter: natrio at

...00:00:00 grep ups > > > > > root at fricka:~# fuser /var/run/nut/upssched.pipe > /run/nut/upssched.pipe: 1716171 > > > root at fricka:/proc/1716171/fd# ls -la > total 0 > dr-x------ 2 root root 0 Jun 13 14:36 . > dr-xr-xr-x 9 root root 0 Jun 13 14:35 .. > lrwx------ 1 root root 64 Jun 13 14:36 0 -> /dev/null > lrwx------ 1 root root 64 Jun 13 14:36 1 -> /dev/null > lrwx------ 1 root root 64 Jun 13 14:36 10 -> 'socket:[16424722]' > lrwx------ 1 root root 64 Jun 13 14:36 2 -> /dev/null > lrwx------ 1 root root 64 Jun 13 14:3...

...00:00:00 grep ups > > > > > root at fricka:~# fuser /var/run/nut/upssched.pipe > /run/nut/upssched.pipe: 1716171 > > > root at fricka:/proc/1716171/fd# ls -la > total 0 > dr-x------ 2 root root 0 Jun 13 14:36 . > dr-xr-xr-x 9 root root 0 Jun 13 14:35 .. > lrwx------ 1 root root 64 Jun 13 14:36 0 -> /dev/null > lrwx------ 1 root root 64 Jun 13 14:36 1 -> /dev/null > lrwx------ 1 root root 64 Jun 13 14:36 10 -> 'socket:[16424722]' > lrwx------ 1 root root 64 Jun 13 14:36 2 -> /dev/null > lrwx------ 1 root root 64 Jun 13 14:3...

...5 Component: ssh Assignee: unassigned-bugs at mindrot.org Reporter: ionic at ionic.de As a more general case of #1988, the -f flag also seems to keep stdin and stderr open in the general case: % ssh ionic.de -f -T 'pv -qL 1 /dev/zero' % ls -ldh /proc/7115/fd/* lrwx------ 1 ionic ionic 64 Mar 16 09:21 /proc/7115/fd/0 -> /dev/pts/50 l-wx------ 1 ionic ionic 64 Mar 16 09:21 /proc/7115/fd/1 -> /dev/null lrwx------ 1 ionic ionic 64 Mar 16 09:21 /proc/7115/fd/2 -> /dev/pts/50 lrwx------ 1 ionic ionic 64 Mar 16 09:21 /proc/7115/fd/3 -> 'socket:[14059...

Hi Volker Unfortunately I didn't keep this information but fd=14 now (samba pids) points to [PRO] [root at pf3il0024 ~]# for i in `ps -ef | grep smbd| grep -v grep| awk '{print $2}'`; do ls -la /proc/$i/fd/14; done lrwx------ 1 root root 64 Feb 10 21:16 /proc/3238/fd/14 -> /var/lib/samba/locking.tdb lrwx------ 1 root root 64 Feb 1 01:33 /proc/18405/fd/14 -> /var/lib/samba/locking.tdb lrwx------ 1 root root 64 Feb 1 01:33 /proc/18408/fd/14 -> /var/lib/samba/locking.tdb lrwx------ 1 root root 64 Feb 1 01...

...> >> root at fricka:~# fuser /var/run/nut/upssched.pipe >> /run/nut/upssched.pipe: 1716171 >> >> >> root at fricka:/proc/1716171/fd# ls -la >> total 0 >> dr-x------ 2 root root 0 Jun 13 14:36 . >> dr-xr-xr-x 9 root root 0 Jun 13 14:35 .. >> lrwx------ 1 root root 64 Jun 13 14:36 0 -> /dev/null >> lrwx------ 1 root root 64 Jun 13 14:36 1 -> /dev/null >> lrwx------ 1 root root 64 Jun 13 14:36 10 -> 'socket:[16424722]' >> lrwx------ 1 root root 64 Jun 13 14:36 2 -> /dev/null >> lrwx------ 1 root roo...

...> >> root at fricka:~# fuser /var/run/nut/upssched.pipe >> /run/nut/upssched.pipe: 1716171 >> >> >> root at fricka:/proc/1716171/fd# ls -la >> total 0 >> dr-x------ 2 root root 0 Jun 13 14:36 . >> dr-xr-xr-x 9 root root 0 Jun 13 14:35 .. >> lrwx------ 1 root root 64 Jun 13 14:36 0 -> /dev/null >> lrwx------ 1 root root 64 Jun 13 14:36 1 -> /dev/null >> lrwx------ 1 root root 64 Jun 13 14:36 10 -> 'socket:[16424722]' >> lrwx------ 1 root root 64 Jun 13 14:36 2 -> /dev/null >> lrwx------ 1 root roo...

...=4, events=POLLIN}, > {fd=6, events=POLLIN}, {fd=15, events=POLLIN}, {fd=18, events=POLLIN}, > {fd=19, events=POLLIN}, {fd=35, events=0}, {fd=35, events=POLLIN}], 9, {0, > 14960491}, NULL, 8) = 0 (Timeout) Here's those fds: [root@source ~]# ll /proc/31804/fd/{8,4,6,15,18,19,35} > lrwx------ 1 qemu qemu 64 Jun 21 13:18 /proc/31804/fd/15 -> socket:[931291] > lrwx------ 1 qemu qemu 64 Jun 21 13:18 /proc/31804/fd/18 -> socket:[931295] > lrwx------ 1 qemu qemu 64 Jun 21 13:18 /proc/31804/fd/19 -> socket:[931297] > lrwx------ 1 qemu qemu 64 Jun 21 13:18 /proc/31804/f...

...lhost: On battery. root 1719510 1550505 0 14:40 pts/2 00:00:00 grep ups root at fricka:~# fuser /var/run/nut/upssched.pipe /run/nut/upssched.pipe: 1716171 root at fricka:/proc/1716171/fd# ls -la total 0 dr-x------ 2 root root 0 Jun 13 14:36 . dr-xr-xr-x 9 root root 0 Jun 13 14:35 .. lrwx------ 1 root root 64 Jun 13 14:36 0 -> /dev/null lrwx------ 1 root root 64 Jun 13 14:36 1 -> /dev/null lrwx------ 1 root root 64 Jun 13 14:36 10 -> 'socket:[16424722]' lrwx------ 1 root root 64 Jun 13 14:36 2 -> /dev/null lrwx------ 1 root root 64 Jun 13 14:36 3 -> 'socke...

...lhost: On battery. root 1719510 1550505 0 14:40 pts/2 00:00:00 grep ups root at fricka:~# fuser /var/run/nut/upssched.pipe /run/nut/upssched.pipe: 1716171 root at fricka:/proc/1716171/fd# ls -la total 0 dr-x------ 2 root root 0 Jun 13 14:36 . dr-xr-xr-x 9 root root 0 Jun 13 14:35 .. lrwx------ 1 root root 64 Jun 13 14:36 0 -> /dev/null lrwx------ 1 root root 64 Jun 13 14:36 1 -> /dev/null lrwx------ 1 root root 64 Jun 13 14:36 10 -> 'socket:[16424722]' lrwx------ 1 root root 64 Jun 13 14:36 2 -> /dev/null lrwx------ 1 root root 64 Jun 13 14:36 3 -> 'socke...

FWIW, I wonder if this is a fallout of PR #1274 : https://github.com/networkupstools/nut/pull/1274/files and specifically https://github.com/networkupstools/nut/commit/550064930e369fb3a322c3b28ffff8b4acf53532 which added a `sock_read()` loop continuation effectively if `pconf_char()` returned 0. Just grasping at straws here (since it is a change a couple of months before the release was cut),

FWIW, I wonder if this is a fallout of PR #1274 : https://github.com/networkupstools/nut/pull/1274/files and specifically https://github.com/networkupstools/nut/commit/550064930e369fb3a322c3b28ffff8b4acf53532 which added a `sock_read()` loop continuation effectively if `pconf_char()` returned 0. Just grasping at straws here (since it is a change a couple of months before the release was cut),

...fuser /var/run/nut/upssched.pipe >>> /run/nut/upssched.pipe: 1716171 >>> >>> >>> root at fricka:/proc/1716171/fd# ls -la >>> total 0 >>> dr-x------ 2 root root 0 Jun 13 14:36 . >>> dr-xr-xr-x 9 root root 0 Jun 13 14:35 .. >>> lrwx------ 1 root root 64 Jun 13 14:36 0 -> /dev/null >>> lrwx------ 1 root root 64 Jun 13 14:36 1 -> /dev/null >>> lrwx------ 1 root root 64 Jun 13 14:36 10 -> 'socket:[16424722]' >>> lrwx------ 1 root root 64 Jun 13 14:36 2 -> /dev/null >>> lrwx-...

...fuser /var/run/nut/upssched.pipe >>> /run/nut/upssched.pipe: 1716171 >>> >>> >>> root at fricka:/proc/1716171/fd# ls -la >>> total 0 >>> dr-x------ 2 root root 0 Jun 13 14:36 . >>> dr-xr-xr-x 9 root root 0 Jun 13 14:35 .. >>> lrwx------ 1 root root 64 Jun 13 14:36 0 -> /dev/null >>> lrwx------ 1 root root 64 Jun 13 14:36 1 -> /dev/null >>> lrwx------ 1 root root 64 Jun 13 14:36 10 -> 'socket:[16424722]' >>> lrwx------ 1 root root 64 Jun 13 14:36 2 -> /dev/null >>> lrwx-...

Hi. I tried for some time to reproduce the "Login process died too early issue". It seems related to when the system run out of file descriptors, to force the issue i forwarded 3k of messages trough the server(using thunderbird). I also tried with my usual mail application - mail.app, but no luck there. Aug 26 18:46:36 soekris postfix/cleanup[14739]: fatal: accept