Sponsored Content
Full Discussion: Final Year Project
Operating Systems Linux Final Year Project Post 302857047 by M1S0 on Wednesday 25th of September 2013 10:53:44 AM
Old 09-25-2013
Helloo

Thanks for your replies were very useful.

Sorry for not giving more specification.

The scope of the project will be for me to build a good knowledge based in linux system administration and learn how to design a network.

For example

I have an organization based in four different countries.

USA - New York
Australia - Sydney
Europe - UK
Russia - Moscow

Each office has employees (let's say 20 or 30) and need to have account users, email boxes(mail server),sharing files (file server),print server etc.

Can access through VPN connection to the network if they are working from home or anywhere else.Users are free to use Mac OS/ Windows / Linux as OS on their pcs.

Not sure if that helped or is too much for an 8 month project.

If is too much I would like to do that as my home network so I will minimise it a lot.

I would like to learn and become linux administrator step by step after I graduate, so anything good I could start with to build a strong knowledge and base for the future will be appreciate

Thanks for you replies
M1S0
 

We Also Found This Discussion For You

1. What is on Your Mind?

Final Year Project dilemma

Hello everyone. Need some final year project ideas - what is actual/feasible and beneficial experience-wise? Preferably something related to Networking / Linux / UNIX / Security . Appreciate any help/idea. E.K. (0 Replies)
Discussion started by: reminiscent
0 Replies
REXECD(8)						    BSD System Manager's Manual 						 REXECD(8)

NAME
rexecd -- remote execution server SYNOPSIS
rexecd [ -D ] OPTIONS
Rexec accepts one option: -D Disable reverse DNS look up and in the log will be used client IP addresses. DESCRIPTION
Rexecd is the server for the rexec(3) routine. The server provides remote execution facilities with authentication based on user names and passwords. Rexecd listens for service requests at the port indicated in the ``exec'' service specification; see services(5). When a service request is received the following protocol is initiated: 1. The server reads characters from the socket up to a NUL ('') byte. The resultant string is interpreted as an ASCII number, base 10. 2. If the number received in step 1 is non-zero, it is interpreted as the port number of a secondary stream to be used for the stderr. A second connection will be created to the specified port on the client's machine after receiving and authenticating the user, password, and command from the client. 3. A NUL terminated user name of at most 16 characters is retrieved on the initial socket. 4. A NUL terminated, unencrypted password of at most 16 characters is retrieved on the initial socket. 5. A NUL terminated command to be passed to a shell is retrieved on the initial socket. The length of the command is limited by the upper bound on the size of the system's argument list. 6. Rexecd then validates the user as is done at login time and, if the authentication was successful, changes to the user's home directory, and establishes the user and group protections of the user. If any of these steps fail the connection is aborted with a diagnostic mes- sage returned. 7. A NUL byte is returned on the initial socket and the command line is passed to the normal login shell of the user. The shell inherits the network connections established by rexecd. DIAGNOSTICS
Except for the last one listed below, all diagnostic messages are returned on the initial socket, after which any network connections are closed. An error is indicated by a leading byte with a value of 1 (0 is returned in step 7 above upon successful completion of all the steps prior to the command execution). username too long The name is longer than 16 characters. password too long The password is longer than 16 characters. command too long The command line passed exceeds the size of the argument list (as configured into the system). Login incorrect. No password file entry for the user name existed or the wrong password was supplied. No remote directory. The chdir command to the home directory failed. Try again. A fork by the server failed. <shellname>: ... The user's login shell could not be started. This message is returned on the connection associated with the stderr, and is not pre- ceded by a flag byte. SEE ALSO
rexec(3) BUGS
A facility to allow all data and password exchanges to be encrypted should be present. HISTORY
The rexecd command appeared in 4.2BSD. Linux NetKit (0.17) March 16, 1991 Linux NetKit (0.17)
All times are GMT -4. The time now is 10:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy