I don't think the RPi really counts as an "embedded platform" in this respect. It may be small in size, but beyond that it's a pretty full-featured platform. More power in them than the first thing I had on a nailed up internet connection.
On Sat, Aug 22, 2015 at 2:44 PM, Sam Walton <[email protected]> wrote: > Yes, your and Tilghman's response have more context than a straight SO > answer. That's the beauty of this group. > > I had tried different variations of your SO answer, but it did work. I'm > grateful to award your answer. Thx to both, sam > > On Friday, August 21, 2015 at 8:04:51 PM UTC-5, Csaba Toth wrote: >> >> Resource limits could be a problem too. Check ulimit and it's options. >> Note, it's important which user privileges the postgres daemon has, check >> that user. But I only hit open file limits with wkhtml2pdf with large pdfs >> (200+ pages). I also hit DB specific size limits when restoring full DB >> (10+ GB), that was DB specific resource limit though. In every case >> somehwere there's an error messages. >> >> On Fri, Aug 21, 2015 at 12:10 PM, Tilghman Lesher <[email protected]> >> wrote: >> >>> Another thing to check are the kernel resource limits. As this is an >>> embedded platform, I suspect some of the kernel resources are reduced >>> in size, at least initially: >>> >>> http://www.postgresql.org/docs/9.1/static/kernel-resources.html >>> >>> On Fri, Aug 21, 2015 at 12:52 PM, Sam Walton <[email protected]> wrote: >>> > I'm getting my Raspberry Pi ready for service using Wheezy and have >>> hit a >>> > brick wall on getting my Postgresql server to startup again. I wouldn't >>> > bother the list with this as most are not PG experts but after posting >>> > details of my problem on Superuser I'm guessing my problem is not easy >>> to >>> > solve, thus I bug the Linux experts on what to try next. >>> > >>> > >>> http://superuser.com/questions/958511/postgresql-9-1-raspberry-pi-could-not-bind-ipv4-socket >>> > >>> > I've done the obvious thinks like use lsof to check for open ports. >>> The lack >>> > of interest indicates that this is something I've goofed on. However, >>> it was >>> > running a couple of weeks ago. Looking at my bash history, the only >>> thing I >>> > done in the mean time was to modify some files so that I can run my >>> little >>> > real-time-clock. Which works pretty well, btw. >>> > >>> > Checking Google for any reason port 5432 is not available for PG in >>> > conjunction with RTC yield nothing. Changing the port PG uses didn't >>> work >>> > either. >>> > >>> > So, what other resources other than the StackOverflow family could I >>> query >>> > for pointers on what to check to find more clues for what could be the >>> > issue? >>> > >>> > thx, sam >>> > >>> > -- >>> > -- >>> > You received this message because you are subscribed to the Google >>> Groups >>> > "NLUG" group. >>> > To post to this group, send email to [email protected] >>> > To unsubscribe from this group, send email to >>> > [email protected] >>> > For more options, visit this group at >>> > http://groups.google.com/group/nlug-talk?hl=en >>> > >>> > --- >>> > You received this message because you are subscribed to the Google >>> Groups >>> > "NLUG" group. >>> > To unsubscribe from this group and stop receiving emails from it, send >>> an >>> > email to [email protected]. >>> > For more options, visit https://groups.google.com/d/optout. >>> >>> >>> >>> -- >>> Tilghman >>> >>> -- >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "NLUG" group. >>> To post to this group, send email to [email protected] >>> To unsubscribe from this group, send email to >>> [email protected] >>> For more options, visit this group at >>> http://groups.google.com/group/nlug-talk?hl=en >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "NLUG" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > -- > You received this message because you are subscribed to the Google Groups > "NLUG" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nlug-talk?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "NLUG" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Sent from an actual computer. -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
