Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied
Package: libpam-systemd Version: 232-25 Followup-For: Bug #732209 Hello I am also using Debian Stretch on Cinnamon desktop and the problem seems to be gone. I am no longer getting strange messages in syslog neither the annoying X desktop lock-up. Interestingly, when I do "gksu /usr/bin/x-terminal-emulator", I get a segfault (you read it right, on Debian stable!): " 2017-07-03T20:16:24.930235+02:00 qmitoshiba kernel: [14358.860790] gnome-terminal-[4335]: segfault at 8 ip 560f0872ccb7 sp 7ffca2a0f540 error 4 in gnome-terminal-server[560f08718000+4c000] " Still, I am able to spin-up a new gnome terminal nonetheless. The bug displayed above is less of an issue, as it is not a blocker to your daily routine having to restart your X desktop session like it used to. So, thankfully, the original issue looks like to be gone. Just in case anyone did not notice, the x-terminal-emulator is a gnome-terminal.wrapper Perl script (which in turn runs gnome-terminal) by default: " root@qmitoshiba:~# update-alternatives --display x-terminal-emulator x-terminal-emulator - auto mode link best version is /usr/bin/gnome-terminal.wrapper link currently points to /usr/bin/gnome-terminal.wrapper link x-terminal-emulator is /usr/bin/x-terminal-emulator slave x-terminal-emulator.1.gz is /usr/share/man/man1/x-terminal-emulator.1.gz /usr/bin/gnome-terminal.wrapper - priority 40 slave x-terminal-emulator.1.gz: /usr/share/man/man1/gnome-terminal.1.gz root@qmitoshiba:~# ls -l /usr/bin/gnome-terminal.wrapper -rwxr-xr-x 1 root root 1394 Jun 16 2011 /usr/bin/gnome-terminal.wrapper root@qmitoshiba:~# dpkg -S !$ dpkg -S /usr/bin/gnome-terminal.wrapper gnome-terminal: /usr/bin/gnome-terminal.wrapper root@qmitoshiba:~# file /usr/bin/gnome-terminal.wrapper /usr/bin/gnome-terminal.wrapper: Perl script text executable root@qmitoshiba:~# " After others confirm the same behaviour including on sid, we can close this bug and open a new one against the gnome-terminal. -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libpam-systemd depends on: ii dbus1.10.18-1 ii libc6 2.24-11+deb9u1 ii libpam-runtime 1.1.8-3.6 ii libpam0g1.1.8-3.6 ii libselinux1 2.6-3+b1 ii systemd 232-25 ii systemd-sysv232-25 libpam-systemd recommends no packages. libpam-systemd suggests no packages. -- no debconf information -- Miklos Quartus in...@miklos.info WWW: http://www.miklos.info GPG: 3C4B 1364 A379 7366 7FED 260A 2208 F2CE 3FCE A0D3
Bug#712564: pamassassin: Add feature to run spamassassin as debian-spamd user
Package: spamassassin Followup-For: Bug #712564 > please add the feature to run spamassassin as debian-spamd user. Why so? When spamassassin is running in daemon mode (spamd) as root, the default behaviour is to setuid to the user running spamc. This lets spamd to load and examine the per-user configuration files as the user. So by default, the effective UID is sent to spamd from spamc. Certainly there is a point in what you are suggesting. You are welcome to send a patch for each configuration file where this change could be introduced as an added feature. The alternative username could be passed on to 'spamd' after the '-u' switch. Regards, -- Miklos Quartus WWW: http://www.miklos.info GPG: 3C4B 1364 A379 7366 7FED 260A 2208 F2CE 3FCE A0D3 signature.asc Description: PGP signature
Bug#731516: /etc/cron.daily/spamassassin: sa-compile not executed from cron
Package: spamassassin Followup-For: Bug #731516 Hi Maintainer, Michal, > > It's on my to-do list to split sa-compile into a separate package that > > can properly depend on the tools it needs. The sa-compile package's > > cron job can unconditionally compile the rules, since it can safely > > assume that if you have the package installed then you intend to > > compile your rules. > Indeed this would be best solution. As far as I can see, the 'sa-compile' package is now separated from spamassassin package at least in sid and in Jessie. I do have spamassasin installed, but I don't have sa-compile. So this bug can be closed, am I right? Regards, Miklos -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.5.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages spamassassin depends on: ii adduser 3.114 ii curl 7.47.0-1 ii init-system-helpers 1.34 ii libhtml-parser-perl 3.72-1 ii libhttp-date-perl6.02-1 ii libnet-dns-perl 1.05-2 ii libnetaddr-ip-perl 4.079+dfsg-1 ii libsocket6-perl 0.27-1 ii libsys-hostname-long-perl1.5-1 ii libwww-perl 6.15-1 ii perl 5.22.2-1 ii perl-modules-5.22 [libarchive-tar-perl] 5.22.2-1 ii w3m 0.5.3-28 Versions of packages spamassassin recommends: ii gnupg 1.4.20-6 ii libio-socket-inet6-perl 2.72-2 ii libmail-spf-perl 2.9.0-4 ii libperl5.22 [libsys-syslog-perl] 5.22.2-1 pn sa-compile ii spamc 3.4.1-4 Versions of packages spamassassin suggests: pn libdbi-perl pn libencode-detect-perl ii libio-socket-ssl-perl2.027-1 pn libmail-dkim-perl ii libperl5.22 [libcompress-zlib-perl] 5.22.2-1 pn pyzor pn razor -- Configuration Files: /etc/spamassassin/local.cf changed: rewrite_header Subject SPAM required_score 4.0 ifplugin Mail::SpamAssassin::Plugin::Shortcircuit endif # Mail::SpamAssassin::Plugin::Shortcircuit -- no debconf information -- Miklos Quartus WWW: http://www.miklos.info GPG: 3C4B 1364 A379 7366 7FED 260A 2208 F2CE 3FCE A0D3 signature.asc Description: PGP signature
Bug#687411: /etc/cron.daily/spamassassin blocks cron for up to 3600 seconds
Package: spamassassin Version: 3.4.1-4 Followup-For: Bug #687411 Hello Martin, You wrote on Wed, 12 Sep 2012 15:36:30 +0200: > This has the disadvantage that cron is blocked while the script is > sleeping; it's also annoying when running the script manually. Yes and no. The second part is no longer the case (I don't know what was earlier) but now if running the script interactively, this code block will be skipped: " # Sleep for up to 3600 seconds if not running interactively if [ ! -t 0 ]; then RANGE=3600 number=`od -vAn -N2 -tu4 < /dev/urandom` number=`expr $number "%" $RANGE` sleep $number fi " So this no longer applies. However, the first suggestion of sending the sleep into a detached subshell I completely agree with, I think it's great: > ( > # Sleep for up to 3600 seconds > RANGE=3600 > number=`od -vAn -N2 -tu4 < /dev/urandom` > number=`expr $number "%" $RANGE` > sleep $number > > # Update > umask 022 > sa-update > ) & > these problems should be resolved. Yes, blocking the daily cron with a sleep can be a nuisance from system adminisration point of view. I will propose this wishlist be forwarded on and approved by the maintainer and the change be made in next upcoming package version. Regards, Miklos -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.5.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages spamassassin depends on: ii adduser 3.114 ii curl 7.47.0-1 ii init-system-helpers 1.34 ii libhtml-parser-perl 3.72-1 ii libhttp-date-perl6.02-1 ii libnet-dns-perl 1.05-2 ii libnetaddr-ip-perl 4.079+dfsg-1 ii libsocket6-perl 0.27-1 ii libsys-hostname-long-perl1.5-1 ii libwww-perl 6.15-1 ii perl 5.22.2-1 ii perl-modules-5.22 [libarchive-tar-perl] 5.22.2-1 ii w3m 0.5.3-28 Versions of packages spamassassin recommends: ii gnupg 1.4.20-6 ii libio-socket-inet6-perl 2.72-2 ii libmail-spf-perl 2.9.0-4 ii libperl5.22 [libsys-syslog-perl] 5.22.2-1 pn sa-compile ii spamc 3.4.1-4 Versions of packages spamassassin suggests: pn libdbi-perl pn libencode-detect-perl ii libio-socket-ssl-perl2.027-1 pn libmail-dkim-perl ii libperl5.22 [libcompress-zlib-perl] 5.22.2-1 pn pyzor pn razor -- Configuration Files: /etc/spamassassin/local.cf changed [not included] -- no debconf information -- Miklos Quartus WWW: http://www.miklos.info GPG: 3C4B 1364 A379 7366 7FED 260A 2208 F2CE 3FCE A0D3 signature.asc Description: PGP signature
Bug#788429: spamassassin: /etc/init.d/spamassassin restart fails on Jessie/sysvinit
Package: spamassassin Version: 3.4.1-4 Followup-For: Bug #788429 And BTW, for sake of completeness: on sid the restart argument to the init script works fine without any issues: " root@qmitoshiba:~# /etc/init.d/spamassassin restart [ ok ] Restarting spamassassin (via systemctl): spamassassin.service. root@qmitoshiba:~# echo $? 0 root@qmitoshiba:~# " So I believe this is no longer an issue :-) Thanks for reporting anyway, this bug can be closed. Regards -- Miklos Quartus WWW: http://www.miklos.info GPG: 3C4B 1364 A379 7366 7FED 260A 2208 F2CE 3FCE A0D3 signature.asc Description: PGP signature
Bug#788429: spamassassin: /etc/init.d/spamassassin restart fails on Jessie/sysvinit
Package: spamassassin Version: 3.4.1-4 Followup-For: Bug #788429 > So the 'start-stop-daemon --stop' calls in /etc/init.d/spamassassin are not > able to identify the running spamd processes. Note that this bug does not apply, since systemd we normally restart services via 'systemctl restart '. In my Debian sid, the restarting the service works perfectly well: " root@qmitoshiba:/etc/default# ps -ef |grep spamd root 20738 1 1 21:44 ?00:00:01 /usr/sbin/spamd -d --pidfile=/var/run/spamassassin.pid --create-prefs --max-children 5 --helper-home-dir root 20739 20738 0 21:44 ?00:00:00 spamd child root 20740 20738 0 21:44 ?00:00:00 spamd child root 20763 13386 0 21:47 pts/200:00:00 grep spamd root@qmitoshiba:/etc/default# systemctl restart spamassassin root@qmitoshiba:/etc/default# systemctl status spamassassin ● spamassassin.service - Perl-based spam filter using text analysis Loaded: loaded (/lib/systemd/system/spamassassin.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2016-05-30 21:47:35 CEST; 12s ago Process: 20771 ExecStart=/usr/sbin/spamd -d --pidfile=/var/run/spamassassin.pid $OPTIONS (code=exited, status=0/SUCCESS) Main PID: 20777 (/usr/sbin/spamd) CGroup: /system.slice/spamassassin.service ├─20777 /usr/sbin/spamd -d --pidfile=/var/run/spamassassin.pid --create-prefs --max-children 5 --helper-home-di ├─20778 spamd chil └─20779 spamd chil May 30 21:47:33 qmitoshiba systemd[1]: Starting Perl-based spam filter using text analysis... May 30 21:47:33 qmitoshiba spamd[20771]: logger: removing stderr method May 30 21:47:34 qmitoshiba spamd[20777]: zoom: able to use 353/353 'body_0' compiled rules (100%) May 30 21:47:35 qmitoshiba spamd[20777]: spamd: server started on IO::Socket::IP [::1]:783, IO::Socket::IP [127.0.0.1]:783 (running version 3.4.1) May 30 21:47:35 qmitoshiba spamd[20777]: spamd: server pid: 20777 May 30 21:47:35 qmitoshiba spamd[20777]: spamd: server successfully spawned child process, pid 20778 May 30 21:47:35 qmitoshiba spamd[20777]: spamd: server successfully spawned child process, pid 20779 May 30 21:47:35 qmitoshiba spamd[20777]: prefork: child states: SI May 30 21:47:35 qmitoshiba systemd[1]: Started Perl-based spam filter using text analysis. May 30 21:47:35 qmitoshiba spamd[20777]: prefork: child states: II root@qmitoshiba:/etc/default# " As you can see above, before the restart spamd had PID of 20738, after it was restarted, it changed to 20777. Because Jessie is already on systemd, restarting as shown above should also work on Jessie. Any comments or concerns, please do not hold off. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.5.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages spamassassin depends on: ii adduser 3.114 ii curl 7.47.0-1 ii init-system-helpers 1.33 ii libhtml-parser-perl 3.72-1 ii libhttp-date-perl6.02-1 ii libnet-dns-perl 1.05-2 ii libnetaddr-ip-perl 4.079+dfsg-1 ii libsocket6-perl 0.27-1 ii libsys-hostname-long-perl1.5-1 ii libwww-perl 6.15-1 ii perl 5.22.2-1 ii perl-modules-5.22 [libarchive-tar-perl] 5.22.2-1 ii w3m 0.5.3-28 Versions of packages spamassassin recommends: ii gnupg 1.4.20-6 ii libio-socket-inet6-perl 2.72-2 ii libmail-spf-perl 2.9.0-4 ii libperl5.22 [libsys-syslog-perl] 5.22.2-1 ii sa-compile3.4.1-4 ii spamc 3.4.1-4 Versions of packages spamassassin suggests: pn libdbi-perl pn libencode-detect-perl ii libio-socket-ssl-perl2.027-1 pn libmail-dkim-perl ii libperl5.22 [libcompress-zlib-perl] 5.22.2-1 pn pyzor pn razor -- Configuration Files: /etc/spamassassin/local.cf changed [not included] -- no debconf information Regards, -- Miklos Quartus WWW: http://www.miklos.info GPG: 3C4B 1364 A379 7366 7FED 260A 2208 F2CE 3FCE A0D3
Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied
Package: libpam-systemd Version: 215-11 Followup-For: Bug #732209 Hi Vlad, Yes, I am still able to reproduce this bug in my GNOME session in my latest Jessie, indeed. After opening the root terminal window and in focus, I can use three ways to trigger: 1. In a standar user terminal open a shell and run gksu gedit. 2. Type Super key and search dconf-Editor and run it. 3. Type Super key and search for Files file manager and run it. I do not use MATE so I don't know how that works. My system otherwise is working fine. I don't have access to unstable or experimental distro, so I cannot test it. My system is a healthy Debian Jessie 8 with systemd-sysv: root@localhost:~# systemctl status sysinit.target ● sysinit.target - System Initialization Loaded: loaded (/lib/systemd/system/sysinit.target; static) Active: active since Sun 2015-02-15 18:57:11 CET; 1 day 1h ago Docs: man:systemd.special(7) root@localhost:~# date Mon Feb 16 20:31:46 CET 2015 root@localhost:~# cat /etc/debian_version 8.0 gnome-session: 3.14.0-2 libpam-systemd: 215-11 gnome-shell:3.14.2-3+b1 Package gnome-desktop-environment is *not* installed. Regards, -- Miklos -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libpam-systemd depends on: ii dbus 1.8.12-3 ii libc6 2.19-13 ii libcap21:2.24-6 ii libpam-runtime 1.1.8-3.1 ii libpam0g 1.1.8-3.1 ii multiarch-support 2.19-13 ii systemd215-11 ii systemd-sysv 215-11 libpam-systemd recommends no packages. libpam-systemd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied
Package: libpam-systemd Version: 215-8 Followup-For: Bug #732209 What does systemctl | head say? systemctl | head UNIT LOAD ACTIVE SUB DESCRIPTION proc-sys-fs-binfmt_misc.automount loaded active running Arbitrary Executable File Formats File System Automount Point sys-devices-pci:00-:00:02.0-backlight-acpi_video0.device loaded active plugged /sys/devices/pci:00/:00:02.0/backlight/acpi_video0 sys-devices-pci:00-:00:02.0-drm-card0-card0\x2dLVDS\x2d1-intel_backlight.device loaded active plugged /sys/devices/pci:00/:00:02.0/drm/card0/card0-LVDS-1/intel_backlight (...) Also, see below: root@localhost:~# ps -p1 -o pid,cmd,comm PID CMD COMMAND 1 /sbin/init systemd root@localhost:~# type systemd systemd is /bin/systemd root@localhost:~# readlink /bin/systemd /lib/systemd/systemd root@localhost:~# Apparently, systemd is in charge. Regards, Miklos -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libpam-systemd depends on: ii dbus 1.8.12-3 ii libc6 2.19-13 ii libcap21:2.24-6 ii libpam-runtime 1.1.8-3.1 ii libpam0g 1.1.8-3.1 ii multiarch-support 2.19-13 ii systemd215-8 ii systemd-sysv 215-8 libpam-systemd recommends no packages. libpam-systemd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732209: (no subject)
Content-Type: multipart/mixed; boundary1764408977== MIME-Version: 1.0 From: Miklos Quartus in...@miklos.info To: Debian Bug Tracking System 732...@bugs.debian.org Subject: Re: unable to create file '/run/user/1000/dconf/user': Permission denied Message-ID: 20141230213601.24606.52599.reportbug@localhost X-Mailer: reportbug 6.6.1 Date: Tue, 30 Dec 2014 22:36:01 +0100 This is a multi-part MIME message sent by reportbug. --===1764408977== Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Package: libpam-systemd Version: 215-8 Followup-For: Bug #732209 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear GNOME Maintainer, Here's some progress on the bug I am still experiencing in Jessie. I found that this bug can only be reproduced in a GNOME session if the root terminal window is in focus. So to the steps to reproduce the bug - if you have not managed to so far - - slightly changes as below. 1. Get a root terminal window running and make sure it's in focus (in a GNOME session hit the Super key, type 'root ..' in the search bar and hit Enter to the run the app. 2. Run the 'Files' file manager app (not the PCManFM or other) or the 'dconf Editor' app (hit the Super key, type the app name) and once the window is active, do some one simple action (i.e. click on a menu item). 3. Close the application window. 4. Watch the file permission changes - /run/user/1000/dconf/user which effectively locks up your GNOME session. At the moment I don't have any patch or further information as to what might be the root cause leading up to this issue. I am using the latest up-to-date Jessie from official Debian repositories. It is also worth mentioning that I am using the GNOME minimalist installation, I have the 'core-only' as described on https://wiki.debian.org/Gnome . (i.e. I don't have the gnome-desktop-environment package installed, I have the extra stuff :-/). This way I am perfectly happy user of Debian and GNOME. gnome-session: 3.14.0-2 gnome-shell: 3.14.2-3 gnome-core: 1:3.14+3 gnome-desktop-environment: not installed gnome-desktop: not installed Inform me of any progress. Kind regards, - -- Miklos - -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libpam-systemd depends on: ii dbus 1.8.12-3 ii libc6 2.19-13 ii libcap21:2.24-6 ii libpam-runtime 1.1.8-3.1 ii libpam0g 1.1.8-3.1 ii multiarch-support 2.19-13 ii systemd215-8 ii systemd-sysv 215-8 libpam-systemd recommends no packages. libpam-systemd suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJUoxqyAAoJECII8s4/zqDTrKIIALGo5P7P5xsgGweHcxBQr4Zu e6HOiR2Sc91xudDP+Tty/iXAciG01fRi1vrcc6rlAgTa44/+RC5UJTY5Ar8IL7xC G5w7ChYd+y9gWlMHzLAi/eiC37UFW5HQzp1bsvTWI8y9p5l/lWyP7/56eiKIzNEj +6kLK99EJ92qXscC45SFggiT8871d7y9wW52HbFZHoMzsJfPAel57fMDiupvxZut ndO8mSkUDCD8xn6fpks2Vu2PYhP7NO/w6ip2XYHz/axyj51Wz4y2lQnAFgAS6Twk ubzDQeH0ub6iu7ILkoDImuLlCRAYOR09H7ufCOWDhHDJcybpk3fs+qKxVMf6lyA= =4tzM -END PGP SIGNATURE- --===1764408977== Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=gnome-shell-errormsg.txt Dec 30 22:13:12 localhost gnome-session[21484]: (gnome-settings-daemon:21555): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. --===1764408977==-- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied
Package: libpam-systemd Version: 215-7 Followup-For: Bug #732209 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, I can still reproduce the problem. Can you please provide step-by-step instructions, how to setup the test environment (which packages are installed, which environment is running) and which commands to use to trigger the problem. Let me give you a few details about my environment in the hopes that you (or someone else) will be able to reproduce it. I'd be grateful if you could provide a few pointers how to get rid of this annoying bug. 1. Init system installed on my system is systemd. root@localhost:~# ps -p1 f PID TTY STAT TIME COMMAND 1 ?Ss 0:03 /sbin/init root@localhost:~# ls -l /sbin/init lrwxrwxrwx 1 root root 20 Nov 28 07:37 /sbin/init - /lib/systemd/systemd root@localhost:~# 2. This happens under GNOME session after you log in via gdm3 as a regular (non-root) user. Related package versions are as below. gnome-shell:3.14.1-1 gnome-session: 3.14.0-2 gnome-core: 1:3.14+1 gnome-desktop-environment: 1:3.14+1 gdm3: 3.14.1-3 3. It is worth noting that I have a gvfsd-fuse and a tmpfs line showing up in my /etc/mtab. I am not sure they're related. root@localhost:~# grep /run/user/1000 /etc/mtab tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=394008k,mode=700,uid=1000,gid=1000 0 0 gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0 4. My APT package manager is completely healthy and has got no failed/broken packages, all repositories are used from official Debian mirrors and are brought up-to-date to Jessie. deb http://ftp.hu.debian.org/debian jessie main contrib non-free deb http://security.debian.org/ stable/updates main contrib non-free I also tried with a clean, newly created user (i.e. test) and the problems happens there, too. So this clears me of any user-specific tweaks. Besides, my GNOME session works completely well. I hope the above helps. Let me know if you need anything else. Regards, Miklos - -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libpam-systemd depends on: ii dbus 1.8.12-1 ii libc6 2.19-13 ii libcap21:2.24-6 ii libpam-runtime 1.1.8-3.1 ii libpam0g 1.1.8-3.1 ii multiarch-support 2.19-13 ii systemd215-7 ii systemd-sysv 215-7 libpam-systemd recommends no packages. libpam-systemd suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJUg3IIAAoJECII8s4/zqDT8BkH/3d7xbFS4QoC8Vc9wnPtmskw etYqiiu7G3JrAhQPSnd1/JKlcLvyglbaOoIKny/5FvCRusn36gfLhYQ6z3Chi9Uz S/qk8z/xFGjHVwi2mJjCegZTdxrYn4BLcF8s7BLbIq8k7eTYGZexU91Hx1RUMPd8 ERzS0eok7wFJQeJol+ISJDjtEHAoV7iXfWlO1O9ZztSHn20FVMalnr/sS1DaGzGF XBOFbcUoAXk7EtaH6gJ1WZe2uMsmm0iMv4tGDqn8rgGN2DXYzL5VWNmk1Fe2FZUL VwYvFE9x1mtvS3KzoXL/X2/u2pi5ZmguqGObkokaDT2WYEysc77Pm1a9xNC602c= =to91 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732209: libpam-systemd: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.
Package: libpam-systemd Version: 215-7 Followup-For: Bug #732209 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Vlad , et al., Thanks for the clarification about sending references to earlier cases, when this bug surfaced. Now, I am sending a follow-up for this bug as it still happens in the latest up-to-date Jessie. I can still reproduce it at least in two different ways. See the steps how to reproduce it below. Pre-requisites. a. have a fat32 formatted usb flash drive ready b. your user should be just a regular user on your system without root privileges Steps to reproduce. 1. Log in with your regular user into your GNOME session. 2. Open up a root terminal by typing Windows key - (type 'root' in the search bar and hit Enter to the Root Terminal icon) 3. Type 'watch -n 1 ls -l /run/user/1000/dconf/user' as root to see when the permission of the file changes automatically. Instead of '1000', replace the number of your login user account. In my case it's 1000. 4. Open up the 'dconf Editor' by typing the Windows key - (type 'dconf' in the search bar and hit Enter to the 'dconf Editor' icon. 5. Close the dconf Editor. 6. See the file permission's change in the root terminal window. When this happens, it locks your entire GNOME session rendering your graphical user interface unusable. Unfortunately, I don't have a patch to fix it. Vlad, BTW, this only happens with GNOME sessions. With other window managers (e.g. LXDE, Openbox) it does *not*. Therefore, I do not think it's a systemd bug, rather it's related to GNOME. Do you agree to reassign this bug against either the 'gnome-session' or the 'gnome-shell' package? The related package versions I am still able to reproduce this bug are: gnome-session 3.14.0-2 gnome-desktop-environment 1:3.14+1 gnome-shell 3.14.1-1 Kind regards, Miklos - -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libpam-systemd depends on: ii dbus 1.8.12-1 ii libc6 2.19-13 ii libcap21:2.24-6 ii libpam-runtime 1.1.8-3.1 ii libpam0g 1.1.8-3.1 ii multiarch-support 2.19-13 ii systemd215-7 ii systemd-sysv 215-7 libpam-systemd recommends no packages. libpam-systemd suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJUf3UFAAoJECII8s4/zqDTrT8IAKWJCmn8DucyL4jnet/Bh1M9 7BBxzAoCMTHOEE8Xb4/+IK8vjFPJeGmbnIsMGMpJ7fP7vcilPX8zMZrXCwTFyYac N1+zZTEZI6hzLSWsD0wEvO0AM5OTyTOX53TgobIUCuuu/ObWiNqSls6lcmMxmro0 FWFPHQ5hobIeybhCcs6XmM9YShoZZvXNxIMCIN6Cf5GB95kiLFqaQKDqqxO0tMDG 6Gqv52jb4nJMG+wffS0J+2opQyiQoFNfkM4weGXE68PFYuK/ZSKDwV4fNR6SFX8/ 3tFWHRBOKkRA4eK3AZmXgdYvoa8jqyW439J6TnjDfXoCh1nqCc3dXjlXoO+MYG0= =bd/C -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732209: gnome-control-center: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.
Package: gnome-control-center Version: 1:3.14.1-1 Followup-For: Bug #732209 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, I am still able to reproduce this bug just as it is described in the forum post: http://forums.debian.net/viewtopic.php?f=10t=110035, so I thought I'd report it. The exact steps I use to repduce this are below. - - open a terminal - - run gksu gedit - - close gedit Now try to use the topleft hot corner in GNOME (the Super button) and you'll get locked. Temporary workaround: 1. Switch back to console with CTRL+ALT+F1 and log in as root 2. Do a 'chown 1000:1000 /run/user/1000/dconf/user' 3. Switch to the 1000 uid user in the console 4. Do a ' pkill -f /usr/bin/gnome-shell -HUP' 5. Switch back to your GNOME session. At the moment I do not know what is causing it. My echo $XDG_RUNTIME_DIR variable is correctly set to /run/user/1000. Please let me know once you find the fix. Thanks and regards, Miklos - -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16-3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-control-center depends on: ii accountsservice0.6.37-3+b1 ii apg2.2.3.dfsg.1-2 ii colord 1.2.1-1+b1 ii desktop-file-utils 0.22-1 ii gnome-control-center-data 1:3.14.1-1 ii gnome-desktop3-data3.14.1-1 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii gnome-settings-daemon 3.14.1-1 ii gsettings-desktop-schemas 3.14.1-1 ii libaccountsservice00.6.37-3+b1 ii libatk1.0-02.14.0-1 ii libc6 2.19-12 ii libcairo-gobject2 1.14.0-2.1 ii libcairo2 1.14.0-2.1 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libcheese-gtk233.14.1-1 ii libcheese7 3.14.1-1 ii libclutter-1.0-0 1.20.0-1 ii libclutter-gtk-1.0-0 1.6.0-1 ii libcolord-gtk1 0.1.25-1.1+b1 ii libcolord2 1.2.1-1+b1 ii libcups2 1.7.5-7 ii libdbus-glib-1-2 0.102-1 ii libfontconfig1 2.11.0-6.1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libglib2.0-0 2.42.0-2 ii libgnome-bluetooth13 3.14.0-1 ii libgnome-desktop-3-10 3.14.1-1 ii libgoa-1.0-0b 3.14.1-1 ii libgoa-backend-1.0-1 3.14.1-1 ii libgrilo-0.2-1 0.2.11-2 ii libgtk-3-0 3.14.4-2 ii libgtop2-7 2.28.5-2+b1 ii libibus-1.0-5 1.5.9-1 ii libkrb5-3 1.12.1+dfsg-11 ii libmm-glib01.4.0-1 ii libnm-glib-vpn10.9.10.0-3 ii libnm-glib40.9.10.0-3 ii libnm-gtk0 0.9.10.0-2 ii libnm-util20.9.10.0-3 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-01.36.8-2 ii libpolkit-gobject-1-0 0.105-7 ii libpulse-mainloop-glib05.0-13 ii libpulse0 5.0-13 ii libpwquality1 1.2.3-1 ii libsmbclient 2:4.1.13+dfsg-2 ii libsoup2.4-1 2.48.0-1 ii libupower-glib30.99.1-3 ii libwacom2 0.8-1 ii libx11-6 2:1.6.2-3 ii libxi6 2:1.7.4-1+b1 ii libxml22.9.1+dfsg1-4 Versions of packages gnome-control-center recommends: ii cracklib-runtime 2.9.2-1 ii cups-pk-helper 0.2.5-2+b1 ii gkbd-capplet 3.6.0-1 ii gnome-online-accounts 3.14.1-1 ii gnome-user-guide 3.14.1-1 ii gnome-user-share 3.14.0-1 ii iso-codes 3.57-1 ii libnss-myhostname 0.3-9 ii lxsession [policykit-1-gnome] 0.5.1-1 ii mesa-utils 8.2.0-1 ii mousetweaks3.12.0-1 ii network-manager-gnome 0.9.10.0-2 ii policykit-1-gnome 0.105-2 ii realmd 0.15.1-1+b2 ii rygel 0.24.1-1 ii system-config-printer 1.4.6-1 Versions of packages gnome-control-center suggests: ii gstreamer1.0-pulseaudio 1.4.3-2 ii libcanberra-gtk-module 0.30-2.1 ii libcanberra-gtk3-module 0.30-2.1 ii x11-xserver-utils7.7+3+b1 - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJUY9I3AAoJECII8s4/zqDTKMkIAJ90reKn8g04SwhRE18ca2lo Sbdm5B8dj4TAkdgk5Wd4cfN10PXx9U15LiHB8idO09blwdxX4AuwaYBEHlgebPfG LaTOIjk4gQiPMiFaqh5UMZHwFKvBgjasbCzja4EOZjKypq31mzKcRSgxjKQi7M0U xRwjCmF11OOR0LFICKOavFFqWApCha5UCiXJxVi26QRqi9zBqcEMPL2W0sK3Tj4H 1b4UfCkq7RRkTOYTGd3nWCnCNZWOzqpKHCo1mFy3KfJdyClTWLwIMctV0g4GlDfH
Bug#704425: Fwd: review for RFS sysadmin-guide
Hi Debian Mentors, The reviewer comments' have been processed into the new version of the package. New package uploaded and is pending another review and sponsorship. Note that the package was built on amd64 architecture, because that is the only 'sid' distro I have access to these days. Let me know if you can sponsor upload for me, any comments or corrections required before the upload. Thanks, Miklos -- Forwarded message -- From: Bart Martens ba...@debian.org Date: Fri, Jun 14, 2013 at 5:47 AM Subject: Re: review for RFS sysadmin-guide To: Miklos Quartus in...@miklos.info Hi Miklos, On Fri, Jun 14, 2013 at 01:10:34AM +0100, Miklos Quartus wrote: Note that I only have access to amd64 unstable Debian machine, that is why was built in amd64. That is OK. Most people have only one architecture available. Let me know how to proceed. Shall I write an email again to debian-mentors list to ask for sponsors? I suggest to mention on RFS 704425 that the review comments have been processed into the package at mentors. Then it is clear for everyone that the next step is for a sponsor. The message on the RFS will be automatically copied to the debian-mentors list. Regards, Bart Martens -- Miklos
Bug#704425: RFS: sysadmin-guide/0.9-2 [ITA] -- guide for novice linux system administrators
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package sysadmin-guide * Package name: sysadmin-guide Version : 0.9-2 Upstream Author : Lars Wirzenius, Joanna Oja, Stephen Stafford step...@clothcat.demon.co.uk, Alex Weeks draxe...@gmail.com * URL : http://www.tldp.org/LDP/sag/html/index.html * License : GNU Free Documentation Licence Section : doc It builds those binary packages: sysadmin-guide - linux system administrators' guide To access further information about this package, please visit the following URL: http://mentors.debian.net/package/sysadmin-guide Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/s/sysadmin-guide/sysadmin-guide_0.9-2.dsc Changes since the last upload: sysadmin-guide (0.9-2) unstable; urgency=low * New maintainer (Closes: #678876) * Conforms Debian Policy (Standards-Version) 3.9.3. * Removing cdbs package from build process to conform with dephelper recommendations -- Miklos Quartus in...@miklos.info Mon, 14 Jan 2013 21:14:07 + Regards, Miklos Quartus -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678876: O: sysadmin-guide -- The Linux System Administrators' Guide
Hi Bart, I am interested to take over the maintenance of this package. I will be looking for sponsor in about 1-2 weeks after I will be ready to upload. Let me know how this sounds and if I am doing everything okay. Thanks, -- Miklos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666104: [Pkg-xfce-devel] Bug#666104: xfce4-utils: xfce4 should not start ssh-agent if does not exist
On Thu, Mar 29, 2012 at 11:02:36PM +0200, Yves-Alexis Perez wrote: Please keep the bug on CC: OK On jeu., 2012-03-29 at 21:19 +0100, Miklos Quartus wrote: Hi, On Thu, Mar 29, 2012 at 10:21:04AM +0200, Yves-Alexis Perez wrote: On mer., 2012-03-28 at 19:11 +0100, Miklos Quartus wrote: Package: xfce4-utils Version: 4.8.3-2 Severity: normal What's the problem with the current situation? Just that it does not do what it is supposed to do. It seems to me that it works just fine. Xfce4 works just fine, however, the shell script generates error, indeed. No agent is recognized, therefore it cannot start it up. I still have the same set up on my PC and nothing has changed, the error remains. The error message is the same as in the original bug report. But, if you try the above change, X handles the missing agent more gracefully. I don't think X has anything to do with that. I think it does. The X session. Xfce4 xinitrc to be precise. Tests have been made thoroughly before finally submitting the bug report. Regards, -- Miklos Quartus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666104: xfce4-utils: xfce4 should not start ssh-agent if does not exist
Package: xfce4-utils Version: 4.8.3-2 Severity: normal Dear Maintainer, This bug report has been submitted by the 'bugreport' program. The issue is that ssh-agent (or ssh) is not installed on my PC, but xfce4 during start up tries to invoke it and fails. I get the following error in my .xsession-errors. /etc/xdg/xfce4/xinitrc: 1: /etc/xdg/xfce4/xinitrc: ssh-agent: not found this happens at line 171. Otherwise xfce4 and everything else on my system is working fine, I can use the X environment without having ssh on my system. I suggest to fix it by setting line 139 as follows. CHANGE if test -z $ssh_agent_type; then TO if ! test -z $ssh_agent_type; then With the fix above, the condition later see and will not try to start ssh-agent. Other suggestion is to make the package *dependant* on the ssh package. Currently this package does not depend on ssh, see below. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xfce4-utils depends on: ii dpkg 1.16.1.2 ii exo-utils0.6.2-4 ii libc62.13-27 ii libdbus-1-3 1.4.18-1 ii libdbus-glib-1-2 0.98-1 ii libglib2.0-0 2.30.2-6 ii libgtk2.0-0 2.24.10-1 ii libxfce4ui-1-0 4.8.1-1 ii libxfce4util44.8.2-1 ii procps 1:3.3.2-3 ii x11-xserver-utils7.6+3 ii xinit1.3.1-1 ii xterm [x-terminal-emulator] 276-2 Versions of packages xfce4-utils recommends: ii dbus-x11 1.4.18-1 ii thunar 1.2.3-3 ii xdg-user-dirs 0.14-1 ii xfce4-panel4.8.6-3 ii xfwm4 4.8.3-1 ii xinput 1.5.3-1 ii xscreensaver 5.15-2 Versions of packages xfce4-utils suggests: ii xfce4-session 4.8.3-2 -- Configuration Files: /etc/xdg/xfce4/xinitrc changed [not included] -- no debconf information Thanks, -- Miklos Quartus signature.asc Description: Digital signature
Bug#600927: gdm3: mouse cursor remains a 'clock'
On Wed, Dec 22, 2010 at 12:30:39PM +0100, Josselin Mouette wrote: Does removing the “X-GNOME-Autostart-Notify=true” line in /usr/share/gdm/autostart/LoginWindow/metacity.desktop help? No. In all cases I don’t think it’s a good idea to have gdm3 without metacity. Maybe it should be made a dependency. Yes, perhaps. Installing the 'metacity' package and restarting gdm3 service has solved the problem. I guess we should go for requesting to update the dependencies for the gdm3 package in order to fix and close this bug. Currently 'metacity' is a suggestion only: [...@szonja: ~]$ apt-cache depends gdm3 (...) Suggests: libpam-gnome-keyring Suggests: metacity ^^ Suggests: gnome-mag Suggests: gnome-orca (...) Regards -- Miklos Quartus Linux/FreeBSD System Administrator signature.asc Description: Digital signature
Bug#600927: gdm3: mouse cursor remains a 'clock'
Package: gdm3 Version: 2.30.5-6 Severity: minor Hi I experience the same problem after a clean install of Debian Squeeze from squeeze-di-beta2 i386 CD. Cursor remains a 'clock' in the login screen even after login-logout. I have no metacity. Otherwise no impact on overall behaviour of the system. FYI, in /var/log/gdm3/:0-greeter.log gnome-session complains about not being able to launch metacity as below: gnome-session[1832]: WARNING: Could not launch application 'metacity.desktop': Unable to start application: Failed to execute child process metacity (No such file or directory) . My X.Org core version is 2:1.7.7-10 (xserver-xorg-core) and 1:7.5+8 (xserver-xorg). Kernel version is 2.6.32-5-686, libc6 version is 2.11.2-7 . Perl version is 5.10.1. My X Window Manager is xfce4, version 4.6.2 . At this moment I have no suggestion for a fix. Thank you for your help and support. Regards -- Miklos Quartus Linux/FreeBSD System Administrator signature.asc Description: Digital signature
Bug#350119: eliminate grep error message
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: apache2-common
Version: 2.0.55-4
Severity: minor
Hi,
You might as well eliminate the grep error message. This comes when
there is no config file found in /etc/apach2/conf.d directory. The error
message is displayed on console or normal output when I stop apache2:
# /etc/init.d/apache2 stop
Stopping apache 2.0 web server...grep: /etc/apache2/conf.d/[^.#]*: No
such file or directory
.
Here is a simple patch with modifies the script to feed PIDFILE variable
content (which uses grep command) only when the config file actually
exists, checking the i variable. (Patch attached.)
$ diff /etc/init.d/apache2 /etc/init.d/apache2.new
40c40,42
PIDFILE=`grep -i ^PidFile $i | tail -n 1 | awk '{print $2}'`
- ---
if [ -f $i ]; then
PIDFILE=`grep -i ^PidFile $i | tail -n 1 | awk '{print
$2}'`
fi
- -- System Information --
Debian Release: testing/unstable
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: 2.6.15-1-686
C library version: 2.3.6-3
Locale: LANG=en_US.UTF-8, LC_CTYPE=hu_HU.UTF-8 libc6 (= 2.3.5-1),
Versions of packages apache2-common depends on:
libdb4.3 (= 4.3.28-1), libexpat1 (= 1.95.8), debconf,
debianutils (= 1.6), mime-support, openssl, net-tools,
ssl-cert (= 1.0-7), libmagic1, libgcc1 (= 1:3.3.5),
apache2-utils (= 2.0.55-4), lsb-base (= 2.0)
BR,
Miklos
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFELZ61BVP7q1vdH4sRAg03AKDT5R6MPY7PBsqqeo/SKccgaHaNMgCfWkH+
Ks2viAmPxn45AKQiOph+pK0=
=ZRKO
-END PGP SIGNATURE-
40c40,42
PIDFILE=`grep -i ^PidFile $i | tail -n 1 | awk '{print $2}'`
---
if [ -f $i ]; then
PIDFILE=`grep -i ^PidFile $i | tail -n 1 | awk '{print $2}'`
fi
