Re^3: How to make sure that non-Perl programs will respect Perl's file locking?

Hmmm... So you *do* are changing the smbpasswd in your CGI script... I wouldn't recommend it...

The fact that Slackware doesn't support PAM is really a suprise to me... I've been using PAM for a long time and actually can't think how it can't be in Slackware...

Anyway... If you were using PAM, you could place a pam module that reflects the changes on the user password to the smbpasswd file. (I know such module exists, just don't remeber its name).

"Fixing" your Slackware to include PAM is possibly a good idea, or else you'll have to stick with this insecure approuch of changing this files directly...

daniel

Comment on Re^3: How to make sure that non-Perl programs will respect Perl's file locking?

Replies are listed 'Best First'.
Re^4: How to make sure that non-Perl programs will respect Perl's file locking? by lRem (Scribe) on Jan 11, 2006 at 21:12 UTC
It never was in Slackware, as well as it never was in OpenBSD. And in the latter, it probably never will, with no way to install it by yourself. As for me, this is enough to don't use PAM in my programs. Unless I would think it's worth implementing both PAM and PAMless versions (which I never did). On the other hand, PAM can be added to Slackware and all other Linux distros. So when you're not thinking about OpenBSD (other UN*Xes have PAM support), you can just add PAM to the dependencies list. -- Someday, people who know how to use computers will rule over those who don't. And there will be a special name for them: secretaries. -Dilbert quote	[reply]

Replies are listed 'Best First'.

Re^4: How to make sure that non-Perl programs will respect Perl's file locking?
by lRem (Scribe) on Jan 11, 2006 at 21:12 UTC

--
Someday, people who know how to use computers will rule over those who don't. And there will be a special name for them: secretaries. -Dilbert quote

[reply]