Sponsored Content
Operating Systems Solaris Network Path Not Found Error "Sunfire V100" Post 302099513 by louisd11 on Tuesday 12th of December 2006 01:41:44 PM
Old 12-12-2006
Network Path Not Found Error "Sunfire V100"

I recently got this new old server from a friend. I just installed a fresh version of Solaris 10 on it. I have put a static IP of 192.168.100.10 the server. Their is no subnetting scheme on the network. And I made the hostname "SunServ." And I also changed the folder "/etc/inet/hosts" because I kept getting this error

Quote:
"Dec 12 10:37:06 SunServ sendmail[278]: unable to qualify my own domain name (S
unServ) -- using short name
Dec 12 10:37:06 SunServ sendmail[278]: [ID 702911 mail.alert] unable to qualify
my own domain name (SunServ) -- using short name
Dec 12 10:37:06 SunServ sendmail[279]: unable to qualify my own domain name (Sun
Serv) -- using short name
Dec 12 10:37:06 SunServ sendmail[279]: [ID 702911 mail.alert] unable to qualify"
So I added the line Sunserv.ciscolab.com because we do have a domain name on our network. So I would like to access ther server and put files on it. But when I go on a windows machinen and type in "\\SunServ" in run I get the "Cannot find the network path" error. And the same error comes up when I type in the IP. SO how do I add the server to the network so I can add files and folders?
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Same ol "no acceptable cc found in $PATH" but I'm not clueless... just still a noob

Hey All, Let me start out w/ I have serched the forums and found this to be a typical problem. None of the threads have been able to help in my situation though. I know cc or gcc needs to be installed in ...bin]# (or lead the path of the app to wherever gcc is when compiling) so the app can... (4 Replies)
Discussion started by: SloYerRoll
4 Replies

2. Red Hat

"No Drives Found" error during Redhat Linux AS 4 installation

I'm trying to install Redhat LInux AS 4 update 4 on an IBM x306 series server. I keep getting following error: "No Drives Found. An error has occurred - no valid devices were found on which to create new file systems. Please check your hardware for the cause of this problem." I called IBM and... (2 Replies)
Discussion started by: pieman8080
2 Replies

3. Solaris

Solaris9 - qlogic HBAs - luxadm reports "Found path to 0 HBA ports"

Hi All, I'm actually trying to configure a Qlogic HBA on a solaris9 connecting in a Brocade SAN. I installed Solaris9 and now trying to look at FC devices.. bash-2.05# luxadm -e port Found path to 0 HBA ports bash-2.05# luxadm probe No Network Array enclosures found in /dev/es... (7 Replies)
Discussion started by: ilan
7 Replies

4. Shell Programming and Scripting

"find . -printf" without prepended "." path? Getting path to current working directory?

If I enter (simplified): find . -printf "%p\n" then all files in the output are prepended by a "." like ./local/share/test23.log How can achieve that a.) the leading "./" is omitted and/or b.) the full path to the current directory is inserted (enclosed by brackets and a blank)... (1 Reply)
Discussion started by: pstein
1 Replies

5. Red Hat

Could interrupt disabled cause "opreport error: No sample file found"?

Hi All I would like to profile my application with oprofile but I can't since no samples are collected. The kernel of my app is 2.6 on RED HAT Enterprise 5.3 (Tikanga) so OProfile is setup in timer interrupt mode # opcontrol --list-events Using timer interrupt. I... (0 Replies)
Discussion started by: manustone
0 Replies

6. Windows & DOS: Issues & Discussions

Avoiding DOS space related "path not found errors"

Well I have a lot of scripts that require dragging and dropping files in order to define Source files etc. However more often then not it is the case that the path to said file contains NUMEROUS spaces. I know one way to evade this problem is to encase the path in Quotes like this: ... (7 Replies)
Discussion started by: pasc
7 Replies

7. Shell Programming and Scripting

Bash script fails with "function: not found" error

Hello everyone, I am having problems figuring this out. This script below is supposed to create a list of file names with their "md5sum", in a file "lib-list.txt" When I run it "sh component-list.sh " I get this:component-list.sh: 4: component-list.sh: function: not found component-list.sh:... (4 Replies)
Discussion started by: joemb
4 Replies

8. Shell Programming and Scripting

find . -path "*_nobackup*" -prune -iname "*.PDF" \( ! -name "*_nobackup.*" \)

These three finds worked as expected: $ find . -iname "*.PDF" $ find . -iname "*.PDF" \( ! -name "*_nobackup.*" \) $ find . -path "*_nobackup*" -prune -iname "*.PDF" They all returned the match: ./folder/file.pdf :b: This find returned no matches: $ find . -path "*_nobackup*" -prune... (3 Replies)
Discussion started by: wolfv
3 Replies

