<html><body bgcolor="#FFFFFF"><div>Actually I found out that log is written to /var/log/syslog and this was all I needed. I still have issue with number of threads over 2 (or even 1), I get segfaults, but this is different issue.</div><div><br></div><div>Jaak<br><br>On 25.01.2010, at 14:28, Jonathan-David SCHRODER <<a href="mailto:jonathan.schroder@gmail.com">jonathan.schroder@gmail.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>get back into your screen with screen -r renderd_screen (or screen -r rend <= string that starts with the name of you screen session, as you can read it in screen -ls or screen -list)<br><br><div class="gmail_quote">On Mon, Jan 25, 2010 at 1:27 PM, Jonathan-David SCHRODER <span dir="ltr"><<a href="mailto:jonathan.schroder@gmail.com"><a href="mailto:jonathan.schroder@gmail.com">jonathan.schroder@gmail.com</a></a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Jaak,<br><br>Instead of hacking your own renderd service start/stop/.. script (eg. creating a file /etc/init.d/renderd)...<br>
...you can just run renderd in a screen (apt-get install screen) in -f(oreground) and redirect its output with redirection to some file while keep it going to stdout.<br>
<br>screen -S renderd_screen #creates a screen named renderd_screen<br>#run this in screen now<br>./renderd -f 2>&1 | tee -a /var/log/renderd<br># -f => runs renderd in foreground, 2>&1 copies stderr to stdout, | tee -a ... takes previous process's stdout and puts it into /var/log/renderd<br>
#and (D)etach your screen with Ctrl+A then D<br>
<br>If you did not know screen, google for linux screen tutorial to get help on using screen.<br><br>Take care<br><font color="#888888"><br>Jonathan</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">
On Tue, Jan 12, 2010 at 12:08 PM, Jaak Laineste <span dir="ltr"><<a href="mailto:jaak.laineste@gmail.com" target="_blank"><a href="mailto:jaak.laineste@gmail.com">jaak.laineste@gmail.com</a></a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br>
Is there a way to save renderd debug log to a file? I can see the<br>
debug log when I start renderd with -f option, but I'd like to run it<br>
as normal service, silently, but have debug log in e.g.<br>
/var/log/renderd.log<br>
<br>
I was getting occasional Segmentation Faults in renderd (when I use<br>
>2 threads), this may be useful for troubleshooting.<br>
<font color="#888888"><br>
--<br>
Jaak Laineste<br>
<br>
_______________________________________________<br>
dev mailing list<br>
<a href="mailto:dev@openstreetmap.org" target="_blank"><a href="mailto:dev@openstreetmap.org">dev@openstreetmap.org</a></a><br>
<a href="http://lists.openstreetmap.org/listinfo/dev" target="_blank"><a href="http://lists.openstreetmap.org/listinfo/dev">http://lists.openstreetmap.org/listinfo/dev</a></a><br>
</font></blockquote></div><br>
</div></div></blockquote></div><br>
</div></blockquote></body></html>