05-20-2010
10 More Discussions You Might Find Interesting
1. Cybersecurity
restricted access...
Hi
I need to restrict users shell access to only $HOME under /home for each user. I don't want them getting out of their own directories. From what I understand chroot is something I could use, but I want to avoid this since it involves creating symbolic links to a number... (9 Replies)
Discussion started by: alwayslearningunix
9 Replies
2. UNIX for Dummies Questions & Answers
I need to create a user that only has access to 1 directory (e.g. /vol/mita/test). The user needs to be able to rsh into that directory to run a script. The user should not be able to navigate to any other directories above /vol/mita/test. Any help would be appreciated! (4 Replies)
Discussion started by: ngagne
4 Replies
3. UNIX for Dummies Questions & Answers
Hello,
I am a newborn baby to Unix and I was told that it was possible to have Microsoft Access databases on a Unix web server. I am using Perl to interface and query the Access database, which puts the information into the appropriate fields of a web page. Then updated information is submitted... (1 Reply)
Discussion started by: spiderling
1 Replies
4. Solaris
Hi All,
I'm on Solaris 8, I need to provide Read-only access to a user to 2 directories only.
Using rsh (restricted shell) as the user's login shell, I can restrict the user's access to a certain directory only, but how can I set in such a way that the user can access only the 2 directories... (4 Replies)
Discussion started by: max_min
4 Replies
5. UNIX for Advanced & Expert Users
I'm the admin in a shop in which my developers have and use the root account, all UNIX newbies.
I've been unable to convince management myself that this is an unacceptable practice.
I've looked in a couple books I have and can't find any chapters, discussions, etc that make the argument that... (2 Replies)
Discussion started by: keith.m
2 Replies
6. Solaris
We want to secure access to a server by restricting the number of users who can login to it. Our users are NIS users. Only few of them can telnet/ssh this server.
Do you have any idea on how to implement that?
thanks. (1 Reply)
Discussion started by: melanie_pfefer
1 Replies
7. UNIX for Advanced & Expert Users
Hi All,
I am facing a problem, regarding code security on a server.
We have configured a server which contains our code (ear present in jboss/server/xyz/deploy) in it, and need to bind the code to the server itself so that no one can take the code out of the. the problem is that the password of... (3 Replies)
Discussion started by: akshay61286
3 Replies
8. UNIX for Dummies Questions & Answers
Hello,
I am using MySecureShell to chroot all sftp accesses. The problem that I have is that my boss does not want root to be able to use sftp. Root should still be able to ssh. Any ideas? (2 Replies)
Discussion started by: mojoman
2 Replies
9. Solaris
Hey
Is there any way to differentiate if a user is logged directly into a UNIX functional account or if they have scsu'ed into the functional account?
Cheers
Paul (2 Replies)
Discussion started by: runnerpaul
2 Replies
10. Shell Programming and Scripting
i want to access database (sql script) within a unix script.
help me (2 Replies)
Discussion started by: chamaraa
2 Replies
LEARN ABOUT DEBIAN
databaseintro
databaseintro(1grass) Grass User's Manual databaseintro(1grass)
Database management in GRASS GIS
Attribute management in general
GRASS can be linked to one or many database management systems (DBMS). The db.* set of commands provides basic SQL support for attribute
management, while the v.db.* set of commands operates on the vector map (see Vector introduction).
Available drivers
Available drivers are listed in SQL support in GRASS GIS.
Notes:
The default DBF driver provides only very limited SQL support (as DBF is not an SQL DB) while the other DBMS backends (such as PostgreSQL,
MySQL etc) provide full SQL support since the SQL commands are sent directly to the DBMS.
DB connection management
The current database management settings are shown or modified with db.connect for current mapset. Available DBMI drivers are listed with
db.drivers. Some DBMI backends require a user/password for driver/database to be set with db.login. In order to test a driver, run
db.test.
Attribute data import and export
Attribute data can be imported with db.in.ogr from various formats and exported with db.out.ogr. To internally copy a a full table or
selectively parts of it, use db.copy.
Further conversion tools:
MDB Tools: Convert MS-Access data to SQL, DBF, etc.
Openoffice.org with SQL Databases
SQL commands
GRASS supports to main SQL operations, execution of an SQL statement (db.execute) and selection of data from a table (db.select). See the
SQL help page for examples.
Managing the default DBMI settings
Per default vector map attributes are stored in DBF table files. This default definition can be modified with db.connect. If an external
DBMS is used, db.login may be required.
Creating a database
Specific commands are explained on the individual driver pages (these pages are only available if driver was compiled in this installa-
tion):
DBF: see DBF page
SQLite: SQLite page
mySQL: meSQL pages
ODBC: ODBC page (connect to Oracle, etc.)
PostgreSQL: PostgreSQL and PostGIS page
Metadata
All columns for a given table are listed with db.columns. The command db.describe describes a table in detail. To list all available
tables for a given database, run db.tables.
Table maintenance
To drop a column from a selected attribute table, use db.dropcol. With db.droptable an attribute table can be deleted.
Database Schema
Currently schema support only works for PostgreSQL connections. Default schema can be set with db.connect. Note that the default schema
will be used by all db.* modules.
db.tables returns 'schema.table' if schemas are available in the database.
Migrating to a different database engine
To migrate a GRASS database table (or a GRASS vector map) to a different DBMI engine, the best solution is to create a new MAPSET, define
the DBMI settings accordingly with db.login. Then the table of interest can be copied over with db.copy from the original MAPSET. Like-
wise, a vector map including its table(s) are copied from the original MAPSET to the current MAPSET with g.copy.
See also
Introduction to GRASS vector map processing
Introduction to GRASS raster map processing
Main index - database index - full index
(C) 2008-2011 GRASS Development Team
GRASS 6.4.2 databaseintro(1grass)