Tickets :: [#10638] email from cron /usr/bin/horde-alarms

6.0.0-alpha14

7/2/25

Summary	email from cron /usr/bin/horde-alarms
Queue	Gollem
Queue Version	2.0-RC1
Type	Bug
State	Resolved
Priority	2. Medium
Owners	jan (at) horde (dot) org
Requester	gimili17 (at) gmail (dot) com
Created	10/12/2011 (5012 days ago)
Due
Updated	10/17/2011 (5007 days ago)
Assigned	10/12/2011 (5012 days ago)
Resolved	10/17/2011 (5007 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

10/17/2011 04:27:05 PM	Jan Schneider	Assigned to Jan Schneider State ⇒ Resolved

10/17/2011 04:26:58 PM	Git Commit	Comment #8	Reply to this comment
Changes have been made in Git for this ticket: Use proc_open() instead of exec() to catch stderr (~~Bug #10638~~). 2 files changed, 14 insertions(+), 2 deletions(-) http://git.horde.org/horde-git/-/commit/e87e93344aa68eced5df1360e9d6830b1ae6a827

10/12/2011 04:46:43 PM	Michael Slusarz	Comment #7	Reply to this comment
The Smb backend works by calling exec() on $backends['smb']['smbclient']. This should catch all output. I'm almost positive exec() doesn't capture stderr by default. IIRC, using exec() you need to either pipe stderr into /dev/null (or equivalent) or, for a more cross-platform solution, use proc_open() instead.

10/12/2011 04:39:45 PM	Jan Schneider	Comment #6	Reply to this comment
No. What I was saying is, that this should not happen, and I have no idea why it does or how to prevent it.

10/12/2011 04:20:35 PM	gimili17 (at) gmail (dot) com	Comment #5	Reply to this comment
The Smb backend works by calling exec() on $backends['smb']['smbclient']. This should catch all output. Can you dumb this down for me? Do you want me to change $backends['smb'] = to $backends['smb']['smbclient'] =

10/12/2011 02:48:09 PM	Jan Schneider	Comment #4	Reply to this comment
The Smb backend works by calling exec() on $backends['smb']['smbclient']. This should catch all output.

10/12/2011 02:37:08 PM	gimili17 (at) gmail (dot) com	Comment #3	Reply to this comment
And do you see this output too (on the webpage or in the logs) when using Gollem through the browser? I did not see anything in the browser and I could not see anything obvious in the log.

10/12/2011 02:11:18 PM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
And do you see this output too (on the webpage or in the logs) when using Gollem through the browser?

10/12/2011 11:48:48 AM	gimili17 (at) gmail (dot) com	Comment #1 Milestone ⇒ State ⇒ Unconfirmed Patch ⇒ No Queue ⇒ Gollem Summary ⇒ email from cron /usr/bin/horde-alarms Type ⇒ Bug Priority ⇒ 2. Medium	Reply to this comment
As soon and I install gollem I start getting emails every five minutes as follows: subject: Cron <root@server> /usr/bin/horde-alarms body: Domain=[myorganization] OS=[Unix] Server=[Samba 3.5.6] Domain=[myorganization] OS=[Unix] Server=[Samba 3.5.6] If I remove gollem the emails stop. I am using the smb driver in gollem.