9. Solaris

Changing "rx_queue_number" in "ixgbe.conf". Reboot or Network Restart?

Hi all, First post here. Working on Solaris 10, on a Sun t4-4, need to change RX queue depth(ethernet, not HBA) and was wondering if i could get by with just restarting the network or if i should just bounce the whole shebang. Apologies if i missed a similar thread. if there is one, please... (2 Replies)
Discussion started by: caspnx
2 Replies
DOVEADM-DIRECTOR(1)						      Dovecot						       DOVEADM-DIRECTOR(1)

NAME
doveadm-director - Manage Dovecot directors SYNOPSIS
doveadm [-Dv] director add [-a director_socket_path] host [vhost_count] doveadm [-Dv] director flush [-a director_socket_path] host|all doveadm [-Dv] director map [-a director_socket_path] [-f users_file] [host] doveadm [-Dv] director remove [-a director_socket_path] host doveadm [-Dv] director dump [-a director_socket_path] doveadm [-Dv] director status [-a director_socket_path] [user] DESCRIPTION
doveadm director can be used to manage and query the status of the list of backend mail servers where Dovecot proxy can redirect connec- tions to. OPTIONS
Global doveadm(1) options: -D Enables verbosity and debug messages. -v Enables verbosity, including progress counter. Command specific options: -a director_socket_path This option is used to specify an alternative socket. The option's argument is either an absolute path to a local UNIX domain socket, or a hostname and port (hostname:port), in order to connect a remote host via a TCP socket. By default doveadm(1) will use the socket /var/run/dovecot/director-admin. The socket may be located in another directory, when the default base_dir setting was overridden in /etc/dovecot/dovecot.conf. ARGUMENTS
host A mail server's hostname or IP address. user Is a user's login name. Depending on the configuration, a login name may be for example jane or john@example.com. vhost_count The number of "virtual hosts" to assign to this server. The higher the number is relative to other servers, the more connections it gets. The default is 100. COMMANDS
director add doveadm director add [-a director_socket_path] host [vhost_count] The command's tasks are: * assign a new mail server to the director. * increase/decrease the vhost_count of an already assigned server. director flush doveadm director flush [-a director_socket_path] host|all doveadm director flush drops all user associations either from the given host or all hosts. This command is intended mainly for testing purposes. director map doveadm director map [-a director_socket_path] [-f users_file] [host] The command doveadm director map is used to list current user -> host mappings. -f users_file Path to a file containing all user names (one per line). When given no userdb lookup will be performed. This may be a helpful alternative when for example the network connection to the LDAP or SQL server is slow. host Specify a server's IP address or hostname, to list only mappings of the given host. director remove doveadm director remove [-a director_socket_path] host Use this command in order to remove the given host from the director. director dump doveadm director dump [-a director_socket_path] Dump the current host configuration as doveadm commands. These commands can be easily run after a full director cluster restart to get back to the dumped state. director status doveadm director status [-a director_socket_path] [user] This command is used to show the current usage of all assigned mail servers. When a user name is given, this command shows which server the user is currently assigned to, where the user will be assigned after the current saved assignment gets removed and where the user would be assigned to if the whole proxy cluster was restarted fresh. FILES
/etc/dovecot/dovecot.conf Dovecot's main configuration file. /etc/dovecot/conf.d/10-director.conf Director specific settings. EXAMPLE
Add a director with vhost count 150 (or change existing one's vhost count to 150): doveadm -v director add x1357.imap.ha.example.net 150 2001:db8:543:6861:143::1357: OK Remove a director: doveadm director remove x1357.imap.ha.example.net Query the status of mail hosts in a director: doveadm director status mail server ip vhosts users 192.168.10.1 100 125 192.168.10.2 100 144 192.168.10.3 100 115 Query the status of a user's assignment: doveadm director status user@example.com Current: 192.168.10.1 (expires 2010-06-18 20:17:04) Hashed: 192.168.10.2 Initial config: 192.168.10.3 This means that the user is currently assigned to mail server on IP 192.168.10.1. After all of user's connections have logged out, the assignment will be removed (currently it looks like at 20:17:04, but that may be increased). After the assignment has expired, the user will next time be redirected to 192.168.10.2 (assuming no changes to director settings). If the entire Dovecot proxy cluster was restarted, so that all of the director configuration would revert back to its initial values, the user would be redirected to 192.168.10.3. REPORTING BUGS
Report bugs, including doveconf -n output, to the Dovecot Mailing List <dovecot@dovecot.org>. Information about reporting bugs is avail- able at: http://dovecot.org/bugreport.html SEE ALSO
doveadm(1) Dovecot v2.1 2011-05-11 DOVEADM-DIRECTOR(1)
All times are GMT -4. The time now is 01:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy