I manage a software development network, where the developers have a need to frequently (more than 10 times a day) change the system date. From my understanding, correct me if I'm wrong, only root (or a uid 0) can change the system date. I need a solution to allow users to change the date without having root access or equivalence. I have an idea that I could use a user executable script, to generate a file with their date change in it. Then using a second script looking for that file and reading it's contents continually (or close to it), execute the date change as root. Of course, I don't know how to do this, or if it's possible ... ?
Any ideas?

RH AS 2.1 (7.2)

Thanks in advance,
Matt

Cheers,
Tink

No manual entry for sudoers ....

Ummm...I'll probably get chewed out for this one but there is another way to do it besides using sudoers. What you can do is assign the date command to a different group(i.e. wheel). Then add all the people you want to have access to the date command to the wheel group. Then chmod wheel so that it has group executable permissions.

A quick and dirty way to get things done. Most people prefer sudoers. They say it is more secure although I don't know why.

Because wheel might have a bunch of permissions you're
not always aware of? ;}

Cheers,
Tink

P.S.: Rocks, stones, pebbles, ... :}

Not aware of? Isn't that your job as an admin to BE aware!

Tink,

I see an rpm available for sudo 1.6.6 (i386) - It is designated for RH 8.0 - should there be any problem with this on AS 2.1 (7.2 Kernel)?

Thanks,
Matt

Crashed,

How does changing the group get around the fact that the users can't change the date ... ? They already can execute the date command, they just cant change it. Am I missing something?

Thanks,
Matt

Hi Matt!

Sorry, I'm not too good when it comes to knowing
dependencies for other than my distro of choice (Slack)
... but if you go to rpmfind I'm almost certain
you'll find a package for your specific distro.

Cheers,
Tink

Because the wheel group is one idea that linux should have not taken from unix...although sudo does fix it. Actually, the problem with a wheel group is the idea that some people just have more rights over others WHILE sudo just gives you all the commands you need to work and no more.

Isn't giving certain users access to certain commands through sudo giving some people more rights then others?

I'm not going to beat this one into the ground because I really think this is a matter of preference.

if you let me, I'd like to clarify myself.
User1 may be sysadmin and need to do backups
User2 may be sysadmin and need to deal with users, root access- but for different reasons.

so a wheel group is created that allows user1 and user2 to do their job: BUT, this also means user2 has access to stuff only user1 needs, and vice versa.

Now, I understand that these example may be bad, but the idea remains the same. Sudo, on the other hand, will not make a "general, fit all" group, but instead give each user only the tools one needs, and no more.

the distinction may not seem big, but it does exist. often sudo is not the best solution - yet sometimes it is - but that's the power of *nix: use the right tool for the right job.