This bug still exist. Debian 4.0r2 danted -v >danted: dante v1.1.18 danted -d >Jan 20 11:36:55 (1200829015) danted[0]: socks_seteuid(): old: 0, new: 13 >Jan 20 11:36:55 (1200829015) danted[0]: socks_reseteuid(): current: 13, new: 0 >Jan 20 11:36:55 (1200829015) danted[0]: socks_seteuid(): old: 0, new: 65534 >Jan 20 11:36:55 (1200829015) danted[0]: socks_reseteuid(): current: 65534, >new: 0 >Jan 20 11:36:55 (1200829015) danted[0]: socks_seteuid(): old: 0, new: 65534 >Jan 20 11:36:55 (1200829015) danted[0]: socks_reseteuid(): current: 65534, >new: 0 >Jan 20 11:36:55 (1200829015) danted[0]: fixsettings(): no external address >given >Jan 20 11:36:55 (1200829015) danted[0]: sockdexit(): terminating
(addition, dante don't start at all, even when run manually, with proper danted.conf) What about maintainer? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
