2011/4/28 Edvin Dunaway <span dir="ltr"><<a href="mailto:edvin@eddinn.net">edvin@eddinn.net</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I was thinking of the following structure for default locations of files and binaries, for starters:<br><br>/etc/init.d/pagekited<br>
/etc/logrotate.d/pagekite<br>/etc/pagekite/<br><div style="margin-left: 40px;">-pagekite.conf (if needed?)<br></div><div style="margin-left: 40px;">-pagekite.rc<br></div><div style="margin-left: 40px;">-local.rc<br></div>
/home/user/pagekite/wwwroot/ (optional for the built in pyhttp daemon?)<br>/home/user/pagekite/.pagekite.rc<br>/usr/bin/pagekited<br>/var/log/pagekite/kitename.log<br>/var/run/pagekited.pid<br></blockquote><div><br>I would skip the /home/user/... files completely. Those users who want to use pagekite interactively will create folders and config themselves (possibly by asking the tool to do it).<br>
<br>I don't think packages generally touch user's home directories much - and since we're not assuming everyone uses the tool we shouldn't touch the default skeleton user configuration either.<br><br></div>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">most of this can be done via .rc/.conf and daemon parameters<br>
BRE: what's your input on this?<br></blockquote><div><br></div></div>-- <br>Bjarni R. Einarsson<br>The Beanstalks Project ehf.<br><br>Making personal web-pages fly: <a href="http://pagekite.net/" target="_blank">http://pagekite.net/</a><br>