Hi,
On 11/13/2011 12:23 PM, Markus Raab wrote:
The output (without correct sudoers present) is:
---
ADPROTO: 0.5
sudo: no tty present and no askpass program specified
ADPERR: Failed to execute 'sudo aptitude update' (256).
---
Is this sudo line ok for that protocol?
The protocol does not care about unkown output. It seems that your
/etc/sudoers config does not allow calling `sudo aptitude update` w/o
password.
To show the 'Failed to execute 'sudo aptitude update' (256).' in the CUI would
help a lot I guess.
There will be an diagnostic screen showing the detail information in
(one of) the next apt-dater releases.
I additionally noticed now that "VIRT: Physical" is not correct, it seems
unable to detect vserver properly. Shall I open a bug report for that
too?
Yes, please open a bug. It might be helpful if you supply the content of
/proc/cpuinfo and the output of dmidecode along with the opening.
Ok, I found out that apt-dater-host uses imvirt internally which seems to have
no support for vserver at all.
cpuinfo gives no clue (it just says what it tells on the physical server too)
and dmidecode just outputs:
# dmidecode 2.9
/dev/mem: No such file or directory
So I do not see an obvious way to support it. It would be just an low-priority
feature request of an software which likely will be obsolete/removed next
Anyway, I would like to add support for it.
Regards,
Thomas
--
[email protected] Tel. +49 351 477 77 30
www.ibh.de Fax +49 351 477 77 39
-----------------------------------------------------------------------
Dipl.-Ing. Thomas Liske
Netzwerk- und System-Design
IBH IT-Service GmbH Amtsgericht Dresden
Gostritzer Str. 67a HRB 13626
D-01217 Dresden GF: Prof. Dr. Thomas Horn
Germany VAT DE182302907
-----------------------------------------------------------------------
Ihr Partner für: LAN, WAN IP-Quality, Security, VoIP, SAN, Backup, USV
-----------------------------------------------------------------------
professioneller IT-Service - kompetent und zuverlässig
-----------------------------------------------------------------------
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
