You are not logged in.
Pages: 1
Hi to all!
I'm using remind (http://www.roaringpenguin.com/products/remind) as a (CLI) calendar program. To see my next events I just tip:
rem
Now, I noticed that the rem (or remind) process is not killed after the output is printed. I can use the shell again, but the rem program is somehow still running in background. As a consequence, after some rem runs the whole computer gets very slow and unusable.
I can obviously cast the command:
rem;killall rem
but it is not a good solution. Do you know if this behaviour is normal, due to some bad configuration, or a bug?
Offline
By default, remind stays running, since it is supposed to deal also with timed reminders - and the only way to do that is to keep running. There's a switch which disables this, namely -q. So I run remind as 'rem -q'.
Offline
Thank you. I coulld not find the right option in the man page, because it only says: "not to queue reminds" but does not mention the process itself.
Now I can safely put the command into my wmii status bar, where it gets filtered through some sed and shows me how many reminders I have.
Offline
Pages: 1