6 More Discussions You Might Find Interesting
1. AIX
Hello,
On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active.
We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED.
... (3 Replies)
Discussion started by: terrya
3 Replies
2. Filesystems, Disks and Memory
Hello,
On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active.
We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED.
... (1 Reply)
Discussion started by: terrya
1 Replies
3. Shell Programming and Scripting
Hi,
I just started working on a script. After my research, i found a command which can help me:
AIM: To build a script which starts the services (Services 1) on server 1 automatically whenever its down. And it has a dependency on other service (Service 2) on Server 2.
So my script has to... (4 Replies)
Discussion started by: draghun9
4 Replies
4. Red Hat
I had a doubt if any services need to be restarted if port no in /etc/services in an RHEL setup is changed. For eg, the port no of 443 for SSL may need to be changed.
I hope my query is clear whether any services need to be restarted if port no in /etc/services is changed.
Please revert with... (10 Replies)
Discussion started by: RHCE
10 Replies
5. Linux
Hi,
Am doing an enhancements related to monitoring a Linux disk I/O statistics.
The /proc/diskstats file is used to get the each disk I/O statistics. But, It returns the raw value.
How to calculate the Disk Queue Length and Disk Busy time from the raw values.
Guide me. (1 Reply)
Discussion started by: maruthu
1 Replies
6. Solaris
Previously , i remove the disk by
#vxdg -g testdg -k rmdisk testdg02
But i got error when i -k adddisk
bash-2.03# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none - - online invalid
c0t1d0s2 auto:none ... (1 Reply)
Discussion started by: waibabe
1 Replies
LEARN ABOUT OSX
cupsaddsmb
cupsaddsmb(8) Apple Inc. cupsaddsmb(8)
NAME
cupsaddsmb - export printers to samba for windows clients
SYNOPSIS
cupsaddsmb [ -H samba-server ] [ -U samba-user[%samba-password] ] [ -h cups-server[:port] ] [ -v ] -a
cupsaddsmb [ -H samba-server ] [ -U samba-user[%samba-password] ] [ -h cups-server[:port] ] [ -v ] printer [ ... printer ]
DESCRIPTION
cupsaddsmb exports printers to the SAMBA software (version 2.2.0 or higher) for use with Windows clients. Depending on the SAMBA configura-
tion, you may need to provide a password to export the printers. This program requires the Windows printer driver files described below.
OPTIONS
cupsaddsmb supports the following options:
-H samba-server
Specifies the SAMBA server which defaults to the CUPS server.
-U samba-user[%samba-password]
Specifies the SAMBA print admin username which defaults to your current username. If the username contains a percent (%) character,
then the text following the percent is treated as the SAMBA password to use.
-a
Exports all known printers. Otherwise only the named printers are exported.
-h cups-server[:port]
Specifies a different CUPS server to use.
-v
Specifies that verbose information should be shown. This is useful for debugging SAMBA configuration problems.
SAMBA CONFIGURATION
cupsaddsmb uses the new RPC-based printing support in SAMBA 2.2.x to provide printer drivers and PPD files to Windows client machines. In
order to use this functionality, you must first configure the SAMBA smb.conf(5) file to support printing through CUPS and provide a printer
driver download share, as follows:
[global]
load printers = yes
printing = cups
printcap name = cups
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
public = yes
guest ok = yes
writable = no
printable = yes
[print$]
comment = Printer Drivers
path = /etc/samba/drivers
browseable = yes
guest ok = no
read only = yes
write list = root
This configuration assumes a FHS-compliant installation of SAMBA; adjust the [printers] and [print$] share paths accordingly on your system
as needed.
MICROSOFT POSTSCRIPT DRIVERS FOR WINDOWS
The base driver for Windows 2000 and higher is the Microsoft PostScript driver, which is available on any system running Windows 2000 or
higher in the %WINDIR%SYSTEM32SPOOLDRIVERSW32X863 folder for 32-bit drivers and %WINDIR%SYSTEM32SPOOLDRIVERSX643 folder for
64-bit drivers.
However, currently only Windows 2000 and higher is supported by the Microsoft driver, so you will also need to get the Adobe driver to sup-
port Windows 95, 98, and Me clients. The Adobe and Microsoft drivers for Windows 2000 are identical.
Once you have extracted the driver files, copy the 32-bit drivers to the /usr/share/cups/drivers directory and the 64-bit drivers to the
/usr/share/cups/drivers/x64 directory exactly as named below:
[Windows 2000 and higher]
ps5ui.dll
pscript.hlp
pscript.ntf
pscript5.dll
Note: Unlike Windows, case is significant - make sure that you use the lowercase filenames shown above, otherwise cupsaddsmb will fail to
export the drivers.
ADOBE POSTSCRIPT DRIVERS FOR WINDOWS 95, 98, AND ME
cupsaddsmb can use the Adobe PostScript printer driver for Windows 95, 98, and ME, which are available for download from the Adobe web site
(http://www.adobe.com).
The Adobe driver does not support the page-label, job-billing, or job-hold-until options.
Once you have installed the driver on a Windows system, copy the following files to the /usr/share/cups/drivers directory exactly as named
below:
[Windows 95, 98, and Me]
ADFONTS.MFM
ADOBEPS4.DRV
ADOBEPS4.HLP
ICONLIB.DLL
PSMON.DLL
Note: Unlike Windows, case is significant - make sure that you use the UPPERCASE filenames shown above, otherwise cupsaddsmb will fail to
export the drivers.
KNOWN ISSUES
Getting the full set of Windows driver files should be easier.
SEE ALSO
smbd(8), smb.conf(5), http://localhost:631/help
COPYRIGHT
Copyright 2007-2013 by Apple Inc.
8 July 2013 CUPS cupsaddsmb(8)