@Seth around? Know anything at all about sigaction?

Or possibly @Braiam?

@hichris123 mm?

@Braiam Would you happen to know why running this as root works, but running it as my own user fails with "Sigaction failed at number 65 (Operation not permitted)"?

@hichris123 for me it fails at invalid argument...

I think it would be more useful if you have a strace ./file so I can look at it

@Braiam what's that?

 strace /path/to/binary_that_is_failing

@Braiam Alright, running as my user vs running as root.

@hichris123 I don't have any idea from where the bdflush() function comes from but according to the man pages you need "CAP_SYS_ADMIN capability." which obviously your user don't have, btw, the function is depreciated

@Braiam Welp, I guess it's a bug on Chromium's part. This code comes from the chromium code... :/

try gdb ./sigaction (with the debug symbols) and then type run to check out

@hichris123 I figured as much, but Chrome is a mix of setuid's that might trick the kernel into allowing this, btw, did you read this? code.google.com/p/chromium/issues/detail?id=245680

@Braiam yeah, that's what the .c came from. And this is from running on 14.04, weird...

Any idea how to give myself "CAP_SYS_ADMIN" capability?

@hichris123 execcap 'cap_sys_admin=eip' binary

according to this kernel.org/pub/linux/libs/security/linux-privs/kernel-2.2/…

@Braiam Looks like you have to already have that capability... and for some reason it's giving command not found. :(

Maybe it's something different in newer versions?

@hichris123 about the code question, you can ask why bdflush() bails out in UL or SO, adding capabilities to a process you can ask in UL

hmm, okay.

What are you trying to do Chris?

@Seth run my own built version of chromium. And sigaction isn't liking me.

Apparently the process is not allowed to use bdflush, since it doesn't have CAP_SYS_ADMIN privs?

From the manpages (emphasis mine):

> bdflush starts, flushes, or tunes the buffer-dirty-flush daemon. Only the super-user may call bdflush.

aha.

Gah, now I guess I have to get it to work with sudo.

@Seth If I run it with sudo, then it gives an error that the D-BUS daemon isn't running.

@Seth what version is that?

at the bottom should appear the date of the man page

> bdflush() starts, flushes, or tunes the buffer-dirty-flush daemon. Only a privileged process (one with the CAP_SYS_ADMIN capability) may call bdflush().

^ mine says that

are you reading man 2 bdflush, right?

This is the one I saw first: linux.about.com/library/cmd/blcmdl2_bdflush.htm

My local one says the same as yours though.

@hichris123 no idea honestly.

[ SmokeDetector ] SmokeDetector started at rev b7cc7a2 (@Undo)

[ SmokeDetector ] All-caps title: GOAL PROGRAMMING EXCERSICE on math.stackexchange.com

[ SmokeDetector ] SmokeDetector started at rev b7cc7a2 (@Undo)

@Andy You could try to fetch new messages using WebSockets instead of HTTP (by using watch_socket instead of watch in ChatExchange).

That being said, WebSockets break more frequently than the HTTP method. I noticed that for my bot in Shadow's Den.

[ SmokeDetector ] SmokeDetector started at rev b7cc7a2 (@Undo)

[ SmokeDetector ] All-caps title: CAULADORA COM VALORES PROGRAMADOS on stackoverflow.com

@ProgramFOX Do you have a method of restarting after it breaks?

@Andy Try stackoverflow.com/questions/1611256/…

I'm not sure though what should be inside the try block, as I don't use that method, because I don't want to store the password in a file.

You could ask @Undo how he wrote his auto-restarter; he has a script that re-runs SmokeDetector when it breaks.

@ProgramFOX @Andy github.com/Charcoal-SE/SmokeDetector/blob/master/nocrash.sh

@Undo Thanks!

:D

!!/alive?

@ProgramFOX Of course

@Undo I noticed that Smokey keeps running if an error occurs in a different thread. Does your auto-restart script still restart Smokey if an error occurs in a different thread?

I created a new SmokeDetector revision by the way. If a privileged user replies delete to a message of SmokeDetector, it deletes that message.

[ SmokeDetector ] All-caps title: DO I NEED TRANSIT VISA FOR LONDON UK on travel.stackexchange.com

[ SmokeDetector ] Bad keyword detected, Phone number detected: vashikaran specialist in mumbai+91-9950211818 delhi on english.stackexchange.com

[ SmokeDetector ] All-caps title: IOS 8 UPDATE ISSUES on apple.stackexchange.com

[ SmokeDetector ] SmokeDetector started at rev 086e65b (@Undo)

@SmokeDetector delete

ah I see it.

@SmokeDetector delete

@hichris123 Of course

Oh, not like that?

no

@SmokeDetector !!/delete

oops

@SmokeDetector delete

ah

@ProgramFOX Looks like Manish's wrapper doesn't expose message.content_source, this is what gets logged when a message comes in:

MessagePosted({u'user_id': 73046, u'event_type': 1, u'room_name': u'Charcoal HQ', u'message_id': 17784756, u'content': u'@SmokeDetector delete', u'parent_id': 17784715, u'room_id': 11540, u'show_parent': True, u'time_stamp': 1411332922, u'user_name': u'Undo', u'id': 33000462}, <ChatExchange.chatexchange.client.Client object at 0x7f2b322c7050>)

(or maybe I don't know what I'm talking about, I haven't tested it very much)