Re: Unattended-upgrades do not seem to be able to restart services
Hello, On 16-06-08 22:11:33, Jesper Dybdal wrote: > At the end of unattended-upgrades-dpkg.log, I see: > > >Services to be restarted: > >Skipping dbus.service... > >systemctl restart apache2.service cron.service > >Log ended: 2016-06-08 04:36:36 > > However, apache2 and cron have not been restarted [..] It's not unattended-upgrades, what you're seeing is the output of needrestart, which is configured by default to only showing what it would do, but not actually restarting anything. Take a look at the configuration below /etc/needrestart. Cheers Wolfgang signature.asc Description: Digital signature
Re: apt-cacher-ng not expiring any more
Hi David, On 15-09-11 11:06:58, David Wright wrote: > The wheezy-backports-sloppy version, 0.8.3-1~bpo7+1 (i386) worked > well, but only until Sept 5/6; on this occasion, the disppearing file > is debrep/dists/jessie/InRelease: > > Bringing index files up to date... > Checking/Updating debrep/dists/jessie/InRelease... 404 Not Found Faced with the same problem, it seems removing the files that acng is complaining about from the local cache hierarchy stops it from trying to refresh it. This even worked with the backports (non-sloppy) version AFAICT. Cheers Wolfgang signature.asc Description: Digital signature
Re: dovecot-imapd and imaps protocol
Hello, On 14-02-13 20:32:45, Alan Chandler wrote: I am trying to figure out if the dovecot-imapd is able to support the imaps protocol It is. all the guides say put the following at the head of /etc/dovecot/dovecot.conf protocols = imap imaps (and pop3 etc but I am not interested in that) That looks like written for dovecot 1.x, the wheezy version which has !include_try /usr/share/dovecot/protocols.d/*.protocol is 2.x. The configuration syntax changed quite a bit, but can be converted if you have a working old setup using doveconf, see README.Debian.gz. So why doesn't it specify imaps. Am I missing another package which does that? Basically, you shouldn't need to do anything, because the imap-login service is defined in /etc/dovecot/conf.d/10-master.conf in Debian, allowing both imap and imaps. It's just that it's not an additional protocol config setting as it was in 1.x. What makes you think that imaps isn't working, did you try connecting and got a connection refused? Cheers Wolfgang signature.asc Description: Digital signature
Re: touch /var/lib/sudo/$USER / use sudo when unlocking xscreensaver (xfce)
Hello,
On Sun, Apr 21, 2013 at 11:22:23AM +1000, Zenaan Harkness wrote:
I run sid XFCE, and have some keyboard shortcuts for
docked-with-external-monitor, no-external-monitor (.screenlayout
files) and corresponding networking configs.
In rc.local, I put touch /var/lib/sudo/{my-usr} and I find this very
convenient.
I would like the same in principle, when unlocking xscreensaver.
Anyone know how to achieve this, or if it's possible without hacking some
code?
If I understand you correctly, you never want to type a password when
running your commands with sudo? Then why not just use NOPASSWD in the sudoers
file?
Cheers
Wolfgang
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130424103541.ga3...@lenny.spiney.org
Re: touch /var/lib/sudo/$USER / use sudo when unlocking xscreensaver (xfce)
Hello, On Wed, Apr 24, 2013 at 10:56:30PM +1000, Zenaan Harkness wrote: If I understand you correctly, you never want to type a password when running your commands with sudo? Not quite. I want sudo 'activated' when I enter my password. Ie, when I log in to XFCE, or when I unlock the xscreensaver, I have in both cases just entered my password. So because I just entered my password, I expect sudo to be 'activated'. Ah, now I get it. :) I suppose there's a way to do this using xscreensaver-command -watch and some scripting, but if you have only a couple of scripts that need to run rather often (and are not very dangerous, i.e. allow no interactivity or shell commands), then I'd still use NOPASSWD for those specific scripts in sudoers. After all, it's not like you can only have one line in sudoers per user/group. :) Cheers Wolfgang -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130424161128.ga17...@lenny.spiney.org
Re: NFS automount not happening
On 12/11/2012 11:08 AM, Chris Davies wrote: Bob Proulx b...@proulx.com wrote: The dhcpd will ping the address after the lease has expired and before assigning it again and will notice that it is still in use and will avoid assigning that address to another client. ICMP ping? Are you sure? I suppose Bob was referring to the ping-check as per the ISC dhcpd, see http://manpages.debian.net/cgi-bin/man.cgi?query=dhcpd.conf The client has to renew the lease, indeed, but the server also tries to make sure there are no duplicate IPs in the network. Cheers Wolfgang -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50c72cbf.9020...@karall-edv.at
Re: Works on .htaccess but not in sites-available
Hello, On 10/30/2012 10:02 PM, Jorge wrote: In /var/www/www.etxea.org/htdocs/.htaccess I've got the following content ... [..] RewriteCond $1 !^(index\.php|images|robots\.txt|user_guide) RewriteRule ^(.*)$ /index.php/$1 [L] [..] VirtualHost * RewriteCond $1 !^(index\.php|images|robots\.txt|user_guide) RewriteRule ^(.*)$ /index.php/$1 [L] Matches in VirtualHost context start with /, i.e. you have to use !^/(index\.php|images|robots\.txt|user_guide) See http://httpd.apache.org/docs/current/mod/mod_rewrite.html#rewriterule (the box What is matched?) Cheers Wolfgang -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50938336.3000...@karall-edv.at
Re: [OT] munin
Hello, why's this OT? :) On Sat, Mar 03, 2012 at 11:01:07PM -0500, Brad Alexander wrote: this is on both the working and non-working nodes. My network is not running ipv6. In fact, net-pf-10 is commented out on all the hosts that I have checked. IIRC, to actually disable IPv6 you need to actually uncomment the line, replacing the ipv6 with off, like alias net-pf-10 off Can anyone tell me why these 5 nodes will not connect to the server and refuses connections to localhost and ::1? What does grep ^allow /etc/munin/munin-node.conf produce on the machines? Cheers Wolfgang -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120304084825.ga16...@lenny.spiney.org
Re: [OT] munin
On Sun, Mar 04, 2012 at 07:11:49AM -0500, Brad Alexander wrote: alias net-pf-10 off Ah. I figured if the net-pf-10 was commented out, it was taken out of play. No, you actually have to turn it off, commented out means use the defaults, i.e. IPv6 is available. Not that it matters I guess. The netstat output for many servers shows only TCP6/UDP6, but they still work on IPv4 as well (there are 2 ways to create the sockets, I can't remember the details), e.g. apache: lenny:~# netstat -tulpen | grep apache tcp6 0 0 :::80:::* LISTEN 0 2062901 7794/apache2 tcp6 0 0 :::443 :::* LISTEN 0 2062905 7794/apache2 The only one not commented out is allow ^192\.168\.4\.63$ Where 192.168.4.63 is the munin server. And from the munin server, what does echo -e 'list\nquit' | nc address according to munin.conf 4949 yield for the working/non-working hosts, any difference? Cheers Wolfgang PS: no need to CC me, I'm subscribed to the list. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120304205247.ga9...@lenny.spiney.org
Re: [OT] munin
On Sun, Mar 04, 2012 at 06:44:47PM -0500, Brad Alexander wrote: Yes. Non-working: echo -e 'list\nquit' | nc 192.168.4.9 4949 (UNKNOWN) [192.168.4.9] 4949 (munin) : Connection refused Hmm, since Bob suggest a bug in recent versions (I don't know, not running wheezy or sid on any munin-node installations at the moment), could you try disabling IPv6 and try again? And if this is really a bug with munin-node not working with IPv6 enabled this needs to be reported to the BTS. Cheers Wolfgang -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120305063010.ga4...@lenny.spiney.org
Output of /sbin/route reversed?
Hello, I just noticed on my notebook running up-to-date sid that the output of route changed compared to what I've been used to for ages, in that it shows the default gateway as top-most line: x61s:/etc# /sbin/route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 10.135.15.254 0.0.0.0 UG0 00 eth0 [..rest of the about 15 entries get printed below..] Is this something I missed regarding the kernel routing table? Or is this some problem with my setup? (plain ifupdown configuration plus OpenVPN, but it's the same w/out OpenVPN) Cheers Wolfgang -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111013065756.ga13...@lenny.spiney.org
Re: Output of /sbin/route reversed?
On Thu, Oct 13, 2011 at 02:43:12PM +, Camaleón wrote: On Thu, 13 Oct 2011 08:57:56 +0200, Wolfgang Karall wrote: I just noticed on my notebook running up-to-date sid that the output of route changed compared to what I've been used to for ages, in that it shows the default gateway as top-most line: x61s:/etc# /sbin/route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 10.135.15.254 0.0.0.0 UG0 00 eth0 [..rest of the about 15 entries get printed below..] Is this something I missed regarding the kernel routing table? Or is this some problem with my setup? (plain ifupdown configuration plus OpenVPN, but it's the same w/out OpenVPN) I also get the same on my wheezy (gateway displays first). Curiously, ip ro is also affected and shows the default route in the first row. Maybe an intended change from the net stack? I didn't see anything in the NEWS when updating in the last couple of months and I only realized this recently, so I wonder where this change is documented. After all, this will break loads of custom scripts fetching the gateway address from the last line of the output of route. Not that these scripts shouldn't be improved to at least search for ^0\.0\.0\.0 instead, which will still break since I suppose multiple default gateways get sorted in the wrong order now too... Any idea where to ask how this change came to be, or which package to report a bug against? Cheers Wolfgang -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111013150339.ga31...@lenny.spiney.org
Re: udev rules for 2 identical webcams + 1 spare cam
Hi,
On 07/14/2011 08:59 PM, Tuxoholic wrote:
SUBSYSTEM==video4linux, ATTRS{idVendor}==046d, \
ATTRS{idProduct}==08a2, Name=video1, GROUP=video
SUBSYSTEM==video4linux, ATTRS{idVendor}==046d, \
ATTRS{idProduct}==08a2, Name=video2, GROUP=video
I suppose using the same set of attributes for the 2 identical cameras
twice leads to unpredictable or at least unwanted results. I'd suggest
using the serial number of the cameras as additional attribute to get a
perfect match.
Cheers
Wolfgang
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e1fee70.7060...@karall-edv.at
Re: OT: Safe to access SSH server from work?
On Fri, May 06, 2011 at 01:08:52PM +0100, Brian wrote: Keyloggers would get the key passphrase too. And the USB stick would have its contents pilfered. So, keys don't appear to give any advantage over passwords on an untrusted machine. For the connect from untrusted computers there are one-time-passwords. I've used libpam-opie in the past with great success for the occasional connection from internet cafe's for example. Cheers Wolfgang -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110506131122.ga7...@lenny.spiney.org
Re: OT: Safe to access SSH server from work?
Hello, On Fri, May 06, 2011 at 05:00:18PM +0100, Dom wrote: However, libpam-opie seems to have been dropped by Debian after squeeze, due to lack of support, some security issues, and no updates for quite a few years. I run Wheezy, is there a supported alternative to libpam-opie? A quick apt-cache search turns up libpam-otpw and otwp-bin available in sid, haven't used them (yet) though. Cheers Wolfgang -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110506203739.ga25...@lenny.spiney.org
Re: xmodmap settings are forgotten/lost during session
Hello, trying to investigate this further, I set up a Cron job running every minute executing the following commands: DISPLAY=:0.0 xmodmap /dev/null 21 \ DISPLAY=:0.0 xmodmap -pke | grep -q F19 || echo xmodmap gone \ DISPLAY=:0.0 xmodmap ~/.Xmodmap I.e. I check whether my mapping for F19 is still and generate some output to get an email from Cron every time the settings are gone, reloading the settings in the last line. The first is just a check whether there's actually a X11 session on the first DISPLAY. And I get a regular pattern, exactly every 10 minutes my xmodmap settings get flushed. Of course I searched for other Cron jobs, but to no avail. What else could reset my keyboard settings every 10 minutes? Or has anyone an idea how to debug this further? Cheers Wolfgang -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110503182801.ga29...@lenny.spiney.org
Re: xmodmap settings are forgotten/lost during session
Hello, On 04/28/2011 02:06 AM, Steve Kleene wrote: On Wed, 27 Apr 2011 21:20:46 +0200, Wolfgang Karall wrote: after upgrading ... I lost my F19/F20 mapping done via xmodmap About a week ago my ~/.Xmodmap, which turns off Caps Lock, started being ignored. It is not even accessed (as judged by ls -lu) when I start X. The problem is not so much that ~/.Xmodmap is not read when X starts (I could work around that I guess), but that the mappings I have set up with xmodmap are vanishing while I'm using my notebook. So something resets my mappings on a more or less regular basis (I'll probably set up a cronjob with xmodmap -pke to find out some timing here) without me ever telling my system to do so. Cheers Wolfgang -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4db90b8b.1070...@karall-edv.at
xmodmap settings are forgotten/lost during session
Hello, after upgrading my Debian sid machine to the latest packages (see list below according to dpkg.log) I lost my F19/F20 mapping done via xmodmap for the Forward/Back keys of my notebook. After investigation the issue I ran xmodmap ~/.Xmodmap on my settings manually and it worked, but after a while (since I don't use those keys anywhere apart from the browser I don't quite tell how much time passed) the keys stopped working again, also xmodmap -pke didn't list the key mappings any longer. And this happens all the time, I can set up the mappings, but after a while they're gone. Nothing special seem to trigger this (not resuming from S3, for example), just time passing long enough seems to make something on my system reset the mappings. I'm not sure what might be the culprit here, and I don't quite know how to debug this (there's no way to listen to this kind of reconfiguration event I guess?), does anybody here have an idea if the latest XFCE updates might be the cause? Cheers Wolfgang PS: the list of packages that got upgraded after which the problem started showing up, most are probably completely unrelated: audacity audacity-data binutils bluez-hcidump bzr ca-certificates concordance cpp-4.5 cups-pdf curl dbus dbus-x11 debhelper desktop-file-utils diffpdf djvulibre-bin exo-utils ftp fuse-utils g++-4.5 gcc-4.5 gcc-4.5-base gcc-4.6-base ghostscript ghostscript-cups ghostscript-x gnokii gnokii-cli gnokii-common gnome-keyring gnome-menus gs-common gs-gpl gtk2-engines-xfce hicolor-icon-theme initramfs-tools install-info libboost-filesystem1.46.1 libboost-regex1.46.1 libboost-system1.46.1 libconcord2 libcurl3 libcurl3-gnutls libdb4.6 libdb4.7 libdb4.8 libdb5.1 libdbus-1-3 libdjvulibre21 libdjvulibre-text libexo-1-0 libexo-common libextutils-depends-perl libfuse2 libgarcon-1-0 libgarcon-common libgcc1 libgck0 libgcr-3-0 libgfortran3 libglib2.0-0 libgnokii6 libgnome-keyring0 libgomp1 libgs9 libgs9-common libgudev-1.0-0 libhtml-tree-perl libkeybinder0 liblucene2-java libmediainfo0 libnet-domain-tld-perl libnet-http-perl libpam-gnome-keyring libperl5.10 libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0 libpq5 libpython2.6 libquadmath0 libquvi0 libreadline5 libreadline6 libsqlite3-0 libstdc++6 libstdc++6-4.5-dev libtasn1-3 libthunar-vfs-1-2 libthunar-vfs-1-common libthunarx-2-0 libudev0 libwireshark0 libwireshark-data libwiretap0 libwsutil0 libxfce4ui-1-0 libxfce4util4 libxfce4util-common libxfcegui4-4 libxfconf-0-2 lintian linux-headers-2.6.38-2-686 linux-headers-2.6.38-2-common linux-image-2.6.38-2-686 linux-libc-dev man-db mediainfo menu mkvtoolnix mkvtoolnix-gui orage pcmciautils perl perl-base perl-modules perl-suid policykit-1 python2.6 python2.6-minimal python-argparse python-bzrlib python-cairo python-central python-gconf python-glade2 python-gnome2 python-gtk2 python-pyorbit python-support rdesktop readline-common shared-mime-info sqlite3 sshfp stunnel4 sun-java6-bin sun-java6-jre sun-java6-plugin thunar thunar-data thunar-volman tnef tzdata tzdata-java ucf udev virtualbox-4.0 wireshark wireshark-common xfce4 xfce4-appfinder xfce4-artwork xfce4-clipman xfce4-clipman-plugin xfce4-mixer xfce4-panel xfce4-session xfce4-settings xfce4-utils xfce4-volumed xfce4-xkb-plugin xfce-keyboard-shortcuts xfconf xfdesktop4 xfdesktop4-data xfprint4 xfwm4 xfwm4-themes xgnokii x-ttcidfont-conf -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110427192046.ga11...@lenny.spiney.org
dpkg bug regarding dependencies?
Hello, when trying to work around http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620088 I downgraded nfs-common to the version in testing, which actually worked, even though nfs-kernel-server has a versioned dependency on nfs-common (see below), is this a bug in dpkg or did I miss something regarding the versioned dependency handling? I actually only noticed since aptitude forbid-version did bail out telling me that there is a dependency problem. Cheers Wolfgang PS: the shell output: x61s:~# apt-cache policy nfs-common nfs-kernel-server nfs-common: Installed: 1:1.2.3-1 Candidate: 1:1.2.3-1 Version table: *** 1:1.2.3-1 0 500 http://ftp.at.debian.org/debian/ sid/main i386 Packages 100 /var/lib/dpkg/status nfs-kernel-server: Installed: 1:1.2.3-1 Candidate: 1:1.2.3-1 Version table: *** 1:1.2.3-1 0 500 http://ftp.at.debian.org/debian/ sid/main i386 Packages 100 /var/lib/dpkg/status x61s:~# apt-cache show nfs-kernel-server | grep ^Depends Depends: libblkid1 (= 2.16), libc6 (= 2.3), libcomerr2 (= 1.01), libgssapi-krb5-2 (= 1.6.dfsg.2), libgssglue1, libk5crypto3 (= 1.6.dfsg.2), libkrb5-3 (= 1.6.dfsg.2), libnfsidmap2, libtirpc1, libwrap0 (= 7.6-4~), nfs-common (= 1:1.2.3-1), ucf, lsb-base (= 1.3-9ubuntu3) x61s:~# dpkg -i nfs-common_1.2.2-5_i386.deb dpkg: warning: downgrading nfs-common from 1:1.2.3-1 to 1:1.2.2-5. (Reading database ... 177879 files and directories currently installed.) Preparing to replace nfs-common 1:1.2.3-1 (using nfs-common_1.2.2-5_i386.deb) ... Unpacking replacement nfs-common ... Setting up nfs-common (1:1.2.2-5) ... Installing new version of config file /etc/init.d/nfs-common ... Stopping NFS common utilities: statd. Starting NFS common utilities: statd. Processing triggers for man-db ... x61s:~# -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110402192217.ga3...@lenny.spiney.org
