Now I remember the pmvarrun program comes up as missing when I install CID. systemctl comes up as missing also & of course the systemctl program error is due to the fact that antiX doesn't have systemd as the init system. I'm thinking that the pmvarrun error can be ignored & my weird stuff going on is due to something else. For my install of antiX 23.1 I had tried an init system called runit which is 1 of the options that they now have in antiX. I'm now in the process of installing antiX 23.2 & reverting...
Eduardo, I've got a message that's coming up when I login to a TTY console. It only happens when I login with a domain user. The message says "HXproc_run_async: pmvarrun: No such file or directory". I'm not even sure this is a bona fide error or just a message but I'm getting some weird stuff going on & wanted to get your input. Is there a log file that you would need to look at to help figure this out? This is on a Debian derivative called antiX 23.1. More than a year ago you had given me the instructions...
Hello Eduardo! I continue to use CID on my computers but now I have run into this problem where the password for the domain account is not cached. This is the 1st attempt at setting up a laptop that won't always be connected to the domain. I followed the instructions presented earlier in this discussion that recommended adding the line cached_login = yes to the /etc/security/pam_winbind.conf file. I didn't have that file so I created it & my 1st mistake was not putting [global] as a line above the...
Thanks Eduardo.
Eduardo, do you think there is a possibility CID would work on FreeBSD? Just wondering. Thanks!
It wasn't hard to figure out the problem but it would be helpful to change your summary to show the username & password as not capitalized. Thanks!! Vance
Sorry for the delay Eduardo. I've been busy with other things & not able to get to this project. On my problem with joining the domain, I had tried it with double quotes but that didn't work but with your tutoring I tried it with single quotes & that did work. The 2nd problem was resolved when I did the updates the computer needed. I think it was something broken with policykit-1 before the updates were done because when I ran the command "sudo cid-gtk" before updating I got an error that in part...
Eduardo, I've got a weird problem going on here. Using AntiX 21 which is a Debian derivative. It's also the same 1 I asked a question about several months ago because it doesn't have systemd. I suppose that might be related to my current problem but probably not. The commandline I try to use is "sudo cid join domain=ayres.lan user=vance pass=Emerson!!4510". Before I enter the password for sudo I get a line that tells me what I asked for. That line prints out as "sudo cid join domain=ayres.lan user=vance...
AntiX doesn't use systemd. Is there a way around the requirement of CID to use systemd? Thanks Eduardo!
Got it. Thanks Eduardo!
That did it Eduardo!!! Do you think the change you made in 1.2.4 will a be necessary improvement for other Debian flavors? I would assume the change is only applicable to Debian & its derivatives. It's been so good to work with you Eduardo & learn more about Linux. If I can be of assistance in the future let me know!
Trinity & it's version 4.7. I did just notice that 4.8 has been released though. I did figure out a workaround. Using the command "sudo systemctl set-default multi-user" in a TTY then rebooting changes the OS so it comes up to a TTY login rather than the GUI. Then I simply use startx to start the GUI & the shares are intact. Thanks for the help Eduardo. You are going above & beyond the standard support for your product CID!
My solution to this problem was to use a SDDM theme that allowed entering both the username & password. I was then able to login using SDDM
Here's the mount command in a terminal window in the GUI before I login to vance in a TTY: vance@q4os-desktop:~$ mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=966244k,nr_inodes=241561,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=198292k,mode=755) /dev/sda1...
Eduardo, I have some interesting information I'd like to get your feedback on. I did some more testing on this & discovered that if I login with CID users at a TTY console in Q4OS the login script works!!! The shares folder is created & the drive resource from the server is available! Then I logged out of the TTY session & was able to login at the GUI with the CID user but the shares folder is NOT created but if I go back to a TTY session & login with the same CID user I've been using all along the...
Good news Eduardo, This is the 1st time I've used the pam_mount capability but as far as I can tell it worked just as it should with Debian Bullseye!!!! This will give me the foundation to try getting other client OSs to work. Thanks!!! Vance
Eduardo, Thanks for the help. I think I did what you asked me to do. As you have time you can give me other thoughts. I'll continue to try changes. At this point I'm using a Debian derivative called Q4OS for the client & I'm still using Zentyal 6.2 on the server. I would assume either of these could be the problem. I think I'll try Debian Bullseye here pretty quick but if there's a log file or anything else that would help you figure this out I can provide that. Thanks!!! Vance
Eduardo, Further information. The /var/log/cid/scripts.log file simply has a bunch of lines in it that say this: "May 07 22:00:43 E520dt CID Init Script >> start 0: Successfully registered hostn ame with DNS" Thanks!!! Vance
Here's the shares.xml file.
So, Eduardo here's what I've done. I used the shares.xml file you have in /usr/share/cid/templates/scripts_cid/ & put the line you recommended in the file. I rebooted but the mount didn't work. What am I doing wrong? I have attached 2 files. The shares.xml file is attached as well as a screenshot of the location I put the file & the permissions on the file.