Sponsored Content
Full Discussion: Very Interesting Problem
Operating Systems Solaris Very Interesting Problem Post 302352501 by ilikecows on Friday 11th of September 2009 01:41:14 PM
Old 09-11-2009
Assuming users dont need to update it you have three options:

A. install IIS or apache on the windows box, share the file, and reference your link to it
B. host the file off your solaris server and reference your link to it
C. share the directory with microsoft file sharing, mount the share on solaris under your apache directory, and reference your link to it

Option B would be by far the easiest.

If your users need to modify this file I would recommend hosting off your Solaris box and create two links on your site. One for Windows users and another for unix users. Share the file out via NFS/SAMBA, and reference each link with the appropriate style. You will probably have to use automounting on your unix machines.

UNIX: /path/to/file
Windows: \\server\path\to\file

Last edited by ilikecows; 09-11-2009 at 02:46 PM..
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

An interesting problem

hi!, here is an interesting problem ..... I ftp a file named " my first file.doc" from windows to my HP workstation. Ftp is succesful. The file appears with the same name in my home directory.. But now how do I open this file?? while using Vi or More or other editor, they take only the... (5 Replies)
Discussion started by: jyotipg
5 Replies

2. UNIX for Advanced & Expert Users

interesting problem

After a server reboot for regular mainatanance we face the following situation: 1/ user accounts with ksh can't start the korn shell 2/ korn shell scripts do work however, if executed from bash 3/ normal users with bash can't run ksh 4/ root can run ksh 5/ if I switch the default shell to... (3 Replies)
Discussion started by: rein
3 Replies

3. SCO

I have an interesting problem and need advice

We have an inhouse built application which handles our AR function. We'd like to email statements out of the application directly. My question is this is there a good, solid, command line driven, scriptable Mail Transport Agent that would allow us to send a semi unique email (with a statement and... (1 Reply)
Discussion started by: Maldain
1 Replies

4. Shell Programming and Scripting

Interesting problem

Hello, So I'm utilizing the bash brace expansion feature to checkout multiple folders from cvs with ease, while excluding certain subfolders within. So I do a command like this: cvs co trunk/{mod_a,mod_b,mod_c} \!trunk/{mod_a,mod_b,mod_c}/web to checkout modules trunk/mod_a , trunk/mod_b ,... (1 Reply)
Discussion started by: neked
1 Replies

5. Shell Programming and Scripting

interesting problem

Hi, I am new in this forum and I am glad to be a part of it. I have a problem that has two parts: 1/ extract just the timestamp from a filename: for example, I have a file called 'sales20080226144525.txt' and I want to extract just the '20080226144525' part out of it. 2/ Now, take that... (5 Replies)
Discussion started by: ChicagoBlues
5 Replies

6. Programming

Interesting Problem About Incrementing ++

Here is my code: int startingPort = 200; string tempPort; stringstream out; out<<startingPort; tempPort = out.str(); //tempPort carries startingPort in string format //convert tempPort to *char - currentPort going to be passed into getaddrinfo() char currentPort;... (10 Replies)
Discussion started by: f.ben.isaac
10 Replies

7. AIX

Interesting Problem! 2 VIOs, One is problematic, assigning disks and resources from the other only

Hi, The scenario is like this: 1.We needed to assign two hdisks to an LPAR 2.SAN team gives us two ldevs 3.One of our VIO is hanging on cfgmgr operation 4. We ran cfgmgr on the smooth VIO. Got the disks and assigned the disks from there to the LPAR.(By passed the other VIO as in didnt run... (11 Replies)
Discussion started by: aixromeo
11 Replies

8. Solaris

Interesting Disk Error Problem

Hi Folks, Have an interesting problem here, have just upgraded some machines (Test and Development) to the latest and greatest as in. SunOS ss063a 5.10 Generic_147440-13 sun4u sparc SUNW,Sun-Fire-V440 However on all the systems we are seeing the same problems, during the boot there is a... (3 Replies)
Discussion started by: gull04
3 Replies

9. Shell Programming and Scripting

Interesting awk problem

Hello; I wish to manipulate the output from the following: ps axo %mem,pid,euser,cmd|sort -nr 14.4 3170 root /usr/sbin/snmpd -Lsd -Lf /dev/null -p /var/run/snmpd.pid -a 3.6 3635 root splunkd -p 8089 start 2.6 3383 root /usr/sbin/httpd 2.1 15496 apache /usr/sbin/httpd ... (5 Replies)
Discussion started by: delphys
5 Replies
link(1) 						      General Commands Manual							   link(1)

NAME
link, unlink - Creates an additional directory entry for an existing file SYNOPSIS
link file1 file2 unlink file STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: link: XCU5.0 unlink: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. DESCRIPTION
The link command performs the link() system call to create an additional directory entry for an existing file, file1. In effect, the underlying file then has two names, file1 and file2 (either of these arguments can be a pathname). The old and new entries share equal access rights to the underlying file. The unlink command performs the unlink() system call to remove a link to file created by link. The unlink command removes the directory entry specified by the file parameter and, if the entry is a hard link, decrements the link count of the file referenced by the link. You should be familiar with the link() and unlink() system calls before you use these commands. The link and unlink commands do not issue error messages when the associated system call is unsuccessful. NOTES
The link and unlink commands cannot be used to link and unlink directories. EXIT STATUS
The link and unlink commands both exit with the following: The link() or unlink() system call succeeded. Too few or too many arguments specified. The link() or unlink() system call failed. SEE ALSO
Commands: fsck(8), ln(1) Functions: link(2), unlink(2) link(1)
All times are GMT -4. The time now is 12:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy