I recently botched a jail build (amazing what can happen when you misspell DESTDIR ) while building the distribution target in /etc. This obviously overwrote my password databases, which I (mostly) recovered with a bit of help from the proftpd password file.
It appears that as a result of this, the DirectAdmin daemon does nothing more than continuously read /etc/spwd.db (a la ktrace). It dumped core once, but the stack was extremely long (and obviously without debugging symbols) to make any use of it.
Might you guys know why this is? I have no issues administrating my server by console, but my customers obviously do .
Kind regards,
Devon H. O'Dell
It appears that as a result of this, the DirectAdmin daemon does nothing more than continuously read /etc/spwd.db (a la ktrace). It dumped core once, but the stack was extremely long (and obviously without debugging symbols) to make any use of it.
Might you guys know why this is? I have no issues administrating my server by console, but my customers obviously do .
Kind regards,
Devon H. O'Dell