Reputation
622
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
3 13
Newest
 Yearling
Impact
~38k people reached

  • 0 posts edited
  • 0 helpful flags
  • 12 votes cast
Apr
12
answered Dovecot says: “Requested CRAM-MD5 scheme, but we have only CRYPT” yet CRAM-MD5 is available
Apr
12
comment postgrey configuration on Fedora Core 21 is very different, and not documented
Oh, OK, well, that's the default - not required! But I guess it's good to be explicit.
Apr
12
accepted postgrey configuration on Fedora Core 21 is very different, and not documented
Apr
12
comment postgrey configuration on Fedora Core 21 is very different, and not documented
OH CRAP! I hate it when I miss something so obvious like that! :( Oh well, live and learn!
Apr
12
comment postgrey configuration on Fedora Core 21 is very different, and not documented
Thanks, it works! SURE wish someone would update the documentation! Meanwhile, this Q/A will serve as a place others can find an answer until then! BTW, what does the 'permit' restriction do / refer to - I haven't seen that before?
Apr
12
comment call multiple Sql files in a single SQL file in Postgres
@Trip Trip, don't forget to give voretaq credit for his answer!
Apr
12
asked postgrey configuration on Fedora Core 21 is very different, and not documented
Apr
12
asked Dovecot says: “Requested CRAM-MD5 scheme, but we have only CRYPT” yet CRAM-MD5 is available
Sep
24
awarded  Autobiographer
Feb
5
awarded  Yearling
Oct
14
awarded  Talkative
Oct
14
accepted SETUID / SETGID on a binary executable stopped working following upgrade of Fedora Core
Oct
14
comment SETUID / SETGID on a binary executable stopped working following upgrade of Fedora Core
@MIfe I've been trying but there seems to be a bug; NOTHING happens. I either look at your link and it's blank, or I try the "automatically move this discussion to chat " and I see things but NO chance to type anything. It says I should log in to chat at the bottom BUT I AM LOGGED IN, clearly!
Oct
14
comment SETUID / SETGID on a binary executable stopped working following upgrade of Fedora Core
let us continue this discussion in chat
Oct
14
revised SETUID / SETGID on a binary executable stopped working following upgrade of Fedora Core
added the code in the C program that's having the error. Then added 'ls -l' output.
Oct
14
comment SETUID / SETGID on a binary executable stopped working following upgrade of Fedora Core
@MIfe Note the code that's running is now in the question section above. At first I said maybe it was the part that was calling Java, but no, it has trouble before that and I cited the code...
Oct
14
revised SETUID / SETGID on a binary executable stopped working following upgrade of Fedora Core
added the code in the C program that's having the error.
Oct
14
comment SETUID / SETGID on a binary executable stopped working following upgrade of Fedora Core
@MIfe Of course. It runs perfectly as the developer which is why I never noticed the problem over this long period of time!
Oct
14
comment SETUID / SETGID on a binary executable stopped working following upgrade of Fedora Core
@MIfe Sorry, I thought "program" was enough to make it clear it's NOT a script. It's actually a C program. I'm not sure just what the file access error would be, but it refuses the reads. Your guess about NFS was good: yes, NFS. ...The application was first written in 1997 or thereabouts and has worked all this time under the exact same scenario - the only thing that has changed is the OS version, even the build scripts and NFS mounting are the same!
Oct
14
asked SETUID / SETGID on a binary executable stopped working following upgrade of Fedora Core