Tested samba 2:4.1.6+dfsg-1ubuntu2.14.04.5+lp1416906 today.
The "force user" option is working once more.
Thanks for the patch.
Gérald
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1416906
Title:
Public bug reported:
There is nasty regression bug in samba 4.1.6
That prevents the use of the "force user" option.
https://bugzilla.samba.org/show_bug.cgi?id=9878
It has been fixed in 4.1.7.
For now I installed samba from: ppa:linux-schools/backports
In order to get things working again.
Gér
I installed rsync_3.1.1-2_amd64.deb from the vivid repo.
It installed without issue on trusty and, fortunately, resolves this
major bug.
Gerald
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384503
The point of the mountall2 script was to introduce the idea of a more
intelligent booting process, with pre and post mount hooks and the
ability to check the progress of the FSCK remotely.
I shied away from using the nobootwait option because I needed a
postmount script to restart some services on
I am please to say that the problem is no longer there with:
libssl1.0.0_1.0.1-4ubuntu1
Gérald
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/968801
Title:
SSHd crash with SecureCRT NO-OP
To manage
Its been a week, when will the fix be available in the repos?
The bug is still there with: libssl1.0.0_1.0.1-2ubuntu4
FYI, There is an official patch for the vpaes problem.
Gérald
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Public bug reported:
The moment SecureCRT (SSH client) sends a NO-OP packet, SSHd crashes with this
error:
sshd[1701]: segfault at b9552000 ip b75299f8 sp bfd52370 error 6 in
libcrypto.so.1.0.0[b74d1000+192000]
Debian has a related bug: Bug#665836
I have the problem with:
libssl1.0.0_1.
** Attachment removed: "A working work-around"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/614662/+attachment/1480113/+files/mountall2.tar.gz
--
A better mountall
https://bugs.launchpad.net/bugs/614662
You received this bug notification because you are a member of Ubuntu
Bugs, whi
To summarize, when booting a system, we have 2 options:
- We use "bootwait" on all local filesystems (default)
- We use "nobootwait" on all local filesystems.
The problem with "bootwait" is that it outright prevents the use of Ubuntu on a
headless system.
The problem with "nobootwait" is that i
I think we need to include the very real scenario where Ubuntu Server is
used in a headless capacity. For example I have a dedicated server with
GoDaddy and I have absolutely ZERO access to console. In truth, I
rarely have access to console on pretty much all the server I admin.
If I reboot a sy
I wrote a small script to make booting a system a little less scary. You
can find it here, https://bugs.launchpad.net/bugs/614662
Gérald
--
Boot hangs and unable to continue when automount disk in fstab is not available
(Off or Disconnected)
https://bugs.launchpad.net/bugs/571444
You received t
Even if you set your entry in /etc/fstab to NOT run fsck, the current
mountall will HANG your system if there is a problem.
BTW, I wrote a small script to make booting a system a little less
scary. You can find it here, https://bugs.launchpad.net/bugs/614662
Gérald
--
No error message displaye
Public bug reported:
Binary package hint: initramfs-tools
If you get kernel messages like this:
md: personality for level 1 is not loaded!
And when you run:
mdadm --detail /dev/md0
You get:
State : active, Not Started
This is most likely cause by the fact that the RAID1 module is lo
Here is an updated version of mountall2 which does a better job of
respecting mount hierarchies.
** Description changed:
Binary package hint: mountall
The current implementation of mountall in Lucid is rather dangerous if
you don't have console access.
It will effectively hang your
** Attachment added: "A working work-around"
http://launchpadlibrarian.net/53212583/mountall2.tar.gz
--
A better mountall
https://bugs.launchpad.net/bugs/614662
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Public bug reported:
Binary package hint: mountall
The current implementation of mountall in Lucid is rather dangerous if
you don't have console access.
It will effectively hang your boot process if anything goes wrong. (MD
did not get assembled, data drive is offline, etc.) If you don’t have
c
You know what I would REALY love to see since I am always concerned
about mountall giving me grief is and new option for the sixth field in
fstab.
If would be great if mountall could be updated such that the sixth field in
fstab is:
0 Don't check and **DON'T PAUSE**, filesystem does not need to b
> I would much rather have it display the error on the terminal instead.
Tell me about it. I don't have monitors attached to the servers I admin
so this is a real prob for me.
I can no longer admin the servers strictly from the serial console.
Gérald
--
No error message displayed when device
The reason you don't see anything is that you disabled the Ubuntu splash
screen.
If you remove the kernel options "quite splash" and you have entries in your
fstab that the system has a problem mounting.
**Your in trouble!**
I use a serial console to manage all my servers and this upstart bug i
19 matches
Mail list logo
