On Wed, Aug 23, 2000 at 09:17:48PM -0500, Brent Harding wrote:
> If the script makes the file, say for example
> #!/bin/sh
> echo enter a username to create
> read $USER
> echo enter user's password
> read $PASSWORD
> echo $USER:$PASSWORD >>/etc/requested.users
> Then on the hour in cron have it
kmself@ix.netcom.com wrote:
> On Tue, Aug 22, 2000 at 09:37:05PM -0400, Mike Werner wrote:
> > Brent Harding wrote:
> > > How would cron do something such as, emailing a file once and awhile,
> > > make
> > > the file empty, and wait until the next run, but not mail anything if it's
> > > empt
If the script makes the file, say for example
#!/bin/sh
echo enter a username to create
read $USER
echo enter user's password
read $PASSWORD
echo $USER:$PASSWORD >>/etc/requested.users
Then on the hour in cron
have it mail to me the file with a subject of requested users, or piped the
file to that
On Wed, Aug 23, 2000 at 07:18:00PM -0500, Brent Harding wrote:
> >
> >> deleting would be something tricky, wouldn't want him deleting what I
> >> create.
> >
> >What are you deleting here? I'm confused.
> If he got access to userdel, he could delete users he shouldn't delete,
> just like, if he
>
>> deleting would be something tricky, wouldn't want him deleting what I
>> create.
>
>What are you deleting here? I'm confused.
If he got access to userdel, he could delete users he shouldn't delete,
just like, if he wants mail on his domain, he could add and delete his own
stuff only. I suppo
The problem is that email itself is insecure and unauthenticated, unless
you're using GPG or similar signing methods.
On Wed, Aug 23, 2000 at 11:17:57AM -0500, Brent Harding wrote:
> Actually, I think it's going to email me the users to add, I would do it
> with making a requestusers group, changi
On Wed, Aug 23, 2000 at 11:14:01AM -0500, Brent Harding wrote:
> Doesn't he have to have access to /etc/shadow though?
For what? If you provide sudo access to use the useradd or adduser
commands, the commands run *as root*. Updating of /etc/passwd and
/etc/shadow are transparent.
> The delay
On Tue, Aug 22, 2000 at 09:37:05PM -0400, Mike Werner wrote:
> Brent Harding wrote:
> > How would cron do something such as, emailing a file once and awhile,
> > make
> > the file empty, and wait until the next run, but not mail anything if it's
> > empty. I've never done much with emailing
On Tue, Aug 22, 2000 at 07:21:01PM -0500, Brent Harding wrote:
> How would cron do something such as, emailing a file once and awhile,
> make
> the file empty, and wait until the next run, but not mail anything if it's
> empty. I've never done much with emailing besides piping echo to mail
Brent Harding wrote:
> How would cron do something such as, emailing a file once and awhile,
> make
> the file empty, and wait until the next run, but not mail anything if it's
> empty. I've never done much with emailing besides piping echo to mail, but
> it's limited to one line.
What I
How would cron do something such as, emailing a file once and awhile, make
the file empty, and wait until the next run, but not mail anything if it's
empty. I've never done much with emailing besides piping echo to mail, but
it's limited to one line.
Supposing every hour I want it to email me all
11 matches
Mail list logo
