08-07-2017
If 4.1.7 contains a fix for the problem (which is what the release note says) that you are worried about, then unless you have other concerns and/or samba has other vulnerabilities, I suggest that if it's not broken, Don't try and fix it. You don't know whether an upgrade will break something else.
Look and see what patches have been issued for 4.1.7 and why. Apply the patches for anything that you're concerned about.
Upgrade to a newer version if that offers new functionality that you could use.
Last edited by hicksd8; 08-07-2017 at 08:46 AM..
10 More Discussions You Might Find Interesting
1. Solaris
Hi ,
I need to collect all information about the patches in my server , I want to know what is the required patch and how to apply it.
Regards (2 Replies)
Discussion started by: ArabOracle.com
2 Replies
2. Solaris
Hello experts.
How can i see kernel patch version? what are advantages applying that patch?
Thanx in advance (5 Replies)
Discussion started by: younus_syed
5 Replies
3. Red Hat
Hi,
Is there any command to know the patch version?Suppose i installed RTlinux patch in rethat linux.How can i know the patch version installed?Any helps appreciated.
Thanks,
Sathi. (2 Replies)
Discussion started by: sathiyaraj V
2 Replies
4. Solaris
Hi,
As in the solaris material i know that the patch is added through the command "patchadd <patch no.>".
But i need to know, what are all the steps we have to follow while applying a patch in a production server. My friend says that we have to detach mirror before applying patch and not... (6 Replies)
Discussion started by: Sesha
6 Replies
5. Solaris
Hi there,
Apologies if this question has been asked and answered already but I've not been able to find the thread.
Question: Is it possible to apply the Solaris 10 Recommended Patch Cluster to a whole root (non-global) zone locally? I.E. apply the patch cluster from the non-global in... (3 Replies)
Discussion started by: nm146332
3 Replies
6. Solaris
I'm trying to setup our jumpstart server to automatically apply the latest patch cluster during installs, but I'm running into an issue. Every time Jumpstart runs it has this error. Obviously it's processing the patch_order file, so I'm not sure what I'm missing.
... (0 Replies)
Discussion started by: christr
0 Replies
7. HP-UX
Hi guys,
Question:
I downloaded a security update for samba:
samba-3.0.7-CAN-2004-0882.patch
The question is how can I get in installed? I cannot find instructions anywhere and it is not a tar file.
Little help? (1 Reply)
Discussion started by: 300zxmuro
1 Replies
8. UNIX for Dummies Questions & Answers
what are the typical steps used by system adminstrators while applying an application patch upgrade (1 Reply)
Discussion started by: ramky79
1 Replies
9. HP-UX
I am running HP-UX 11iv3 March 2013 release.
smbstatus -V #output
Version 3.4.3 based HP CIFS Server A.03.01.03
What exactly version i am running?
is it 3.4.3 or
A.03.01.03?
Thank you! (1 Reply)
Discussion started by: lamoul
1 Replies
10. Ubuntu
I have applied a patch using this command:
patch -p1 < (file)
then I did git commit -a.
Now I want to recompile the kernel for making this patch live.
Should I use
make oldconfig
or
make localmodconfig
After that,
make -j$(grep -c "processor" /proc/cpuinfo)
sudo make... (1 Reply)
Discussion started by: BHASKAR JUPUDI
1 Replies
cleanup(1M) cleanup(1M)
NAME
cleanup - HP-UX patch cleanup utility
SYNOPSIS
DESCRIPTION
The command provides functions useful when dealing with HP-UX patches on HP-UX.
The command logs all information to
Options
recognizes the following options:
Preview the task but do not actually perform the requested action.
Notify the user of
tasks and request confirmation before performing the requested action.
Commit patches superseded at least
number times. This option is a front-end to the option of (see swmodify(1M)) that provides an easier interface to commit
multiple patches at once.
Remove patches in the specified software depot that have been superseded by
patches also available from the depot.
Specifies whether the software depot contains patches for HP-UX 10.X or 11.X
releases. This option is only valid with the option. If the option is not specified, it defaults to HP-UX 11.X patches.
Specifies whether patches in the software depot that contain a corequisite or
prerequisite attribute specifying one of the superseded patches as a dependency should also be removed. This option is valid
only with the option. If the option is not specified, it defaults to true.
Remove HP-UX 10.X patches that remain in the Installed Product Database
after an upgrade to HP-UX 11.X. These patches are removed from the IPD so that they are no longer displayed in the output of
the command (see swlist(1M)). The HP-UX 10.X patch files are also removed from
Correct the
attribute for HP-UX 11.X patches.
Recommendations
The command should be executed after updating to HP-UX 11.X from HP-UX 10.20. It is not necessary to execute after updating from one ver-
sion of HP-UX 11.X software to another because SD-UX will properly remove 11.X patch information from the IPD in these situations.
The command should be executed whenever patches are added to a software depot. It is not a requirement that superseded 11.X patches be
removed from a software depot, but it is a recommendation to conserve disk space and to avoid confusion. If superseded patches exist in
the same depot as patches that supersede them, SD-UX on HP-UX 11.X will handle the situation properly.
The command can be executed to commit all patches that have been superseded at least the specified number of times. The only benefit from
committing patches is that disk space will be recovered in the
The command can be executed to insure that the attribute of all patch filesets is set correctly. There are several known situations where
the attribute will be set incorrectly. This command can be run at any time, but will be most useful after a system has been installed
using Ignite-UX.
AVAILABILITY
This command is standard on HP-UX 11i v3. On 11i v2 it is available in patch PHCO_32220 or a superseding patch. On 11i v1 it is available
in patch PHCO_27780 or a superseding patch.
WARNINGS
Extreme care should be used when committing patches. Once a patch has been committed, it cannot be removed from the system. Patches
should only be committed when you are satisfied with their behavior. Recovering disk space should not be the only factor considered when
committing patches.
AUTHOR
was developed by HP.
SEE ALSO
show_patches(1), sysdiff(1), check_patches(1M), swlist(1M), swmodify(1M), swremove(1M), sd(4).
cleanup(1M)