I've used APC for years--since I obtained several off lease years ago for
almost nothing. However, they've all slowly bit the dust--their charging
circuits giving out. Some research reveals that APC has always had a poor
design--the electronics are not insulated from the heat making component
failu
On Fri, May 10, 2013 at 10:20 AM, S. Dale Morrey wrote:
> I feel your pain. I made the mistake of following instructions for
> installing Asterisk on CentOS and trying them on an RHEL box awhile back.
> The version numbers were the same so I figured it would be safe. The
> directions had me add
I feel your pain. I made the mistake of following instructions for
installing Asterisk on CentOS and trying them on an RHEL box awhile back.
The version numbers were the same so I figured it would be safe. The
directions had me add a repo that "upgraded" some vital packages and
completely horked
I just got hit with my own sloppiness.
I have some Debian boxes where all the repos call out for "stable", and
others where all the repos call out for the release, "squeeze" or now
"wheezy". Those are fine.
This morning I found one box had almost all repos calling for
"squeeze", but one called fo
-s
When run by root:
smbpasswd [options] [username]
otherwise:
smbpasswd [options]
options:
-L local mode (must be first option)
-h print this usage message
-s use stdin for password prompt
-c smb.conf file Use the given pa
*Hey pluggers,*
* *
*Does anyone know of a way to get smbpasswd to take the actual password of
the user from stdin on the command line? I mean, for example, the unix
passwd program has the --stdin parameter, which lets you echo the password
and pipe it, i.e*
* *
*echo ThisIsMyPass | passwd dan
