Re: vbox cannot find headers, although they are installed

2018-01-07 Thread x9p
On Sat, January 6, 2018 11:36 pm, Harry Putnam wrote: ... > (Look at /var/log/vboxadd-install.log to find out what went wrong) ... the line above can explain a lot. cheers. -- x9p | PGP : 0x03B50AF5EA4C8D80 / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE "I don't know wh

Re: is there any Windows virus that affect linux?

2017-12-13 Thread x9p
> Stefan We know. Poor Assange... but it was a beautiful job. cheers. -- x9p | PGP : 0x03B50AF5EA4C8D80 / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE

Re: is there any Windows virus that affect linux?

2017-12-13 Thread x9p
> <https://www.xkcd.com/538/> I luv that comic :) cheers. -- x9p | PGP : 0x03B50AF5EA4C8D80 / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE

Re: is there any Windows virus that affect linux?

2017-12-12 Thread x9p
ite easy) PE --> ELF infection on ext? partition on same disk, unencrypted (bit more of work) cheers. -- x9p | PGP : 0x03B50AF5EA4C8D80 / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE

Re: Upgraded to stretch but apache2 still uses php5

2017-12-04 Thread x9p
if there is still something there with: # egrep -rs php5 /etc/apache2/ also in hole system: dpkg -l | egrep php5 If so, repeat process of upgrade the packages, restart apache2 PS: Assuming your apps works with php7 cheers. x9p > I thought I'd try a better webmail than squirrelmail, so

Re: estamated number of Linux users?

2017-10-27 Thread x9p
On 2017-10-27 16:41, John Hasler wrote: Ric writes: I wouldn't demean the Linux Counter effort calling it "Utterly useless". It's a simple statement of fact. The Linux Counter data is utterly useless for the purpose of estimating the number of Linux users. :%s/Linux/active Linux/g

Re: estamated number of Linux users?

2017-10-27 Thread x9p
On 2017-10-27 14:27, Ric Moore wrote: On 10/26/2017 11:21 PM, John Hasler wrote: Celejar writes: https://www.linuxcounter.net/ I don't know how meaningful its data are. Utterly useless. I wouldn't demean the Linux Counter effort calling it "Utterly useless". Those folks have maintained the

Re: Wifi works in Ubuntu and not in Debian

2017-09-21 Thread x9p
> Since now, I thank in advance. > > Regards, > Claudio Ferreira > cheers. x9p

Re: sudo slow on DNS lookup, with invalid resolv.conf entries

2017-09-18 Thread x9p
with his resolv.conf? Have I missed that? > Hardcoded company nameserver in /etc/resolv.conf that only works when VPN is up. VPN was down and problem appeared. x9p

Re: sudo slow on DNS lookup, with invalid resolv.conf entries

2017-09-18 Thread x9p
c/hosts 127.0.0.1 localhost localhost.localdomain 127.0.1.1 localhost ::1 localhost ip6-localhost ip6-loopback root@localhost:~# x9p

Re: sudo slow on DNS lookup, with invalid resolv.conf entries

2017-09-18 Thread x9p
t equal to "localhost.dom.ain". - Thanks for the memo. Seems the solution is to not call machine localhost, if insist in doing so, be sure it contains a "localhost.localdomain" line in /etc/hosts. I believe topic is closed with this. Thanks x9p

Re: sudo slow on DNS lookup, with invalid resolv.conf entries

2017-09-18 Thread x9p
use case and see why you get invalid > setup. The problem might be somewhere else. > > regards > > My chosen machine name was "localhost", problem partially lies here. x9p

Re: sudo slow on DNS lookup, with invalid resolv.conf entries

2017-09-17 Thread x9p
o, the change in /etc/hosts from (default in stretch): 127.0.0.1 localhost to (my system): 127.0.0.1 localhost localhost.localdomain is justifiable as it breaks (not literally break, just adds lot of delay) to sudo in a non-networked environment. x9p

Re: sudo slow on DNS lookup, with invalid resolv.conf entries

2017-09-17 Thread x9p
erver: root@localhost:~# head -1 /etc/hosts 127.0.0.1 localhost localhost.localdomain Should be on debian by default in my opinion. x9p

Re: sudo slow on DNS lookup, with invalid resolv.conf entries

2017-09-15 Thread x9p
nful way (I won't even try to predict what you could > break in your setup) to fix this is to ensure that your hostname is > 'localhost' verbatim. > I still think correct way is sudo not try to access network functions in a setup where it does not need to - waste of time, code, and opens it to more bugs. Thanks for the analysis Reco. x9p

Re: sudo slow on DNS lookup, with invalid resolv.conf entries

2017-09-15 Thread x9p
localhost". > No changes were made to the /etc/sudoers except this: myuser ALL=(ALL) NOPASSWD:ALL I did not touched any Host_List. Debian by default do not come with localhost on /etc/sudoers. sudo binary does come with the "localhost" string in it. root@localhost:~# strings /usr/bin/sudo | egrep localhost localhost x9p

Re: sudo slow on DNS lookup, with invalid resolv.conf entries

2017-09-15 Thread x9p
debian-user@lists.debian.org is sufficient. There's no > need to CC me, I'm subscribed to the list. > Sorry for that. I just hit "reply all", fixing. x9p

Re: sudo slow on DNS lookup, with invalid resolv.conf entries

2017-09-15 Thread x9p
loopback > > Curious. Can you reproduce the behaviour if sudo is run as root? > I propose to simplify things a bit (needs to be run as root): > strace was already run as root (did "sudo su" as root to prove the point), otherwise strace would fail with "effective uid is not 0". x9p

Re: sudo slow on DNS lookup, with invalid resolv.conf entries

2017-09-15 Thread x9p
nf hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname root@localhost:~# grep localhost /etc/hosts 127.0.0.1 localhost 127.0.1.1 localhost ::1 localhost ip6-localhost ip6-loopback x9p

sudo slow on DNS lookup, with invalid resolv.conf entries

2017-09-15 Thread x9p
I was getting > 30sec to complete "sudo su" on a host. This host had invalid entries in resolv.conf and I realized sudo was doing 5 seconds lookup on each entry searching for "localhost.localdomain" sudo is 1.8.19p1 @ stretch. Believe no DNS lookups should be made... even for localhost sendmms