I'm running Fedora Core 3 on several Dell SX280s. They are single use machines, running a software suite that receives and prints documents.

That part works fine.

On similar RHEL 3 machines, I've edited sudoers to allow non-privileged accounts to restart this software using a simple 3 line script (essentially stop the software, then start 2 separate daemons, all by pointing to executables that are specifically written for these tasks in the /usr/bin directory.) This works fine on RHEL 3.

In Fedora, I get the following error:
sesh: Error execing /usr/scripts/urestart: Exec format error

where /usr/scripts/urestart is the name of my 3 line script.

I've checked sudoers and can't find any errors. I've checked the script and can't find any errors. I can run the script as root with no problems.

I've checked permissions on the script and directory, and they're fine.

I can't find any information on the web on what that sesh: error means.

Any ideas?

fiservguy

Just browsing the "0 reply" threads and saw yours. Since it has been there a while, let me give you a (off-the-wall) suggestion:

I suspect that sesh is the SELinux version of bash, and that you've got SELinux enabled. root is probably in the seusers (see the command) as (perhaps) the only user permitted to change sedoers.

All that being said, I'm really just guessing, and I've never seen the sesh: Error message.

1 members found this post helpful.

(I got sidetracked on other issues, and just came back to this problem)

Your post was more helpful than you may have thought, PTrenholme. The ultimate problem was sloppy script writing on my part.

I didn't have a shell declaration at the beginning of my script. The script was being called by /usr/bin/sesh, and it apparently doesn't understand the simple bash commands I had entered. Adding the shell declaration (#!/bin/bash) solved the problem.

One more error identified and documented in my own little world, several hundred thousand to go...

Thanks for the feedback,
fiservguy

1 members found this post helpful.

I wrote a custom script and just started noticing these errors

sesh: Error execing ./getlastlog.sh: Exec format error

and this is what was causing the issue...

[onhodgdm@myserver 040910]$ cat getlastlog.sh
# Written by %%%%%%% - UNIX Admin
#!/bin/bash

and changed it to
[onhodgdm@myserver 040910]$ cat getlastlog.sh
#!/bin/bash
# Written by %%%%%%% - UNIX Admin

## Problem solved

1 members found this post helpful.

Same problem here and this tip really helped me! Thank you very much.