Sponsored Content
Full Discussion: Best practices
Operating Systems Solaris Best practices Post 302760711 by Corona688 on Thursday 24th of January 2013 12:44:15 PM
Old 01-24-2013
That's actually a few questions.

The mountpoint itself, before its mounted, what permissions should it have? Probably root, and read-only to everything else. You don't want the mountpoint to be used when not mounted by accident, that could fill up your root filesystem.

When it's mounted, what permissions should it have? Well, a mountpoint is in effect just a folder like any other. It may have to have certain permissions; if you put a mountpoint on /var/cache/squid, it ought to belong to user squid, group squid, and be writable by squid, or it won't be a whole lot of use.

Given that in some ways it's easier to rearrange filesystems than files -- you can plant them literally wherever you want -- it may be best to mould filesystems to the layout you want rather than vice versa.

Last edited by Corona688; 01-24-2013 at 01:49 PM..
This User Gave Thanks to Corona688 For This Post:
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Scripting Best Practices

Hi - I am new to this and was wondering if some of you can help me out. I am just starting to write scripts and need some guidelines on creating scripts. I'm calling them "Best Practices"...what should I do and not do when creating scripts. All I know so far is that I should avoid putting... (5 Replies)
Discussion started by: toddjameslane
5 Replies

2. Shell Programming and Scripting

Korn Shell Best Practices

I am new to ksh scripts (still reading manuals). I need to write an application that reads a multi-line parameter file, builds sql on-the-fly, runs plsql and saves the output in a specific format for further processing. I am looking for anything on Best Practices for building such an... (1 Reply)
Discussion started by: mtravis
1 Replies

3. UNIX for Advanced & Expert Users

emergency shutdown best practices.

Has anyone implemented or have suggestions on how to shutdown many remote unix/linux servers from a single script initiated from 1 server? I need this to execute in parallel as time is not on my side. Our ups is sadly underrated and will die in approximately 15 minutes. (There is not... (10 Replies)
Discussion started by: jsw371
10 Replies

4. UNIX for Advanced & Expert Users

Best practices with AIX system users?

All, Preliminaries: AIX 5.2 Tivoli Maestro 6.1 (9.2) I am auditing an older AIX system. As it stands, I can login remotely to the system using the Maestro application's user account. This is BAD. The administrator claims that he cannot disable the remote login, because it will... (1 Reply)
Discussion started by: Thatto
1 Replies

5. UNIX for Dummies Questions & Answers

Best practices for Source control

Hi all, i am trying to incorporate source control management in my project. We have about 50 - 60 shell scripts on 3 different machines dev, stag and production, but there is no source control. All the files have to be located at specific locations on each machine for it to work I want to... (4 Replies)
Discussion started by: chvs2000
4 Replies

6. Shell Programming and Scripting

Global Script Best Practices

Hey there. I am a relative rookie when it comes to Linux/Unix Administration and have been learning to adapt my meager coding skill to working with shell scripts in the 'nix realms. I have done some exhausting searches for and found plenty of information on making scripts globally available but... (2 Replies)
Discussion started by: Tenuous
2 Replies

7. Linux

Virtualization best practices

Hello admins and gurus I have a controversial topic: now we are investing in a new Linux OS that will hold our Sybase database. The server will virtualized on a VMware server hosted on SAN storage. Now the question is, when we install the database engine is it better - in terms of performance -... (1 Reply)
Discussion started by: abohmeed
1 Replies
basic_pam_auth(8)					      System Manager's Manual						 basic_pam_auth(8)

NAME
basic_pam_auth - Squid PAM Basic authentication helper SYNOPSIS
basic_pam_auth [-n service name TTL ] [-o] [-1] DESCRIPTION
basic_pam_auth allows Squid to connect to a mostly any available PAM database to validate the user name and password of Basic HTTP authen- tication. OPTIONS
-s service-name Specifies the PAM service name Squid uses, defaults to squid -t TTL Enables persistent PAM connections where the connection to the PAM database is kept open and reused for new logins. The TTL specifies how long the connection will be kept open (in seconds). Default is to not keep PAM connections open. Please note that the use of persistent PAM connections is slightly outside the PAM specification and may not work with all PAM configura- tions. -o Do not perform the PAM account management group (account expiration etc) CONFIGURATION
The program needs a PAM service to be configured in /etc/pam.conf or /etc/pam.d/squid The default service name is squid , and the program makes use of the auth and account management groups to verify the password and the accounts validity. For details on how to configure PAM services, see the PAM documentation for your system. This manual does not cover PAM configuration details. NOTES
When used for authenticating to local UNIX shadow password databases the program must be running as root or else it won't have sufficient permissions to access the user password database. Such use of this program is not recommended, but if you absolutely need to then make the program setuid root chown root basic_pam_auth chmod u+s basic_pam_auth Please note that in such configurations it is also strongly recommended that the program is moved into a directory where normal users can- not access it, as this mode of operation will allow any local user to brute-force other users passwords. Also note the program has not been fully audited and the author cannot be held responsible for any security issues due to such installations. AUTHOR
This program and documentation was written by Henrik Nordstrom <hno@squid-cache.org> COPYRIGHT
Squid basic_pam_auth and this manual is Copyright 1999,2002,2003 Henrik Nordstrom <hno@squid-cache.org> Distributed under the GNU General Public License (GNU GPL) version 2 or later (GPLv2+). QUESTIONS
Questions on the usage of this program can be sent to the Squid Users mailing list <squid-users@squid-cache.org> REPORTING BUGS
Bug reports need to be made in English. See http://wiki.squid-cache.org/SquidFaq/BugReporting for details of what you need to include with your bug report. Report bugs or bug fixes using http://bugs.squid-cache.org/ Report serious security bugs to Squid Bugs <squid-bugs@squid-cache.org> Report ideas for new improvements to the Squid Developers mailing list <squid-dev@squid-cache.org> SEE ALSO
squid(8), pam(3), pam.conf(5), chown(1), chmod(1), GPL(7), PAM Systems Administrator Guide The Squid FAQ wiki http://wiki.squid-cache.org/SquidFaq The Squid Configuration Manual http://www.squid-cache.org/Doc/config/ 5 Sep 2003 basic_pam_auth(8)
All times are GMT -4. The time now is 04:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy