On 24 July 2013 21:07, Szládovics Péter <p...@szladovics.hu> wrote:
> 2013-07-24 19:55 keltezéssel, Odhiambo Washington írta: > > > > > On 24 July 2013 20:42, Szládovics Péter <p...@szladovics.hu> wrote: > >> 2013-07-24 19:31 keltezéssel, Odhiambo Washington írta: >> >> >> >> >> On 24 July 2013 20:09, Szládovics Péter <p...@szladovics.hu> wrote: >> >>> 2013-07-24 18:50 keltezéssel, Odhiambo Washington írta: >>> >>> >>> >>> >>> On 24 July 2013 19:18, Szládovics Péter <p...@szladovics.hu> wrote: >>> >>>> 2013-07-24 15:55 keltezéssel, Odhiambo Washington írta: >>>> >>>> On 24 July 2013 16:53, Szládovics Péter <p...@szladovics.hu> wrote: >>>>> >>>>>> 2013-07-24 15:49 keltezéssel, Odhiambo Washington írta: >>>>>> >>>>>> On 24 July 2013 16:44, Szládovics Péter <p...@szladovics.hu> wrote: >>>>>>> >>>>>>>> 2013-07-24 15:08 keltezéssel, Odhiambo Washington írta: >>>>>>>> >>>>>>>> I have SOGoTimeZone = "Africa/Nairobi"; in sogo.conf, but that >>>>>>>>> seems >>>>>>>>> to be ignored. The platform is FreeBSD, if that matters. >>>>>>>>> >>>>>>>> >>>>>>>> I think the tzselect maybe can help to you - some minimal linuxes is >>>>>>>> contain >>>>>>>> this command (in the libc-bin package). >>>>>>>> I think the bsd is contains too. >>>>>>>> >>>>>>> >>>>>>> In FreeBSD, we use tzsetup, which writes to /etc/locatime. >>>>>>> >>>>>>> My TZ setup is fine. This appears to be a SOGo issue, I am afraid. >>>>>>> >>>>>> >>>>>> What's happen if you start the command from command line as sogo user? >>>>>> >>>>> >>>>> In my response to Christian, I have detailed it. >>>>> I however copy & paste again here: >>>>> >>>>> >>>>> root@gw:/usr/home/wash # su - sogo >>>>> [sogo@gw ~]$ /usr/local/GNUstep/Local/Tools/Admin/sogo-ealarms-notify >>>>> 2013-07-24 13:02:31.663 sogo-ealarms-notify[17614] No local time zone >>>>> specified. >>>>> 2013-07-24 13:02:31.664 sogo-ealarms-notify[17614] Using time zone >>>>> with absolute offset 0. >>>>> >>>>> However, if I specify the TZ enviroment variable, it doesn't complain: >>>>> >>>>> [sogo@gw ~]$ export TZ="Africa/Nairobi" >>>>> [sogo@gw ~]$ env >>>>> SHELL=/usr/local/bin/bash >>>>> TERM=linux >>>>> USER=sogo >>>>> FTP_PASSIVE_MODE=YES >>>>> >>>>> PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/var/db/sogo/bin >>>>> MAIL=/var/mail/sogo >>>>> BLOCKSIZE=K >>>>> PWD=/var/db/sogo >>>>> TZ=Africa/Nairobi >>>>> SHLVL=1 >>>>> HOME=/var/db/sogo >>>>> _=/usr/bin/env >>>>> [sogo@gw ~]$ /usr/local/GNUstep/Local/Tools/Admin/sogo-ealarms-notify >>>>> [sogo@gw ~]$ >>>>> >>>> >>>> TZ variable won't help. I no have it too, but all features are >>>> working fine without this error. >>>> >>>> Could you please give us a strace output? >>>> >>> >>> Any guideline on how to run the trace? >>> >>> >>> Of course. strace. >>> >>> So, you log in as sogo user, and run the command as: >>> >>> strace /usr/local/GNUstep/Local/Tools/Admin/sogo-ealarms-notify >>> 2>/path/to/output.file >>> >>> And then send the output file to us (or share it somewhere). >>> >>> Before check the strace exists on your syístem. If not, this maybe helps: >>> http://www.cyberciti.biz/faq/howto-installl-strace-under-freebsd/ >>> >> >> >> >> [sogo@gw ~]$ pwd >> /var/db/sogo >> [sogo@gw ~]$ strace >> /usr/local/GNUstep/Local/Tools/Admin/sogo-ealarms-notify >> 2>/var/db/sogo/output.file >> [sogo@gw ~]$ less output.file >> strace: open("/proc/...", ...): No such file or directory >> trouble opening proc file >> >> >> Did you see the link what I send above? The main parts are RED >> >> *WARNING!* These examples only work for i386 32 bit FreeBSD computer >> (strace is not ported to amd64 arch [64 bit]). >> Install strace >> >> First update FreeBSD ports collection and install strace from >> /usr/ports/devel/strace: >> # portsnap fetch update >> # cd /usr/ports/devel/strace >> # make install clean >> Mount /proc file system >> >> You need to mount /proc filesystem to use trace command under FreeBSD, >> enter: >> # mount -t procfs proc /proc >> >> > I did. > > root@gw:/usr/home/wash # mount | grep proc > procfs on /proc (procfs, local) > root@gw:/usr/home/wash # su - sogo > [sogo@gw ~]$ strace > /usr/local/GNUstep/Local/Tools/Admin/sogo-ealarms-notify > 2>/var/db/sogo/output.file > > outout.file contains: > > pread: Device busy > .... > pread: Device busy > pread: Device busy > pread: Device busy > PIOCRUN: Input/output error > trouble opening proc file > > > Hmmm... Should be working... > Could you please run it as root? > > Same result! -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 "I can't hear you -- I'm using the scrambler." -- users@sogo.nu https://inverse.ca/sogo/lists
