Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#31402 - [smbnetfs] systemd support

Attached to Project: Community Packages
Opened by Steven (Stebalien) - Monday, 03 September 2012, 18:04 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 17 September 2012, 10:46 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Here are two possible smbnetfs service files. The first is a direct translation of the rc script. The second allows the mount point to be configured with the suffix; smbnetfs@mnt-smbnet.service will mount to /mnt/smbnet/.

   smbnetfs.service (0.3 KiB)
   smbnetfs@.service (0.3 KiB)
This task depends upon

Closed by  Sergej Pupykin (sergej)
Monday, 17 September 2012, 10:46 GMT
Reason for closing:  Implemented
Additional comments about closing:  using 1st file
Comment by Dave Reisner (falconindy) - Monday, 03 September 2012, 20:27 GMT
This seems weird... can mount points not be configured via fstab?
Comment by Steven (Stebalien) - Monday, 03 September 2012, 21:15 GMT
Technically, smbnetfs is supposed to be run on login by a user. To get a system-wide instance working, the rc.d script sets the home directory to /etc/smbnetfs and runs smbnetfs as nobody (for security reasons).

There are two ways to get smbnetfs working as a mount program:

1. Write a mount.smbnetfs script that sets the home directory, sus to nobody, and then converts mount options to smbnetfs options. fstab entries would look like:
<anything> /mnt/smbnet smbnetfs options... 0 0

2. Ask upstream to to su to nobody and look for config files under /etc/smbnetfs if called by fuse. This is the correct way to do this. fstab entries would look like:

smbnetfs#<anything> /mnt/smbnet fuse options... 0 0
- or -
<anything> /mnt/smbnet fuse.smbnetfs options... 0 0

-- Edit: There is relevant bug report/patch (http://sourceforge.net/tracker/?func=detail&aid=3563534&group_id=171223&atid=857137) but it handles neither the the config directory issue nor the running as root issue and it requires the ignored device to be called 'none'.
Comment by Dave Reisner (falconindy) - Monday, 03 September 2012, 21:23 GMT
So then it doesn't sound like a system-wide process makes a whole lot of sense. I'm not clear on what value the tempated unit brings, since you couldn't have more than one active at a time.

I realize there's currently an /etc/rc.d script for this, but that doesn't make a whole lot of sense to me either, if this is meant to be a user-specific thing.

Not being a consumer of this, I'll leave it up to Sergey to decide what to do.

Loading...