Sponsored Content
Full Discussion: Samba Woes
Operating Systems AIX Samba Woes Post 302999941 by splattty on Friday 30th of June 2017 09:23:01 AM
Old 06-30-2017
Hi Zaxxon

I'm afraid we need to be at 4.4 or later for compliance according to our Security Officer. Will have a bit more of a play and give in and talk to support if necessary, shame the quick install jobs aren't left alone as they always become FAR more complicated Smilie

Cheers
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

CDROM Woes

Have a Sun CDROM connected to a Ultra machine . Problem is it is not recognizing the drive being connected to it ... When i put the CD in the drive it accepts the CD and zooms initially then quitens out .. The devices drivers are also not created for it ... Any ideas anyone ... I am... (4 Replies)
Discussion started by: Jai
4 Replies

2. UNIX for Advanced & Expert Users

Interrupt level 14 woes

Hi there, My first post here. Currently, i have been experiencing this error quite frequently on a ultra5 com. Things i have done is changing a new hdd and mem modules but i still encounter this error. Some messages from the var/adm WARNING: uncorrectable error from pci0 (upa mid 0) during... (0 Replies)
Discussion started by: kerwen
0 Replies

3. Solaris

Remote CD woes

Good Day, I've remotely mounted a cdrom (no problems theere). The kicker is I can see the directories on the remote CD bout I can't see the files. What am I doing wrong? I'm logged in as root on both systems. All the permissions seem okay - what am I missing? Thanks (2 Replies)
Discussion started by: greg69
2 Replies

4. UNIX for Dummies Questions & Answers

Mksysb and Savevg woes

hi, i'm having a little trouble with an AIX 5.2 script that i have written and i was wondering if anyone could please offer me some advice on how to append a savevg backup to a mksysb tape, or more importantly where i'm going wrong? i've been trying to get this to work on and off for about a... (1 Reply)
Discussion started by: boredazfcuk
1 Replies

5. Solaris

pkgadd woes

Morning all, I am attempting to load a package from a Solaris 8 CDROM. This fails with the error : "pkgadd: ERROR: unable to access pkgmap file </cdrom/ .........../SUNWlibC/pkgmap> No changes were made to the system" Any help would be appreciated Andy (6 Replies)
Discussion started by: AndyD
6 Replies

6. AIX

IVM vs. HMC woes

I have a running VIO server that was managed via IVM. We made the (apparent) mistake of trying to connect a HMC server to it. Other than making a connection, no work has been done via HMC. We've since decided we don't want to use HMC and it's been powered off for a couple of weeks. However,... (1 Reply)
Discussion started by: cjs226
1 Replies

7. Solaris

SSH woes

version of solaris: SunOS 5.8 Generic-117350-39 sun4u sparc SUNW,Netra-240 version of SSH: OpenSSH_4.4p1, OpenSSL 0.9.8d 28 Sep 2006 Task: I need to have another Machine ssh into my machine, by either RSA authentication or username/pass authentication. History: In the begining my... (4 Replies)
Discussion started by: EWTGPAC
4 Replies

8. Solaris

Locale woes

Greetings Forumers! I've been fighting a locale problem on a v490 running Solaris 10 u4 (8/07). When I login to the system, I get several "locale" error messages: user1's password: Last login: Wed May 26 2010 09:14:13 -0400 from system1 You have mail. couldn't set locale correctly couldn't... (0 Replies)
Discussion started by: bluescreen
0 Replies

9. Solaris

samba issue: one samba share without password prompting and the others with.

Hi All, I've been trying to configure samba on Solaris 10 to allow me to have one share that is open and writable to all users and have the rest of my shares password protected by a generic account. If I set my security to user, my secured shares work just fine and prompt accordingly, but when... (0 Replies)
Discussion started by: ideal2545
0 Replies

10. Solaris

Jumpstart woes

Hey, I have been battling with jumpstart for the past few days. Interface nxge0 is set on a vlan: nxge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 0.0.0.0 netmask ff000000 ether 0:21:28:3c:a0:6 nxge998000:... (0 Replies)
Discussion started by: stantonnet
0 Replies
qterm(8B)								PBS								 qterm(8B)

NAME
qterm - terminate processing by a PBS batch server SYNOPSIS
qterm [-t type] [server...] DESCRIPTION
The qterm command terminates a PBS batch server. When a server receives a terminate command, the server will go into a terminating state. While in this state, the server will not allow new jobs to be started or enqueued. By default, qterm will request a "quick" shutdown of the PBS server. Other ways of shutting down the server (specified with the -t argument), and their impact on running jobs, are described below. The qterm command will not exit until the server has completed its shutdown procedure. In order to execute qterm, the user must have PBS Operation or Manager privilege. OPTIONS
-t type Specifies the type of shut down. The types are: immediate All running jobs are to immediately stop execution. If checkpoint is supported, running jobs that were submitted with "-c shutdown" are checkpointed, terminated, and requeued. If checkpoint is not supported or the job cannot be checkpointed, running jobs are requeued if the rerunable attribute is true. Otherwise, jobs are killed. Normally the server will not shutdown until there are no jobs in the running state. If the server is unable to contact the MOM of running job, the job is still listed as running. The server may be forced down by a second qterm -t immediate command. delay If checkpoint is supported, running jobs that were submitted with "-c shutdown" are checkpointed, terminated, and requeued. If a job cannot be checkpointed, but can be rerun, the job is terminated and requeued. Otherwise, running jobs are allowed to continue to run. Note, the operator or administrator may use the qrerun and qdel commands to remove run- ning jobs. quick This option is used when you wish that running jobs be left running when the server shuts down. The server will cleanly shutdown and can be restarted when desired. Upon restart of the server, jobs that continue to run are shown as running; jobs that terminated during the server's absence will be placed into the exiting state. OPERANDS
The server operand specifies which servers are to shutdown. If no servers are given, then the default server will be terminated. STANDARD ERROR
The qterm command will write a diagnostic message to standard error for each error occurrence. EXIT STATUS
Upon successful processing of all the operands presented to the qterm command, the exit status will be a value of zero. If the qterm command fails to process any operand, the command exits with a value greater than zero. SEE ALSO
pbs_server(8B), qmgr(1B), pbs_resources_aix4(7B), pbs_resources_irix5(7B), pbs_resources_sp2(7B), pbs_resources_sunos4(7B), and pbs_resources_unicos8(7B) Local qterm(8B)
All times are GMT -4. The time now is 07:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy