remote-tty won't start correctly after the reboot: /var/run/remote-tty doesn't' exists

Bug #409805 reported by Ryoichi Shimizu
66
This bug affects 7 people
Affects Status Importance Assigned to Milestone
remote-tty (Debian)
Fix Released
Unknown
remote-tty (Ubuntu)
Fix Released
High
Unassigned
Nominated for Lucid by Jean-Baptiste Lallement

Bug Description

Binary package hint: remote-tty

This package has a few bugs in the startup script, /etc/init.d/remote-tty.
Ubuntu 8.04 uses an "==" instead of "=" in a test. On 9.04 before running
startsrv, you need to add:

    mkdir -p /var/run/remote-tty/sock
    mkdir -p /var/run/remote-tty/pid
    chown -R rttymgr:rttymgr /var/run/remote-tty

You don't just after package installation, but /var/run is cleared on reboot.

TEST CASE:
1. install remote-tty
2. check that the following directories exist
/var/run/remote-tty/
/var/run/remote-tty/pid
/var/run/remote-tty/sock
3. Reboot your computer
4. check that the following directories exist
/var/run/remote-tty/
/var/run/remote-tty/pid
/var/run/remote-tty/sock

VERIFICATION SUCCEEDED:
- The directories exist

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report.

The bashism is fixed since 4.0-12. The creation of the /var/run/remote-tty directory in init script still exists in maverick.
Setting status to triaged/medium.

summary: - remote-tty won't start correctly after the reboot
+ remote-tty won't start correctly after the reboot: /var/run/remote-tty
+ doesn't' exists
Changed in remote-tty (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

here is a fix for maverick. This is exactly the same patch for Lucid since it's the same version of the package.
The creation of directories /var/run/{sock,pid} and ownership have been moved from installation to the init script.

tags: added: patch
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

increasing priority to high because the package is unusable.

description: updated
Changed in remote-tty (Ubuntu):
importance: Medium → High
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

patch update with the right Maintainer

Revision history for this message
Stefano Rivera (stefanor) wrote :

Patch looks good, uploading.

For next time: you replaced tabs with spaces in your patch, try to keep to original indentation. (even if this file was a bit ugly)

Please forward this bug (and patch) to Debian and link the Debian bug to this one.

Changed in remote-tty (Ubuntu):
assignee: nobody → Stefano Rivera (stefanor)
status: Triaged → In Progress
Revision history for this message
Stefano Rivera (stefanor) wrote :

BTW: I made one more change:

* Depend on $remote_fs in init script

Changed in remote-tty (Ubuntu):
status: In Progress → Fix Committed
tags: added: patch-forwarded-debian
removed: patch
Revision history for this message
Stefano Rivera (stefanor) wrote :

Fantastic, thanks

Changed in remote-tty (Ubuntu):
assignee: Stefano Rivera (stefanor) → nobody
status: Fix Committed → Fix Released
Changed in remote-tty (Debian):
status: Unknown → New
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Nominating for SRU / Lucid:
- package is broken and remote-tty fails to start after a reboot when /var/run is of type tmpfs.
- safe patch (directories creation moved from install script to init script) and non critical application
- Regression: None, the package is currently unusable.
- updated patch with Stefano's change attached

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :
Changed in remote-tty (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.