Setting up a File Server 1st kapils 2 (stdid) 5761024 bytes 2nd eziodm 3 (stdid) 193536 bytes 3rd eziodm 3 addresses.txt 1024 bytes If we want to cancel a print job, we can use the lprm command. For example, to remove the job with ID 838 from the print queue, we can issue the following command: # lprm 838 Of course, if you try to cancel another user’s print job, and you don’t have permission to do so, then CUPS will prevent you from canceling it. For example, suppose the user eziodm tried to cancel job 2 in the list above: # lprm 2 lprm: You don’t own job ID 2! Note You can learn more about the CUPS printing system at http://..cups.org/. Setting up a File Server A file server is essentially a shared storage space. File servers are generally accessed across a network, and provide its users with a central location for file storage. File systems are also helpful when you need to share files with other users: you can simply place your file in a public directory on the file server, where other users can access it. Like FTP servers, there are essentially two fundamental components to a file server - the storage space itself and the mechanism for accessing it. Whether you’re working on a single machine at home, or as part of a large network in a major organization, you’ll be using a file system to store your files; what a file server adds to this is the notion that the file system is a shared one, accessible by (possibly) many users. There are a number of benefits to be gained by implementing a file server: It reduces administration cost. Instead of having important data stored on many individual PCs (all of which would require backing up), you can store all your important data in one place (on the file server). Then, only the file server needs regular backing up. It provides the opportunity to enforce a more controlled and focused security policy, because the security policy needs only to be applied to the file server. It enables you to provide a more stable and reliable storage solution. It enables you to implement your storage solution on high-spec machines that provide high levels of uptime. Moreover, implementation of RAID or of mirrored SCSI disks (which help ensure data reliability) is more feasible on a central file server than on many PCs. There’s also something to be gained in terms of cost of file storage (although this is less pertinent in these days of cheap storage). First, it makes best use of the available storage capacity by making it accessible to all users. Second, it provides a central repository from which common resources can be made available to all (eliminating the need for each user to store their own copy). Once you’ve got a file system, what makes it a file server is the mechanism that enables the file system to be shared. There is plenty of software around for this purpose - Samba, the Network File System (NFS), the Andrew file system (AFS), and Coda are all examples. Some of these are shipped as part of the Red Hat Linux 9 distribution, and we’re going to focus on one in particular - Samba. 291

Hint: If you are looking for very good and affordable webspace to host and run your java hosting application check Sandzak.com java web hosting provider